Viewing 15 posts - 8,761 through 8,775 (of 22,226 total)
CXPACKET waits in and of themselves are no big deal. They're just indications of parallelism occurring within your system. Now, you may be seeing parallelism for some queries that are...
"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 7, 2014 at 6:53 am
You might want to take a look at this article I wrote in SimpleTalk. It goes through how to retrieve versioned data[/url] from the table. Assuming you can identify 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
March 7, 2014 at 3:41 am
Right there with Gail. This is something I'd test the heck out of this before I got anywhere near production. It's far too big a change to do it any...
"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 7, 2014 at 3:36 am
Sqlsavy (3/7/2014)
How to reduce fragmentation <30?
IndexTypeavg_fragmentation_in_percent
CLUSTERED INDEX 97.67442
CLUSTERED INDEX...
"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 7, 2014 at 3:27 am
sqlbuddy123 (3/6/2014)
Rebuild index doesn't update all the statistics. It updates only index statistics. Column statistics that are not part of index are not updated.
True, but we know they have...
"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 6, 2014 at 6:00 pm
It's hard to know for sure, but on a guess, statistics. I'll bet they're not being well maintained on either machine. Minimum, start with sp_updatestats. After that, you may find...
"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 6, 2014 at 4:28 pm
For a quick hit, I agree with Lowell, pull information out of the cache. You can see what's going on there. For longer term though, you need to look into...
"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 6, 2014 at 4:23 pm
sqlbuddy123 (3/6/2014)
Or just run sp_updatestats to update the stats.And check for any Blocking, Memory, CPU, Disk utilization on the server. Also check for any waits on the server.
--
SQLBuddy
But... If they...
"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 6, 2014 at 4:21 pm
It looks like you've missed something on the security screens. Make sure, minimum, you add the current user. That's actually not always the best way to go about it, but...
"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 6, 2014 at 4:08 pm
I really don't care what naming standards we have. Let's just make them clear and let's enforce them. After that, it's all good.
I have a presentation where I spend about...
"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 6, 2014 at 4:05 pm
SQL Guy 1 (3/6/2014)
"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 6, 2014 at 3:51 pm
If it's an update statement, you could be seeing contention from other resources doing reads at the same time as you're trying to modify the data. That's a pretty classic...
"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 6, 2014 at 12:18 pm
Abu Dina (3/6/2014)
"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 6, 2014 at 11:09 am
Abu Dina (3/6/2014)
"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 6, 2014 at 9:14 am
Just backing up what's been said. You can get extremely granular on the security, and I'd get as granular as possible. If you can, limit all access to the data...
"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 6, 2014 at 7:58 am
Viewing 15 posts - 8,761 through 8,775 (of 22,226 total)