SOLVED
Home

SQL backup authentication after Storage Account upgrade to V2

%3CLINGO-SUB%20id%3D%22lingo-sub-843919%22%20slang%3D%22en-US%22%3ESQL%20backup%20authentication%20after%20Storage%20Account%20upgrade%20to%20V2%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-843919%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EI%20have%20some%20doubts%20before%20upgrading%20Storage%20Accounts%20to%20V2.%26nbsp%3B%3C%2FP%3E%3CP%3EWill%20the%20SQL%20credentials%20and%20access%20remain%20untouched%20for%20the%20SQL%20managed%20backups%20in%20SQL%202016%20-%20using%20SAS%20tokens%20and%20for%20SQL%202014%20using%20regular%20SA%20connection%20keys%3F%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20any%20read%2Fwrite%20speed%20difference%20between%20V1%20and%20V2%3F%20I.e.%20between%20V1%20Standard%20and%20V2%20Standard%20-%20Cool.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-843919%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Backup%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EData%20%2B%20Storage%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-845924%22%20slang%3D%22en-US%22%3ERe%3A%20SQL%20backup%20authentication%20after%20Storage%20Account%20upgrade%20to%20V2%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-845924%22%20slang%3D%22en-US%22%3E%3CP%3EI%20went%20and%20tried%20this%20within%20my%20Azure%20account%20and%20both%20the%20SAS%20string%20and%20the%20storage%20account%20keys%20remained%20the%20same.%20I%20verified%20within%20SQL%20that%20both%20still%20functioned%20with%20SQL%20managed%20backups.%20As%20for%20performance%20there%20is%20no%20difference%20but%20the%20access%20cost%20is%20higher%20on%20the%20cool%20tier%20of%20storage.%20Please%20see%20the%20following%20Microsoft%20Doc.%20Let%20me%20know%20if%20you%20have%20additional%20questions!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fstorage%2Fblobs%2Fstorage-blob-storage-tiers%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fstorage%2Fblobs%2Fstorage-blob-storage-tiers%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F404560%22%20target%3D%22_blank%22%3E%40tymb%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
tymb
Senior Member

Hi,

I have some doubts before upgrading Storage Accounts to V2. 

Will the SQL credentials and access remain untouched for the SQL managed backups in SQL 2016 - using SAS tokens and for SQL 2014 using regular SA connection keys? 

Is there any read/write speed difference between V1 and V2? I.e. between V1 Standard and V2 Standard - Cool.

1 Reply
Solution

I went and tried this within my Azure account and both the SAS string and the storage account keys remained the same. I verified within SQL that both still functioned with SQL managed backups. As for performance there is no difference but the access cost is higher on the cool tier of storage. Please see the following Microsoft Doc. Let me know if you have additional questions!

 

https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-storage-tiers

 

@tymb 

Related Conversations
Extentions Synchronization
Deleted in Discussions on
3 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
35 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies