2011-01-19
2,965 reads
2011-01-19
2,965 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,012 reads
2011-01-12
2,702 reads
2011-01-21 (first published: 2011-01-11)
2,892 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,230 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 Chris Yates
Change is not a disruption in technology; it is the rhythm. New frameworks appear,...
No Scooby-Doo story is complete without footprints leading to a hidden passage. In SQL...
By James Serra
A bunch of new features for Microsoft Fabric were announced at the Microsoft Fabric Community...
We’re running SQL Server 2019 with database compatibility level 150, and after recent tuning...
Comments posted to this topic are about the item Changing the Recovery Time
Comments posted to this topic are about the item Getting More Time from AI
I want to change the recovery time for a database running on SQL Server 2022. What are my options for setting the value in my ALTER DATABASE statement. If I run this code, what can I use in place of the xxx to define what 12 means?
ALTER DATABASE Finance SET TARGET_RECOVERY_TIME = 12 xxx;See possible answers