Editorial - iPod

Technical Article

Easy Licenses

  • Article

Software licensing can be complex and confusing. Even in Windows and SQL Server, where hard limits are not enforced, people have problems determining how they should license software. Steve Jones talks about what vendors could do to help us.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2009-11-19

1,026 reads

Technical Article

Testing at Scale

  • Article

It seems that many companies don't have the luxury of working with a variety of hardware configurations to test their architecture before deploying their applications. Some of the issues involve time and some involve tools. Steve Jones has an idea that could help with the latter today.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2009-11-16

1,261 reads

Blogs

Wait… Could This Be the End of Index Maintenance?

By

While attending SQLCon and FabCon Europe in Barcelona, there were a lot of announcements...

Copilot on the Power BI Report Canvas vs. Modern Report Builder

By

(This is the second post in a three-part series on how AI is changing...

The #MS_DatabaseConnector## Role: #SQLNewBlogger

By

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

Read the latest Blogs

Forums

Pay for Performance

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Pay for Performance, which is...

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

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