Viewing 15 posts - 15,016 through 15,030 (of 49,552 total)
mitch.fh (1/2/2013)
I think that like the cost of parallelism at one point exceed the benefit there is a "break-even point" for database files.
Don't make the mistake of thinking that multiple...
January 2, 2013 at 6:27 am
Please post the full and complete, unedited output of that command (you've left out at least one line, possibly more)
January 2, 2013 at 5:11 am
mitch.fh (1/2/2013)
More smaller files or fewer bigger files.
Unless all those files are on different physical drives, fewer bigger files is better. There's no gain from having lots of little files...
January 2, 2013 at 5:10 am
You have a table or index with a - in the name and your code doesn't wrap table and index names in []. You're just going to have to go...
January 2, 2013 at 2:44 am
Please run the following and post the full and complete unedited output.
DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
If you're getting repeated corruptions, there's something wrong in the IO subsystem. Check...
January 2, 2013 at 2:37 am
Maybe. Depends why TempDB's growing.
If it's due to hash and sort spille, adding memory may help (optimising queries may help more). If it's due to temp tables and table variables,...
January 2, 2013 at 2:19 am
REbuilding indexes is done with ALTER INDEX ... REBUILD. That's all that's needed.
Was the long query not to identify which indexes needed rebuilding perhaps?
January 2, 2013 at 2:11 am
Jeff Moden (1/2/2013)
GilaMonster (1/1/2013)
Jeff Moden (12/31/2012)
January 2, 2013 at 2:03 am
Safe. Not usually a good idea, but safe.
If you decide to shrink, you need to rebuild all your indexes afterwards. Don't shrink as small as possible, shrink to a sensible...
January 1, 2013 at 1:17 am
opc.three (12/31/2012)
January 1, 2013 at 12:14 am
Jeff Moden (12/31/2012)
January 1, 2013 at 12:09 am
No way to directly do that, the execution plan event does not have duration as a column.
One way to do this is to first capture procedures running slow and then,...
December 31, 2012 at 3:30 pm
MSSQL_NOOB (12/31/2012)
SQL Server 2000 - Full database back up at 9:00pm; transaction log backup at 12:00pm.
Backing up the log once a day? That's useless for recovery. It means you have...
December 31, 2012 at 1:47 pm
MSSQL_NOOB (12/31/2012)
If the percentage used is averaging around, say 5% BEFORE transaction log backup; does that mean there's just a spike at one point in time of use?
Maybe. You'd need...
December 31, 2012 at 1:45 pm
Per-index. Look up Alter Index. The Norecompute setting is the setting you want.
December 31, 2012 at 1:35 pm
Viewing 15 posts - 15,016 through 15,030 (of 49,552 total)