This month’s T-SQL Tuesday is inspired by the blog post Will the Cloud Eat My DBA Job? by Kendra Little.
Technology has changed a lot in the past years, especially with cloud/globalization/automation. What impact has this had on your job? Do you feel endangered? Over the years I’ve seen a lot of things change with SQL Server.
I remember that somebody told me when I started with SQL Server 200 that T-SQL was never going to be a big thing. How wrong was that guy right?!
The dbatools module recently got a couple of new commands mask data in their databases. One feature with the masking commands that were not yet put in was deterministic masking.
Deterministic masking is the process of replacing a value in a column with the exact value across tables. For example, a database has multiple tables with a column that has first names. With deterministic masking, the first name that’s present will always be replaced with the same value.
The dbatools module recently got a couple of new commands mask data in their databases. One feature with the masking commands that were not yet put in was deterministic masking.
Deterministic masking is the process of replacing a value in a column with the exact value across tables.
For example, a database has multiple tables with a column that has first names. With deterministic masking, the first name that’s present will always be replaced with the same value.
There are lots of great articles that describe how the command for decrypting SQL Server objects when they’re saved with encryption like Encrypting and Decrypting SQL Server Stored Procedures, Views, and User-Defined Functions Simple Way to Decrypt SQL Server Stored Procedure
Most of them rely on T-SQL and SSMS but I wanted to do the same thing with PowerShell. This way I can execute it for several objects at a time and maybe even in multiple databases and instances.
In the third part of the series we discussed the way to get the log shipping errors using the command “Get-DbaLogShippingError”.
This blog will be about how to recover a log shipped database.
I can be very short in this paragraph, there is no out-of-the-box solution to recover a log shipped database.
Initially, log shipping was meant to be used as a warm standby. You have your data on another instance but you still have some human intervention to get it all back up. Imagine the following situation. You have set up log shipping using either the GUI or the commands in dbatools.