Viewing 15 posts - 13,081 through 13,095 (of 22,232 total)
No, you won't see an ExistingConnection event for connections that are not yet existing. Also, don't run the Profiler GUI against your production system. While trace events are pretty safe,...
"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
March 10, 2011 at 5:56 pm
muthukkumaran (3/10/2011)
mymail.default (3/9/2011)
A single stmt stored proc (the stmt is basically a view from many tables) takes about 11-12 sec. from an app. However, it runs instantaneously in SSMS.
Any ideas...
"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
March 10, 2011 at 5:55 am
Or you can get the properties form the Connection event in a trace, even from the Existing Connection event. They show in the text column. You can also get 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
March 9, 2011 at 7:32 pm
Check the connectoin settings, specifically the ANSI settings. When these are different, you will get different execution plans for the same query.
"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
March 9, 2011 at 5:31 pm
did you compare the execution plans? That'll tell you what's going on better than anything else.
"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
March 9, 2011 at 5:30 pm
ksharpe (3/9/2011)
Here is the query:
SELECT [ProductID]
...
"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
March 9, 2011 at 12:11 pm
Sounds like you're not table qualifying the columns in the WHERE clause. Add the table and you should be fine.
"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
March 9, 2011 at 11:01 am
tgarland (3/7/2011)
"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
March 9, 2011 at 10:55 am
Which? Three different things were mentioned.
"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
March 9, 2011 at 10:51 am
sqldba_icon (3/9/2011)
Grant Fritchey (3/9/2011)
"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
March 9, 2011 at 10:50 am
So for each column in a 200 column table, you need to get a row from a different table in order to understand what that column actually is? Yikes. 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
March 9, 2011 at 8:39 am
You're in a great position for a side-by-side upgrade. It's the better approach for upgrading anyway. Install the 2008 server, restore the the 2000 databases to it and then do...
"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
March 9, 2011 at 8:23 am
Based on what you wrote (and yes, I read it too), you have two options. First, set up a serveri-side trace as Gail has already suggested. Second, you can try...
"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
March 9, 2011 at 8:21 am
We've been using it quite a while with no issues. I suppose it's remotely possible that you could mixed data if you had a lot of transactions all trying 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
March 9, 2011 at 8:12 am
In general, the way you can tell something is parameter sniffing is not simply if it runs faster or slower, that could be contention or any number of other things....
"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
March 9, 2011 at 8:05 am
Viewing 15 posts - 13,081 through 13,095 (of 22,232 total)