This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 38%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERR%3C/text%3E%3C/svg%3E)
SQL Server Managed Instance Replication Snapshot
I am working on setting up transactional replication from a SQL Managed Instance to a VM hosted SQL Server. SQL MI requires the snapshot folder for initial replication to be in Azure Storage. SQL MI does not allow Active Directory (Windows) logins.
This means I have to use an SQL login or an Azure Active Directory login to create the snapshot in the snapshot folder. When I use a SQL login, the snapshot agent service starts, but the login cannot create the snapshot subdirectory. When I use an integrated Azure Active Directory login with permissions to the Azure Storage account and file share, the snapshot agent will not start.
What is the magic combination to get the snapshot working?
Hi @Ray R. Mosely Thank you for posting your question on Microsoft Q&A and for using Azure services.
Could you please clarify the below.
Are you trying this topology.? Pub and Dist on SQL MI(s) and Sub on SQL Server?
If you're trying to have Pub on SQL MI and Dist on SQL Server, that will not work.
Regards,
Oury
Pub and Dist on SQL MI. Sub on SQL Server. Snapshot folder in Azure Storage. Pub works, Dist works, Snapshot does not work.
Hi @Ray R. Mosely Sorry for the delay in response to your question.
This topology is supported, and it should work. This problem is often due with some posts not being open, so SQL MI cannot access remote storage.
Regards,
Oury
This snapshot portion of the replication is now working. There is a special procedure available only from the command line to create the authentication for the connection from the MI to the Azure Storage account. Without that, authentication won't work.
@Ray R. Mosely Very Good. Thank you for letting us know. I am glad that it is working.
Regards,
Oury
I checked this internally with our product group but seems like part of the confi is only possible only from T-SQL, not command line.
There is a blog post that talks about setting that direction. there are details on how to setup azure storage for tran replication purpose.
Database migration from Managed Instance to SQL Server with transactional replication
Please let me know if you need more details on that
Hope this helps
Regards,
Oury
Correct, my mistake. It is a T-SQL process not command line. The command line is not available from an MI.
Thanks, Ray
That is correct. Thanks again for your prompt response @Ray R. Mosely Please don't forget to mark as accept answer. It will be helpful for other community members with the same problem.
Regards,
Oury