Viewing 15 posts - 31 through 45 (of 993 total)
No - running DBCC CHECKDB on any copy of the database that is maintained by SAN replication, log shipping, mirroring, etc is not good enough. That tells you nothing about...
June 18, 2014 at 11:09 am
I always advise NOT detaching the original database because you might not be able to attach it again if there's a problem with the database.
Set the database offline, copy the...
April 15, 2014 at 7:07 am
Did you call Product Support yet? What did they say?
March 28, 2014 at 12:05 pm
Another script that: a) doesn't filter out LOB_DATA or ROW_OVERFLOW_DATA allocation units b) runs over all indexes
Do yourself a favor and download Ola Hallengren's database maintenance solution and just use...
March 27, 2014 at 1:33 pm
Don't apologize - everyone starts with zero knowledge about SQL Server.
If the log file is created very small, it will have to autogrow back to the steady-state size. Each autogrow...
March 26, 2014 at 1:41 pm
Correction: ATTACH_REBUILD_LOG will only create a single log file, no matter how many log files you had before.
Beware that in all cases, you get a 0.5MB log file with two...
March 13, 2014 at 3:58 am
Have you tried using EMERGENCY mode and using DBCC CHECKDB to rebuild the log and make the database accessible (albeit transactionally inconsistent)? That's your last resort in this situation.
March 3, 2014 at 6:20 am
I wish people would stop perpetuating the phrases 'external fragmentation' and 'internal fragmentation' and use the phrases that the SQL team, the tools, and Books Online uses: logical fragmentation and...
November 26, 2013 at 11:40 pm
No - I removed it in SQL Server 2005 because people were causing problems for themselves. See http://www.sqlskills.com/blogs/paul/dbcc-pintable/ for some explanation.
If you find a table is dropping out...
October 28, 2013 at 4:56 pm
Are you using Change Tracking? That's what the syscommittab is for. If so, try disabling and reenabling Change Tracking.
If that doesn't fix it, or you're not using Change Tracking, I'd...
October 28, 2013 at 4:46 pm
I know - it's very misleading because it doesn't actually do minimal logging for it.
If you watch the log records, it's a metadata-only operation to unhook the allocation unit and...
August 26, 2013 at 10:13 am
TRUNCATE TABLE is not a minimally-logged operation. It's logged exactly the same way in all recovery models. It's fully logged, but very efficiently logged, including using the deferred-drop mechanism.
Minimal logging...
August 26, 2013 at 8:49 am
Is someone changing the compatibility level/mode of the database?
May 24, 2013 at 4:01 pm
@bitBIG - that comment about understanding the implications was added this morning.
May 6, 2013 at 12:19 pm
Viewing 15 posts - 31 through 45 (of 993 total)