GilaMonster (5/15/2012)
Snapshots are near-instantaneous, they take very, very little time to create and they only use space = amount of changes made during their existence.As I mentioned, checkDB normally takes a snapshot of the database before it starts so that it can get a consistent view of the database without needing locks. So by creating one manually, you're just doing what checkDB woukld do automatically, no extra time, no extra storage space.
Gail - I just read this on creating a database snapshot...
http://msdn.microsoft.com/en-us/library/ms175876(v=SQL.90).aspx
You describe it as the amount of changes made during their existence, but the information I am getting from MSDN is that based on the current size of the source database, I'll need to have sufficient disk space to hold the database snapshot to the maximum size of the source database at snapshot creation.
I guess I am wanting to know if I am going to need another 300+gb of disk space to create the snapshot, and then incremental amounts based on the original for every time I need to run DBCC CHECKDB?
If I have this correct (i.e. needing another 300+gb to do a snapshot for DBCC CHECKDB), then I am going to find a maintenance window to simply remove this RO FG, and be done with it, but if I am not understanding something correctly here - please help me get it right in my thick skull!
:w00t: