Viewing 15 posts - 6,526 through 6,540 (of 22,219 total)
Yep. 100% by design. Isn't the optimizer the coolest thing ever.
"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 26, 2015 at 3:40 pm
Drenlin (3/26/2015)
Phil Parkin (3/26/2015)That's exactly what the compatibility level is for, though it does come with downsides: all of the new features in 2014 are turned off for the databases...
"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 26, 2015 at 3:30 pm
Yet Another DBA (3/26/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
March 26, 2015 at 3:26 pm
I agree with everything that Gail said.
Well, except that you ought to be using extended events instead of trace.
But yeah, you may be hitting waits, CXPacket waits are not, all...
"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 26, 2015 at 3:18 pm
The index DMV, sys.dm_db_index_physical_stats, could cause blocking if you're asking for a detailed report. It's very intrusive.
I haven't seen or or heard about other DMVs causing blocking, yet.
"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 26, 2015 at 5:30 am
I'd really focus on the execution plan. I suspect the MAX itself isn't causing issues but rather the GROUP BY.
One way around it would be to try getting a TOP...
"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 25, 2015 at 11:43 am
I would try running the Upgrade Advisor against the database. I'm not 100% sure you can, but that will tell you specifically what won't work. You can also try 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
March 25, 2015 at 11:40 am
Assuming you have a logical or natural primary key, I'd look to the MERGE statement as an easy, although not necessarily fastest, way to get this done. That assumes 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
March 25, 2015 at 11:38 am
EMarkM (3/25/2015)
Pretty much the first step in any installation document I write (if the organisation doesn't have one, or amend if they do) is to create a Windows...
"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 25, 2015 at 6:46 am
Since INTERSECT does distinct values, why would you also need the DISTINCT word in each of your queries?
But, what Gail said. No way to tell you what's going on without...
"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 25, 2015 at 6:34 am
You could shut down the service (although if you can do that, you ought to be able to connect to it) and the copy the database files to a safe...
"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 25, 2015 at 6:32 am
I guess I misunderstood the question. I'm with Gail.
"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 25, 2015 at 6:28 am
If you can't connect as a windows logon, it's gone. I sure hope this isn't your production server.
"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 25, 2015 at 4:29 am
Yeah, it can be. sp_updatestats is an OK way to update statistics on most systems for most statistics. But some systems and some statistics are going to need a more...
"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 25, 2015 at 4:28 am
The indexes may be fragmented AND the stats are out of date. Rebuilding indexes takes care of both. But, the most likely issue is that the stats are out 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
March 24, 2015 at 7:55 pm
Viewing 15 posts - 6,526 through 6,540 (of 22,219 total)