Using SQL Change Automation in SSMS to Track Static Data Changes
SQL Change Automation 4.1 now allows users to develop static data changes from SQL Server Management Studio.
2020-01-02
SQL Change Automation 4.1 now allows users to develop static data changes from SQL Server Management Studio.
2020-01-02
In order to protect data and comply with regulations such as the GDPR and HIPAA, databases used by developers and testers must not contain private and sensitive data from production databases. To help DBAs protect data, Microsoft have released a new feature as part of SSMS called Static Data Masking. In this article, Greg Larsen demonstrates how to use this new feature.
2019-02-07
2,794 reads
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
By Brian Kelley
On Patch Tuesday, in addition to OS and Office security patches, Microsoft also released...
When mirroring was first released for Azure SQL Database, it used Change Data Capture...
Comments posted to this topic are about the item Multiple Deployment Processes
Comments posted to this topic are about the item How to Use sqlpackage to...
Comments posted to this topic are about the item Upgrading Admin Queries
I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?
See possible answers