Migrating Data From a TDE Enabled SQL Server Database Without a Key
But our database has TDE enabled, shouldn’t our data at rest in the BACPAC be protected? Nope.
But our database has TDE enabled, shouldn’t our data at rest in the BACPAC be protected? Nope.
Over the years I’ve been able to compile a list of issues that I would consider to be common with SQL Server (and other database platforms like Oracle, no platform is immune to such issues). These are the issues that are often avoidable but not always easy to fix once they have become a problem. The trick for senior administrators such as myself is to help teams understand the costs, benefits, and risks of their application design options so as to avoid these common problems. So, here is my list of the top 5 most common problems with SQL Server.
By pausing the SQL Server service before restarting the instance we allow end users to continue their work uninterrupted and we also stop any new connections to the instance.
This is a welcome addition to the install for SQL Server 2016 that I had not seen mentioned previously (you can find lots of posts about the new tempdb options, for example).
Here’s an example of something I came across for Azure SQL Database V12 that I don’t see documented anywhere (yet): You can change the compatibility level of an Azure SQL Database.
It’s that time of year again. It’s only natural for folks to wax nostalgic as 2015 fades into the sunset one final time.