September 21, 2010 at 11:53 am
GilaMonster (9/21/2010)
If you're interested, the snapshot is created using the NTFS alternate stream feature, and is created as an alternate stream of the data files, hence same drive and same directory as the data files are.
Always interested. That's part of the minimally built database I've seen mention of that builds at 64kb or something similar?
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
September 21, 2010 at 1:05 pm
Craig Farrell (9/21/2010)
That's part of the minimally built database I've seen mention of that builds at 64kb or something similar?
Huh?
CheckDB snapshot is created when checkDB starts and dropped as soon as it finishes.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 21, 2010 at 2:20 pm
GilaMonster (9/21/2010)
Craig Farrell (9/21/2010)
That's part of the minimally built database I've seen mention of that builds at 64kb or something similar?Huh?
CheckDB snapshot is created when checkDB starts and dropped as soon as it finishes.
Sorry, should have rechecked my research. NTFS Sparse Files:
http://msdn.microsoft.com/en-us/library/ms175823.aspx
From what I've been able to gather so far (I'm still digging when I can find time, will probably take me a few days to get through what I've found so far) the snapshot from CHECKDB uses these sparse files.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
September 21, 2010 at 2:24 pm
Craig Farrell (9/21/2010)
From what I've been able to gather so far (I'm still digging when I can find time, will probably take me a few days to get through what I've found so far) the snapshot from CHECKDB uses these sparse files.
All database snapshots use sparse files.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 21, 2010 at 2:49 pm
Another thing to note is that you don't need or want to run DBCC CHECKDB ... WITH DATA_PURITY all the time. In fact, according to BOL - you do not need to specify this option for databases that have been created in 2005 and above.
If the database was created in 2000 and upgraded, then you only need to run this one time on the upgraded database.
What you should be running instead is: DBCC CHECKDB ... WITH ALL_ERRORMSGS, NO_INFOMSGS;
DATA_PURITY
Causes DBCC CHECKDB to check the database for column values that are not valid or out-of-range. For example, DBCC CHECKDB detects columns with date and time values that are larger than or less than the acceptable range for the datetime data type; or decimal or approximate-numeric data type columns with scale or precision values that are not valid.
For databases created in SQL Server 2005 and later, column-value integrity checks are enabled by default and do not require the DATA_PURITY option. For databases upgraded from earlier versions of SQL Server, column-value checks are not enabled by default until DBCC CHECKDB WITH DATA_PURITY has been run error free on the database. After this, DBCC CHECKDB checks column-value integrity by default. For more information about how CHECKDB might be affected by upgrading database from earlier versions of SQL Server, see the Remarks section later in this topic.
If PHYSICAL_ONLY is specified, column-integrity checks are not performed.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
September 21, 2010 at 11:43 pm
GilaMonster (9/21/2010)
Bhuvnesh, sure there wasn't an index rebuild job running around the same time? Index rebuild will grow the DB
Thats correct, you hit the nail at right spot. actually one of the DBA had started the index rebuild process( without) intimating others.anyways thanks Gail 🙂
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
Viewing 6 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply