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 Steve Jones
I had seen these roles in various instances, but never dug into the new...
By Brian Kelley
During COVID, I attended training on software/enterprise architecture given by Mark Richards. One of...
For me, the objective is straightforward: have a backup strategy that is reliable, understandable,...
Has anyone encountered recurring request latency when using Microsoft Access with SQL Server 2025...
Comments posted to this topic are about the item The ##MS_DatabaseConnector## User
Comments posted to this topic are about the item Planning for Change
On SQL Server 2025, I run this code as a sysadmin:
CREATE LOGIN Demo WITH PASSWORD = 'Demo1234567' GO ALTER SERVER ROLE ##MS_DatabaseConnector## ADD MEMBER Demo GOI then login as Demo and run this:
USE sandbox go SELECT CURRENT_USERWhat is returned? See possible answers