Viewing 15 posts - 23,566 through 23,580 (of 49,552 total)
(quote the post if you want to see how to get links working properly.)
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 13, 2011 at 4:25 am
File-level backups of SQL data files are not backups. They have a irritating habit of being useless when trying to attach them.
You should have backups of the system databases as...
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 13, 2011 at 4:23 am
Yup. Or you can get a nice pre-written script that already does all of that, like the one at http://sqlfool.com/
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 13, 2011 at 4:20 am
Way too small to care about. The generally recommended rough guide to the size of index you need to worry about for rebuilding indexes is 1000 pages.
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 13, 2011 at 3:00 am
Alter index ... Rebuild is how you remove fragmentation.
Let me guess, it's a tiny index, probably under 10 pages in size?
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 13, 2011 at 12:57 am
Run SP_configure and set allow updates to 1. Update sysdatabases for that database and set the status to 32767.
Then see if you can access the DB and run checkdb. Not...
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 13, 2011 at 12:55 am
All auto grow should be configured in MB, especially the log. A % can cause nasty surprises with larger files, and it's the log that takes longer to grow and...
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 13, 2011 at 12:44 am
sqlbuddy123 (9/12/2011)
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 13, 2011 at 12:43 am
RESTORE DATABASE "Ken-Test"
FROM DISK = 'f:\mssql\backup\Mun-EaseMainWebDb\muneas_backup.bak'
WITH
MOVE 'Mun-EaseEmptyDb_Data' TO 'f:\mssq\data\Test\Ken-Test_Data.mdf',
MOVE 'Mun-EaseEmptyDb_Log' TO 'f:\mssq\data\test\Ken-Test_Log.ldf',
You're missing the l in sql. You've got mssq not mssql.
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 12, 2011 at 4:44 pm
Seeks can be on any index at all. That's the main reason for having an index.
It's a key lookup that's always to the cluster.
p.s. To eliminate key lookups you don't...
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 12, 2011 at 4:43 pm
halifaxdal (9/12/2011)
GilaMonster (9/12/2011)
Did someone detach or drop the DB? Only reasons it wouldn't be in sysdatabases.i don't know, the guy did tell me he saw it was marked as suspect
A...
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 12, 2011 at 4:42 pm
Frankly he should be on at least SP1, preferably SP2 regardless of problems....
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 12, 2011 at 3:37 pm
Did someone detach or drop the DB? Only reasons it wouldn't be in sysdatabases.
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 12, 2011 at 3:37 pm
Autogrow timeout maybe (it'll be in the error log) or autogrow took too long, query that needed space failed and rolled back.
Autogrow's not something that should be relied on for...
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 12, 2011 at 3:02 pm
Note that the restriction on the log file is actually not a restriction. It's 2048 TB, the maximum allowable size for a log file ever.
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 12, 2011 at 2:34 pm
Viewing 15 posts - 23,566 through 23,580 (of 49,552 total)