Steven Jones, Chris Unwin and Phil Factor have already written articles that explain perfectly well the how and the what of SQL Clone, so I won’t repeat those details here. This can save external developers like me a great deal of time, since we can now use the image freely to create the development and test copies of the database. Once the image is stored in the Azure cloud, the Clone Agent on the customer network can be deactivated. For example, I am doing some database work for a customer, the Clone Agent service can be turned on interactively, only at the point I need to create the image. This solution has the added security benefit that you do not necessarily need to have the SQL Clone Agent service running continuously on the server hosting the database you want to copy. This article will describe how you can continue to work with SQL Clone, reliably and without relying on access to the corporate network, by running SQL Clone on an Azure Virtual Machine, storing the images on an Azure File Share, and finally tweaking the DNS configuration of SQL Clone so we can access the remote Azure-hosted SQL Clone Server from a local machine, and deploy clones locally. One of the downsides of this approach is that everything is happening in the RDP session only, so debugging your local Visual Studio session against a database on the network, available in the RDP session, is not possible. Besides that, using a corporate VPN solution often comes with security policies that will prevent you from using other resources than the corporate network.Īnother solution is to work with Remote Desktop and do your database magic on that session. This is because, as for any SQL Server database, there must always be a fast and stable network connection between a clone and its file storage, in this case held in the remote ‘image’ files from which the clone was created (see How SQL Clone Works for details). We might just use SQL Clone via a VPN connection, but this can result in unresponsive clones and slow queries. However, often we need to work on a clone from home, or just remotely, on a different network. SQL Clone is designed primarily for use on a corporate network (WAN or LAN) to help an organization create and deploy copies of very large databases, for development and testing work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |