Viewing 15 posts - 7,651 through 7,665 (of 22,219 total)
SQLRNNR (7/30/2014)
Grant Fritchey (7/30/2014)
I'm going to throw one more datatype thing out there.
The use of GUIDs as your Clustered Index will COST you plenty of space. Changing the 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
July 30, 2014 at 8:31 am
Sean Lange (7/29/2014)
Actually normalization (more tables) causes slower performance.
I want to let this go, but I just can't.
No. Not true.
Everything, everything, within a structured storage engine comes with trade-offs...
"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 30, 2014 at 8:23 am
Pretty sure the key word there is VIEW, but we could also add STATE. Same thing with VIEW DATABASE STATE.
"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 30, 2014 at 8:15 am
Koen's excellent recommendations on compression are really the only way to reduce the size of data stored other than deleting the data.
Your other options are to try to tweak...
"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 30, 2014 at 8:12 am
It could just be that your statistics were out of date on the old tables and the new tables, with more up to date statistics, are generating new execution plans....
"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 30, 2014 at 8:04 am
While I'm sure some of the people here on SSC can help, I would strongly recommend that all licensing questions go directly to Microsoft. Regardless of what some person on...
"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 30, 2014 at 8:01 am
Koen Verbeeck (7/29/2014)
Grant Fritchey (7/29/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
July 30, 2014 at 5:01 am
msandico 57892 (7/29/2014)
Grant Fritchey (7/29/2014)
msandico 57892 (7/29/2014)
Grant Fritchey (7/29/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
July 29, 2014 at 9:21 am
msandico 57892 (7/29/2014)
Grant Fritchey (7/29/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
July 29, 2014 at 8:46 am
As long as we're talking about straight T-SQL commands, you should be fine. If you start trying to access objects directly through SSIS, you may hit issues. Forward compatibility is...
"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 29, 2014 at 8:17 am
mqbk (7/29/2014)
Grant Fritchey (7/29/2014)
So, 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
July 29, 2014 at 6:46 am
Nothing but opinion follows. Take due notice and govern yourselves accordingly.
If we're talking a database administration job working anywhere outside academia (or evidently, the government), the degree itself is unlikely...
"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 29, 2014 at 6:29 am
1tb isn't quite into the VLDB range, but, once you get past around 3-5tb, you need to start looking at things like SAN snapshots. But, even that could be problematic...
"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 29, 2014 at 6:18 am
While you can connect to it, you won't be able to access 2014 objects and may run into issues with objects that contain 2014 only constructs (clustered columnstore).
"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 29, 2014 at 6:14 am
The issue, whatever is causing the slowdown, could very well be within SQL Server. Absolutely. But the timeout itself is controlled at the application connection setting.
So, to troubleshoot this, I...
"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 29, 2014 at 6:12 am
Viewing 15 posts - 7,651 through 7,665 (of 22,219 total)