2011-01-19
2,960 reads
2011-01-19
2,960 reads
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,001 reads
2011-01-12
2,700 reads
2011-01-21 (first published: 2011-01-11)
2,878 reads
2011-01-07
2,695 reads
2010-12-31
2,422 reads
This article demonstrates how to monitor table size growth in SQL Server.
2010-12-21
4,522 reads
2010-12-14
2,226 reads
This article explores the causes and remedies for applications failing due to too many open connections to SQL Server.
2010-12-14
3,775 reads
Have you ever wondered where a certain field is used in a report? Or...
By Steve Jones
One of our internal people was looking to test some process in (I assume)...
By James Serra
Announced at Microsoft Ignite last week were some new product features related to the...
Fildena 100 purple pill, a trusted and effective ED medication, provides a reliable solution...
I am using the following script to import data from a json file. This...
When I connect to my SQL Server using SQL Server Management Studio (SSMS) from...
Which of these inputs is the smaller input to a hash join?
See possible answers