External Article

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

SQLServerCentral Editorial

ETL Security Holes

The growth of ETL processes and secondary systems for reporting, decision support and other analysis creates an issue. Steve Jones points out that we ought to be remembering that security needs to be applied to data, not just systems.

Blogs

Advice I Like: Celebrate Success

By

“On the way to a grand goal, celebrate the smallest victories as if each...

Programmatically Retrieving MLV Lineage and Refresh Times

By

Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...

SWAG Saves the Day

By

PASS Summit East is in one week. I was on the road last week...

Read the latest Blogs

Forums

BCA KCP Sudirman Mansion Telpon/WA:08137887595

By tanehome

BCA KCP Sudirman Mansion Telpon/WA:08137887595.Sudirman Mansion, JL Jenderal Sudirman, Kav. 59 No.77 Lt. G...

BCA KCP Graha Paramita Telpon/WA:08137887595

By tanehome

BCA KCP Graha Paramita Telpon/WA:08137887595.Gdg Graha Paramita Lobby Depan, Jl. Denpasar Raya Blok D-2,...

BCA KCP Gandaria City Telpon/WA:08137887595

By tanehome

BCA KCP Gandaria City Telpon/WA:08137887595.Gedung Mal Gandaria City Mainstreet-Upper Ground M-U25, Jl. Sultan Iskandar...

Visit the forum

Question of the Day

Increase Deadlock Detection

How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?

See possible answers