Viewing 15 posts - 5,866 through 5,880 (of 22,219 total)
You may have found the difference then. If this query needs to execute in parallel and production has more CPUs than Dev, that would explain why it's slower in Dev.
"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
July 7, 2015 at 9:26 am
I'm just surprised you didn't get a table spool in 2008 with a recursive CTE. That's pretty common.
"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
July 7, 2015 at 5:10 am
What's the clustered index on the tables? I'll bet it's the OID column. If so, it can eliminate partitions. If the other column in use has no indexes or only...
"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
July 7, 2015 at 5:09 am
CXPACKET waits are just an indication of parallel execution. They're neither good nor bad. What other waits are being experienced? Are both production and dev set to the same number...
"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
July 7, 2015 at 3:16 am
BL0B_EATER (7/3/2015)
Koen Verbeeck (7/3/2015)
Grant Fritchey (7/3/2015)
That reminds me of the old dot com days. It was expected that everyone was going to work like pigs, nights & weekends. Most 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
July 3, 2015 at 7:04 am
:alien:
<singing> One of these things is not like the others... </singing>
"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
July 3, 2015 at 7:02 am
thbaig (7/3/2015)
Grant Fritchey (7/3/2015)
"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
July 3, 2015 at 6:07 am
krypto69 (7/3/2015)
Capture the wait statistics when the procedure is run in order to understand what...
"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
July 3, 2015 at 6:05 am
Almighty (7/3/2015)
but we can use profiler remotely or as u said by using TSQL right ? extended events are good but for earlier version profiler was better idea
Nope. Running...
"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
July 3, 2015 at 6:02 am
GilaMonster (7/3/2015)
TomThomson (7/3/2015)
But don't make the mistake of thinking that all-nighters are always a sign of problems, or long hours (how can long hours be "heroic"?).
No, I'm not talking...
"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
July 3, 2015 at 5:59 am
Almighty (7/3/2015)
USE PROFILER .. TO FIND OUT WHAT HAPPEN S AT FIRST TIME THEN ANALYIZE THAT
This is actually really bad advice on two levels. First, running the Profiler GUI...
"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
July 3, 2015 at 4:06 am
It could be compile time on the query is very high which can cause some blocking, or that it's loading a lot of data into memory, again, possibly causing blocking....
"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
July 3, 2015 at 4:02 am
If the execution plans are the same then it's likely down to resources. Take a look at the waits statistics before and after the run in order to determine 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
July 3, 2015 at 3:56 am
HanShi (7/2/2015)
Grant Fritchey (7/2/2015)
"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
July 2, 2015 at 3:51 pm
GilaMonster (7/2/2015)
Do you get the feeling that IT people, especially ones at the top-end of the field, 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
July 2, 2015 at 3:49 pm
Viewing 15 posts - 5,866 through 5,880 (of 22,219 total)