Jason Brimhall


Blog Post

Ghosts in your Database

Yes Virginia, there are ghosts in your database.  More specifically, there are ghosts in your SQL Server database.  They are not there to haunt you.  They are not there...

2018-11-26

22 reads

Blog Post

How Long is That Event Taking

Knowing just how long an event takes is a common requirement when troubleshooting. Sometimes, figuring out the unit of time is a bit troublesome. Is it milliseconds, seconds or...

2018-11-20

18 reads

Blog Post

PowerShell ISE Crashes

Working with PowerShell brings a lot of advantages and power to help manage a server. The more current your PoSh version, the more efficiently you will be able to...

2018-11-19

29 reads

Blogs

The #MS_DatabaseConnector## Role: #SQLNewBlogger

By

I had seen these roles in various instances, but never dug into the new...

Asking for Help Isn’t a Weakness

By

During COVID, I attended training on software/enterprise architecture given by Mark Richards. One of...

The Proof of the Backup Is in the Pudding

By

For me, the objective is straightforward: have a backup strategy that is reliable, understandable,...

Read the latest Blogs

Forums

Access + ODBC Driver 18 + SQL Server 2025: ~150–250 ms per request

By Bruno De Grauwe

Has anyone encountered recurring request latency when using Microsoft Access with SQL Server 2025...

The ##MS_DatabaseConnector## User

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The ##MS_DatabaseConnector## User

Planning for Change

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Planning for Change

Visit the forum

Question of the Day

The ##MS_DatabaseConnector## User

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
GO
I then login as Demo and run this:
USE sandbox
go
SELECT CURRENT_USER
What is returned?

See possible answers