Viewing 15 posts - 7,261 through 7,275 (of 22,221 total)
From the slides on the precon I did last week at Summit, this is just a list of table restrictions:
Restrictions
No LOB
No CLR
No user defined types
No VARIANT
No ROWVERSION
No foreign keys
Must 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
November 11, 2014 at 10:21 am
No. No, no, no. Don't do that. Everything just doesn't belong within the in-memory sphere. If you're not experiencing significant slow downs due to latch waits, you really shouldn't even...
"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
November 11, 2014 at 10:05 am
No, there is no way to "push" a table to be in-memory. You must create an in-memory table following all the restrictions and then move the data into that table....
"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
November 11, 2014 at 8:57 am
In addition to the good suggestions so far, you should also factor in the number of transactions each supports. The recovery process of the restore operation when transactions are rolled...
"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
November 11, 2014 at 7:22 am
Thank you for the kind words.
I don't know that I would sweat adding the additional 8 bytes. It's not that much. Yes. it'll be a little wider, but if...
"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
November 11, 2014 at 4:40 am
You have to make a determination for hardware through a whole slew of factors. How much data do you anticipate? How many users will there be? How many transactions will...
"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
November 11, 2014 at 4:08 am
Did you try connecting with the dedicated admin connection (DAC)? I've seen that work in similar circumstances. And yeah, I think your devs might be out to lunch on 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
November 11, 2014 at 3:58 am
I'd go right by 2012 and use 2014. The licensing costs are about the same, and the number of enhancements to 2012 functionality around things like columnstore, statistics, statistics maintenance,...
"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
November 11, 2014 at 3:52 am
It's a little more complex than that. You also have to take into account the logical, or business, identifier for each row. This is sometimes referred to as the natural...
"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
November 11, 2014 at 3:50 am
And, in the event of failover, async means no guarantee of intact 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
November 10, 2014 at 11:00 am
I'd take a look at extended events. You can just capture the events that exceed a certain value for run time and then have them forwarded to just about anything...
"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
November 10, 2014 at 8:16 am
Glad to hear it was narrowed down. It sure didn't sound like a physical problem. Good luck on the fix.
"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
November 6, 2014 at 6:11 am
Glad to hear it's proving useful. Let me know if you have questions.
"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
November 4, 2014 at 6:05 am
One of the first, and most important resources, you've already found. SQL Server Central is one of the best places to get more learning. Not only from the forums like...
"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
November 2, 2014 at 12:55 pm
With no information, I'm with Lynn. It's impossible to say what you need to do to improve performance.
But, whatever other forum you were on is partly correct. A view, a...
"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
November 2, 2014 at 12:50 pm
Viewing 15 posts - 7,261 through 7,275 (of 22,221 total)