SQL Clone and Encryption

SQL Clone is amazing, and it can really save time and disk space for many organizations. I’ve got a series posted here on various little things I’ve learned about the product. There are also a number of articles on the Redgate Community Hub.

I’ve been testing and working with SQL Clone for the last few months, trying to help the devs at Redgate ensure this product is ready to go when it’s released. I’ve written a few pieces on this blog, and I’ve got a new one up on the Redgate blog that looks at Clone and TDE.

When I started looking at this, I assumed SQL Clone would work. After all, the product tries to ensure that a clone looks just like any other database to SQL Server. It does, and TDE just works.

I’m still looking at other features, but so far, everything works great. The clone databases are indistinguishable from normal databases, except that I can blow one away and recreate it from the image in seconds. That’s pretty cool, especially when you’ve messed up a bunch of data while writing code that wasn’t quite production ready.

I’m looking forward to seeing how others use SQL Clone and how this will help ensure developers work with larger, known data sets, in their own sandboxes. Perhaps we’ll finally get rid of the shared database and developers’ work unnecessarily impacting their teammates.

About way0utwest

Editor, SQLServerCentral
This entry was posted in Blog and tagged , , . Bookmark the permalink.
%d bloggers like this: