Viewing 15 posts - 10,921 through 10,935 (of 22,219 total)
Steve Jones - SSC Editor (5/8/2012)
I assume most of you saw it, but for those that didn't, my wife quit her job[/url].
Wonderful news. Best of luck to her and 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
May 8, 2012 at 3:40 pm
The problem isn't the wild card at the end of the criteria. It's the wild card at the start. That requires a scan of the column, which can lead 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
May 8, 2012 at 8:18 am
If you're interested in knowing when the plan was placed into cache, which would be the compile point of the procedure, you can get that from Dynamic Management Objects (DMO)...
"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
May 8, 2012 at 8:16 am
ashkan siroos (5/8/2012)
"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
May 8, 2012 at 6:34 am
capn.hector (5/8/2012)
"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
May 8, 2012 at 6:11 am
You have to have a clustering service running. That's not the same thing has having a standard failover cluster. You can read a little more in the AlwaysOn FAQ.
"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
May 8, 2012 at 5:21 am
I sincerely try to use the correct data type for the situation. Could I just plug int or bigint anywhere rather than think about if a tinyint or smallint can...
"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
May 8, 2012 at 5:06 am
Case statements in the WHERE claue are going to lead to some less than satisfying execution plans. I'd suggest breaking down into different queries rather than do 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
May 8, 2012 at 4:16 am
In general, this is one of those "Doctor, doctor! It hurts when I do this" moments. The correct response being "Don't do do that."
It's pretty rare to have an emergency...
"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
May 8, 2012 at 4:12 am
Keep monitoring the system, thousands and thousands of blocking occurrences will flit by. All that matters is when blocking is excessive, meaning, too much time is spent waiting for resources...
"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
May 8, 2012 at 4:10 am
GilaMonster (5/8/2012)
Bhuvnesh (5/8/2012)
"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
May 8, 2012 at 3:53 am
My experience is the same, a regular refresh to ensure that data reflects production as much as possible. The issue is, this is only viable when the databases are 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
May 8, 2012 at 3:52 am
Unless we're talking about some type of actual error, no, there's nothing to see for a query that behaved, but didn't do what you wanted.
"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
May 7, 2012 at 11:01 am
No, I wouldn't say every table needs it at all. It's a business call. BTW, what about UpdateDate and UpdateBy? And are we doing physical deletes? Instead we could use...
"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
May 7, 2012 at 10:58 am
You can run it on any environment. As you've already been told by Gail, you must run it in Production. When? Find the time when you have the least load...
"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
May 7, 2012 at 5:06 am
Viewing 15 posts - 10,921 through 10,935 (of 22,219 total)