SQLSaturday #52 – Colorado Recap
I had the good fortune of being able to travel to Denver for SQLSaturday #52 the weekend of September 25,...
2010-10-04
674 reads
I had the good fortune of being able to travel to Denver for SQLSaturday #52 the weekend of September 25,...
2010-10-04
674 reads
Back in 2007 when we started SQLSaturday we had the good luck to leverage an existing relationship between Seminole Community...
2010-10-04
763 reads
I drove up on Friday, just under 7 hours with a couple quick stops on the trip. Listened to Team...
2010-10-04
517 reads
Another weekend, another new city, another SQL Saturday. This was my first trip to Kansas City, and it was a...
2010-10-04
1,609 reads
The CPUID website has a screenshot of CPU-Z 1.55.2, showing its support for the upcoming 32nm Sandy Bridge processor, which...
2010-10-04
595 reads
I have been working with a several clients that are leveraging Change Data Capture (CDC) as a tool for incrementally...
2010-10-03
1,359 reads
So many people have been waiting for a SQL Saturday in Houston and now it’s finally here. As a native...
2010-10-03
725 reads
It is amazing how fast time moves the older (and slower) we as humans get. Looking back on time, it...
2010-10-03
631 reads
The KC PASS chapter has successfully executed the latest SQL Saturday. Thanks to all the organizers and volunteers for a...
2010-10-03
2,022 reads
As I discussed in my first part of replication SQL Server 2008 Replication: High Availability Solution Part One, replication is...
2010-10-03
12,090 reads
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,...
By DesertDBA
Note: This post is the invitation for T-SQL Tuesday #204 on November 3rd, 2026....
Wa:083849450961 Ruko Poris Indah, Komp, Jl. Poris Indah Blok K No. 2-3, RT.003/RW.003, Cipondoh...
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