Viewing 15 posts - 22,156 through 22,170 (of 22,219 total)
Good news. You've got an index allocation error. Easiest kind to fix. Drop the index and recreate it. Make sure you've got the recreate script handy prior to dropping of...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 14, 2005 at 8:07 am
One thing not mentioned, is there a difference in parameters being passed by the various users? Are the first three calling proc A and passing in a parameter that returns...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 14, 2005 at 7:18 am
While there are exceptions, the general rule would be to use a join against either a table or a derived table. It's almost always going to be faster becuase of...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 14, 2005 at 7:14 am
I also can't tell you what caused it, but I ran into the same issue. I ran change owner proc against it to set the owner to a user that...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 14, 2005 at 6:48 am
You're going to have to, minimum, set the traceflag 1204 to on. That will spit a bunch of information into your sql error log file that you can use to...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 14, 2005 at 6:36 am
In addition to what everyone has suggested (and the experience thing is the biggest and most important), I'd add the book: Database Administration by Craig S. Mullins. It's not specific...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 14, 2005 at 6:29 am
Fantastic advice... Except for the GUID's. Indexing, especially clustered indexes, against GUID's is pretty problematic. They're bloody slow. I'd be very cautious in when, where, and how I introduced them...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 1, 2005 at 8:49 am
Everything Peter said...
The caveat that you have to be aware of is memory. Every document handle takes a certain amount of memory. Then the document itself chews up memory. Memory...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 30, 2005 at 7:47 am
We use Redgate SQL Compare.
You should know that there are several other tools out there in addition to the ones that others have already mentioned. Embarcadero has a pretty good...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 30, 2005 at 7:13 am
Sounds like a really good script. I'll check it out when it becomes available.
One point, blocking locks and deadlocks are two different things. Deadlocks are caused by two processes...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 30, 2005 at 4:27 am
Great answer. I should have thought to add all of that but didn't. Thanks for help.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 29, 2005 at 4:17 pm
As long as you know that you may have some number of transactions that cross over... No, it's not a big deal at all.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 29, 2005 at 4:08 pm
Set the the traceflags -T1204 and -T3605. This will write the basic deadlock info out to the SQL Server error log. Profiler will still be more useful in tracking down...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 29, 2005 at 10:23 am
The biggest issue with going to Windows Authentication is the lack of support for this from third party applications. Almost every single one of them that I've installed since the...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 29, 2005 at 10:19 am
Manual tests are probably run under your user context where as the automated schedules are running under the security context of the SQL Server instance. You need to verify that...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 28, 2005 at 1:27 pm
Viewing 15 posts - 22,156 through 22,170 (of 22,219 total)