![]() Refresh the Credentials in SSMS and verify the new one was created: Run this in a Query Window, using the Storage Account name and Key from your subscription. SECRET = 'pvv99UFQvuLadBEb7ClZhRsf9zE8/OA9B9E2ZV2kuoDXu7hy0YA5OTgr89tEAqZygH+3ckJQzk8a4+mpmjN7Lg=' Go to your portal, and copy one of the Access Keys associated with your new Storage Account.ĬREATE CREDENTIAL SQLBackups -give this a meaningful name Note that I have no Credentials at this time: I am using SQL Server 2016 Developer Edition on a Windows 10 Pro Dell Precision laptop. I am using 16.x despite 17.4 being out as of this writing, mostly because I upgrade slowly and don’t like the icons of the 17.x releases. For now, that is all we will do in the portal, but leave your browser open for copying the Key and URL, as well as refreshing to see results of the Backup command. When we start to build our T-SQL statements, we will need both the Access key from earlier and the URL.Īt this point, you have an Azure Subscription, with a Standard Storage Account, that has a Blob Container in it. For now just remember where this is or copy it to Notepad, Query window etc. Click the button next to the URL to copy it. After a successful backup, you will see it here.Ĭlick on ‘Container Properties’ to get the URL for this specific container…this will be used in Backup and Restore statements. Note the “no blobs found” in the container. The deployment of the container should be very quick. Also, choose Private for the Public Access Level. I use the SQL instance name here, just as I would for a regular folder on a files hare. If you enter an illegal name it will not let you continue. Names can only be lowercase letters, numbers and hyphens. You will need one of the 2 keys when we create a SQL Server Credential later on.Ĭlick + Container and give it a name. If they get out, you can regenerate either one or both pairs. ![]() Do not give these out freely…only to those with a need for them. ![]() Verify the settings you chose are there (highlights below):Ĭlick on ‘Access Keys’ to see the two auto-generated Keys and Connection strings for accessing this storage account. Go back to the storage accounts blade and refresh to see your new account. Location: probably a good idea to keep it fairly close to the SQL Servers you are backing up for performance reasons…but you may want to send it farther away…your call.Ĭlick Create and wait for the notification to let you know the account exists. Resource group: where will this storage account go? Just a logical container SSD…Standard for testing or infrequently accessed files. Select the properties for your new storage account.Īccount Kind: Storage or StorageV2, not Blob Storage Log into your subscription and click Storage accounts on the left side, then click +Add:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |