Viewing 15 posts - 14,521 through 14,535 (of 49,552 total)
You can restore a clean backup (one from before the corruption occurred), or you can run checkDB with repair allow data loss and lose a whole bunch of data from...
January 31, 2013 at 6:54 am
If SQL is still taking 100% of the CPU, then you haven't tuned all the CPU consuming queries. Keep going, not something you're going to solve in 5 minutes, usually...
January 31, 2013 at 6:25 am
Did you look in Books Online?
Guidelines for Disabling Indexes and Constraints
Disabling Clustered Indexes
The following additional guidelines apply to disabling clustered indexes:
The data rows of the disabled clustered index cannot...
January 31, 2013 at 6:10 am
jamie_collins (1/31/2013)
The issue with that is the passwords. There are about 250 users using SQL auth.
Then script the logins from QA with hashed passwords, script the logins from prod...
January 31, 2013 at 5:48 am
Query sys.dm_db_partition_stats.
January 31, 2013 at 4:09 am
Drop the logins on QA. Script them from prod with their SIDs, run that script on QA. You need to do that once and only once, after that there will...
January 31, 2013 at 4:06 am
Please run the following and post the full and complete, unedited output
DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
January 31, 2013 at 4:01 am
SQL MOD (1/31/2013)
How did you become so good in the SQL Server topic and how many years of experience do you have? Waht is the key to a knowledge like...
January 31, 2013 at 3:51 am
Just don't try and disable the clustered index. There's a large difference there between dropping and disabling.
January 31, 2013 at 3:38 am
SQL MOD (1/31/2013)
January 31, 2013 at 3:33 am
It will lose data in the msdb database, potentially quite a bit of data. But since you have no backups, you don't really have an alternative.
January 31, 2013 at 3:30 am
Ok, so take a read through chapter 6 of the book I recommended, identify the procedures involved in the blocking, see if you can tune them.
January 31, 2013 at 2:36 am
KSC (1/31/2013)
Here's my execution plan...could you please have a look at it.
I can look, but I can't tell you much useful from an estimated plan alone. Actual execution plan please,...
January 31, 2013 at 2:36 am
KSC (1/31/2013)
Why does a query or better stored procedure claim so much cpu? Could you explain this to me or least tell me where I could read about it?
Typically because...
January 31, 2013 at 2:19 am
Deadlocks or blocking?
If you had to kill a session to resolve, it's not a deadlock, just long duration blocking.
Take a read through chapters 6 and 7 of http://www.simple-talk.com/books/sql-books/troubleshooting-sql-server-a-guide-for-the-accidental-dba/, it...
January 31, 2013 at 2:12 am
Viewing 15 posts - 14,521 through 14,535 (of 49,552 total)