Viewing 15 posts - 10,156 through 10,170 (of 22,219 total)
Bhuvnesh (1/15/2013)
Grant Fritchey (1/15/2013)
as soon as the data changes or the inputs change, all bets are off.
yes i have also realized that for smaller set , we can see...
"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 15, 2013 at 5:12 am
You'll have to change the compatibility level.
"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 15, 2013 at 4:37 am
Updating statistics can cause a large number of reads if you're doing a full scan. But the number of writes is extremely small.
Backup and restore are almost exclusively I/O operations....
"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 15, 2013 at 4:37 am
Nothing like getting thrown into the fire. Welcome. We try to help out here as best we can.
From the sounds of it, no constraints especially, you're going to be dealing...
"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 15, 2013 at 4:32 am
And for more you can go to the books. SQL Server 2008 Internals by Kalen Delaney is one of my favorites.
"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 15, 2013 at 4:27 am
Yes, it's going to be a little bit random in the number of rows it returns. However, for a given set of inputs against a constant set of data, 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
January 15, 2013 at 4:26 am
It was a deadlock victim. So while it was trying to modify data, other processes came and caused a deadlock. You should just be able to rerun it. It's pretty...
"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 14, 2013 at 11:14 am
ben.brugman (1/14/2013)
Grant Fritchey (1/11/2013)
"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 14, 2013 at 8:34 am
It's worth mentioning that having a function like that on the ORDER BY can prevent index use. Depending on the size of the data set and the complexity of 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
January 14, 2013 at 5:12 am
No.
Everything I do publicly, my employer actually has some interest in. That's especially true for me, being a public rep for a company. But what I do privately, whether in...
"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 14, 2013 at 5:06 am
I'd check out the new execution plan and figure out what it's doing now. Just so you know in case there are issues in the future. You do have parameters...
"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 14, 2013 at 5:01 am
Bug aside, the only way to be sure what's happening is to read the execution plan to understand why it is doing each operation that it is using to retrieve...
"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 14, 2013 at 4:57 am
Buffer cache hit ratio is a poor indicator. The page life expectancy is pretty low though. I suspect you are hitting the disk a lot. Fragmentation may help at 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
January 12, 2013 at 3:25 am
Right, so as far as SQL Server is concerned you're partitioning to a single drive. Performance is pretty much guaranteed to be poor. Yours does seem abnormally poor, but poor...
"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 11, 2013 at 12:27 pm
Yeah, but is the SAN set to multiple, isolated LUNs for the partitioning? If not, partitioning is going to suffer more than just a straight access to the same set...
"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 11, 2013 at 8:17 am
Viewing 15 posts - 10,156 through 10,170 (of 22,219 total)