Viewing 15 posts - 20,071 through 20,085 (of 22,224 total)
It depends on the severity of the error. Higher severity errors cause a disconnect of the offending process. Those cannot be trapped.
For the other procedures, in SQL Server 2005, you...
"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 2, 2008 at 6:23 am
That sums it up very well.
By the way, you're posting a SQL Server 2000 question in the SQL Server 2005 forum. While this question was fairly generic and the answer...
"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 2, 2008 at 6:21 am
A full and hardy congratulations to you both. You deserved it and you earned it.
"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 2, 2008 at 6:17 am
Yeah, yeah, I used the "depends" right at the beginning and added weasel words "in all likelihood"
I covered my behind.
😛
"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, 2008 at 6:40 am
You have to put a "GO" statement between these two scripts. This seperates the two scripts into seperate commands so that they are processed independently by the server. That allows...
"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, 2008 at 6:27 am
SrikanthSv (7/1/2008)
If the amount of data which the stored procedure hits is huge then use the temp tables. Using temp...
"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, 2008 at 6:15 am
We've got some development teams advocating for it's use right now. I'm trying to build a strong case on either a correct usage (and that DOES NOT mean object databases)...
"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, 2008 at 5:32 am
Really? You're using it? Any words of wisdom on either living with it well or avoiding it entirely?
"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, 2008 at 5:26 am
Nah, go take it. If it's really a question & answer type of test, you'll probably pass. It's likely to be one of those filters that HR puts in place...
"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, 2008 at 1:20 pm
Richlion (6/30/2008)
"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, 2008 at 11:36 am
In addition to that list of links, which is pretty good, I'd just say to get very familiar with Profiler. One of the best books you can get is "Inside...
"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, 2008 at 11:23 am
Hey guys,
You think you have problems now? Wait until nHibernate and all it's ilk are in your development systems. Now you'll have object specific databases with dynamic SQL. Tuning headaches...
"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, 2008 at 7:59 am
It's probably parameter sniffing. As everyone else has already said, get the execution plans and see what the differences are.
"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, 2008 at 7:54 am
I even had a guy go off on a huge lecture that we were asking too many SQL Server specific questions (for a SQL Server specific position) because we should...
"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, 2008 at 7:53 am
Hey guys,
I've been out of town. Thanks for keeping the conversation going. Especially since you've been supplying answers much better than the ones I would have supplied.
"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, 2008 at 6:48 am
Viewing 15 posts - 20,071 through 20,085 (of 22,224 total)