2011-01-25
2,898 reads
2011-01-25
2,898 reads
2011-01-24
2,565 reads
2011-01-20
2,722 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,013 reads
2011-01-12
2,702 reads
2011-01-21 (first published: 2011-01-11)
2,894 reads
2011-01-07
2,695 reads
2010-12-31
2,422 reads
By Steve Jones
Earlier this year I visited a customer that was using the Redgate Monitor webhook...
By Zikato
TSQL ScriptDOM is a useful library for parsing scripts into an abstract syntax tree....
By DataOnWheels
Over the past few months, I have debated starting a new blog to discuss...
Hi, we lost our sever sql2000 To restore database to a new one we...
Hi, since we lost our sql server 2000 server we are trying to restore...
Comments posted to this topic are about the item Do You Really Need HA?
I run this code:
create database experiment
go
use Experiment
go
select DATABASEPROPERTYEX('Experiment', 'LastGoodCheckDbTime')
What is returned? See possible answers