May 11, 2016 at 9:35 am
We have a standalone production SQL Server instance that install on a VM. The database on this server has TDE turned on.
Is it possible to create a develop instance by cloning the production VM?
I assume we need to run sp_dropserver and sp_addserver on the new dev server, since the server name is changed.
Has anyone done this before? Are there any caveats or “gotchas” I should be aware of?
Thanks,
Lijun
May 14, 2016 at 4:41 pm
You could clone the VM. I'd try to make sure there weren't open transactions, as the method you use to clone needs to properly freeze IO, but you can try.
If you use TDE here, you should be fine as the certificate will be in the clone. Changing the name of the Windows machine and SQL are certainly required.
However, if you have a dev instance, it's easy to move the database back with a backup/restore. If you worry about TDE, it's easy to move a backup of the certificate to the dev machine, and you (or someone) should be comfortable this in case production dies. You need a way to restore the database backup.
May 15, 2016 at 10:34 am
Hold the phone a minute. If the production database is under TDE, why on Earth would you copy it to a Developer's box? Sale of private/sensitive information doesn't come just from external sources.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2016 at 1:02 pm
why not just use a clean VM and backup and restore the database and the certificate. Having your prod certificate on a dev database server is questionable itself, your IT security team will likely have kittens
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply