Viewing 15 posts - 13,486 through 13,500 (of 22,227 total)
If it was running good until Sunday, what changed on Sunday? New code release, service pack, new client, new users? Something had to have happened to 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
January 26, 2011 at 12:14 pm
Gail, congrats on getting a spot on the new 24 Hours of PASS.
"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
January 26, 2011 at 9:28 am
To calculate usage over time, you'd need to gather metrics over time. You can use Permon to do this.
I can also suggest (full disclaimer, I work there) Red Gate's SQL...
"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
January 26, 2011 at 9:26 am
I had a UDF I used to use as well. With smaller data sets it works fine. But if you start to grow them, I really suggest using the tally...
"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
January 26, 2011 at 9:22 am
What happened to the available bit in Table c?
The thing is, unless you're maintain a history of availability so that all entries to Table B are inserts (in which case...
"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
January 26, 2011 at 8:48 am
Take a look at this article by Jeff Moden[/url]. He shows how to use a tally table to solve the problem you're describing. It's a very efficient approach.
"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
January 26, 2011 at 8:40 am
I agree. I can't see why you would need to join to that table unless there are other fields and functions you're not showing.
"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
January 26, 2011 at 8:34 am
You should be able to, yes. Why not?
"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
January 26, 2011 at 7:50 am
We haven't run into anything either. Check the documentation on Microsoft's web site to see what is being changed. Run tests on it prior to running it in production. That's...
"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
January 26, 2011 at 7:49 am
You have to make a choice. What does an empty string mean as an integer? Is it NULL? Is it 0? You have to supply something because a number can't...
"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
January 26, 2011 at 7:48 am
If you only need the list of UKEY, why are you selecting all the other columns?
Not having all your code to understand completely what's going on, I may get this...
"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
January 26, 2011 at 7:28 am
The only suggestion I can make is to start using Roles within the database in addition to AD groups. Yes, if the AD server goes offline it can and does...
"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
January 26, 2011 at 6:11 am
It doesn't make any sense that the time would vary, a recompile fixes the time, but you're looking at identical execution plans. Based on the situation you describe, the exec...
"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
January 26, 2011 at 6:02 am
There's no way to directly manage the size of cache. If that's all the cache that is getting used, that's all SQL Server needs. I'd double check to be sure...
"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
January 26, 2011 at 5:57 am
Hey, whoa! If you take away the phrase "It works on my machine" you've just eliminated 2/3 of any conversation I have with developers. What are they supposed to say...
"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
January 26, 2011 at 5:45 am
Viewing 15 posts - 13,486 through 13,500 (of 22,227 total)