2011-01-24
2,569 reads
Administration
2011-01-20
2,728 reads
2011-01-19
2,978 reads
Making a more reliable and flexible sp_MSforeachdb
While the system procedure sp_MSforeachdb is neither documented nor officially supported, most SQL Server professionals have used it at one time or another. This is typically for ad hoc maintenance tasks, but many people (myself included) have used this type of looping activity in permanent routines. Sadly, I have discovered instances where, under heavy load and/or with a large number of databases, the procedure can actually skip multiple catalogs with no error or warning message. Since this situation is not easily reproducible, and since Microsoft typically has no interest in fixing unsupported objects, this may be happening in your environment right now
2011-01-18
3,580 reads
2011-01-17
3,097 reads
2011-01-12
2,706 reads
2011-01-21 (first published: 2011-01-11)
2,932 reads
2011-01-07
2,698 reads
2010-12-31
2,427 reads
Monitoring Table Size Growth in SQL Server
This article demonstrates how to monitor table size growth in SQL Server.
2010-12-21
4,522 reads
Blogs
The #MS_DatabaseConnector## Role: #SQLNewBlogger
By Steve Jones
I had seen these roles in various instances, but never dug into the new...
Asking for Help Isn’t a Weakness
By Brian Kelley
During COVID, I attended training on software/enterprise architecture given by Mark Richards. One of...
The Proof of the Backup Is in the Pudding
For me, the objective is straightforward: have a backup strategy that is reliable, understandable,...
Forums
Pay for Performance
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
Has anyone encountered recurring request latency when using Microsoft Access with SQL Server 2025...
The ##MS_DatabaseConnector## User
Comments posted to this topic are about the item The ##MS_DatabaseConnector## User
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 GOI then login as Demo and run this:
USE sandbox go SELECT CURRENT_USERWhat is returned? See possible answers