2011-01-19
2,970 reads
2011-01-19
2,970 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,055 reads
2011-01-12
2,704 reads
2011-01-21 (first published: 2011-01-11)
2,910 reads
2011-01-07
2,696 reads
2010-12-31
2,424 reads
This article demonstrates how to monitor table size growth in SQL Server.
2010-12-21
4,522 reads
2010-12-14
2,236 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
By Brian Kelley
Fabiano Amorim has written an excellent article at Simple Talk on securing msdb. Here's...
By Steve Jones
This month we have a new host, which I am grateful for. So many...
I needed to do some research because there is more to #temp tables than...
hi , our business partner is asking s4 sap api's for receivable info and...
I have a really stupid question... Is there an easy way to search for...
Comments posted to this topic are about the item How to Work with On-Premises...
The STRING_ESCAPE() function requires 2 parameters in SQL Server 2025. The first is a string of text and the second is the type of escape rules being used. What are the options for the second parameter?
See possible answers