Viewing 15 posts - 13,066 through 13,080 (of 22,224 total)
GSquared (3/11/2011)
GilaMonster (3/11/2011)
I signed off two official design documents back at the bank as "Database Overlord". No one commented.
I, for one, welcome our new reptilian overlords ....
(Now I can't remember...
"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 11, 2011 at 11:23 am
You might want to start to look at tools like Visual Studio Team System or Red Gate SQL Source Control as a mechanism for implementing deployment processes that allow 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
March 11, 2011 at 9:29 am
Koen Verbeeck (3/11/2011)
I see what you did there 😛 :hehe:
You set 'em up, I'll knock 'em...
"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 11, 2011 at 8:07 am
I would look at breaking down the process and doing a chunk of it each night. Considering the size of your system, you should probably be updating the stats a...
"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 11, 2011 at 7:57 am
In general... I'd say that running FreeProcCache is almost never a good solution. If you rebooted the machine, the procedure cache was flushed. That is not maintained from one startup...
"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 11, 2011 at 7:51 am
Or do you mean the Management Data Warehouse? This is the MSDN/BOL entry on how to deploy that.
By the way, I agree, Red Gate's SQL Monitor[/url] is a great tool.
"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 11, 2011 at 7:45 am
mymail.default (3/10/2011)
ok. I assume this to be the "Audit Login" event.Thanks for all ur help.
Yes, that's right. Sorry for any confusion. Pulling stuff out of my brain is sometimes...
"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 11, 2011 at 6:11 am
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
Viewing 15 posts - 13,066 through 13,080 (of 22,224 total)