Viewing 15 posts - 11,851 through 11,865 (of 22,227 total)
I would assume performance for querying is going to start degrading, but honestly, I've never seen a system with 150,000 tables before, so I couldn't tell you when.
I suspect, really...
"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
September 15, 2011 at 5:59 am
Erik Hansson (9/15/2011)
"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
September 15, 2011 at 5:53 am
I'm at a bit of a loss here. Common and best practices are to split up tables, apply unique constraints, primary key constraints, foreign key constraints and build clustered indexes....
"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
September 15, 2011 at 5:50 am
That's just a set of processes. There is lots of information there, but little data.
Personally, I don't like using that because it's so messy. Instead I run queries against 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
September 15, 2011 at 5:47 am
That's one of the tougher ones to set up. You need to capture statement level events. When capturing statement level events, you're going to get lots and lots of 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
September 15, 2011 at 5:41 am
Excellent stuff everyone, thanks. I especially liked the DTA & the Profiler GUI. Excellent stuff.
"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
September 14, 2011 at 11:14 am
mtillman-921105 (9/14/2011)
Grant Fritchey (9/14/2011)
"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
September 14, 2011 at 11:03 am
mtillman-921105 (9/14/2011)
Grant Fritchey (9/14/2011)
I'm tasked with writing another article. This one is all about 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
September 14, 2011 at 10:52 am
Changing the topic for a moment, I'd like to beg some ideas from the group, again.
I'm tasked with writing another article. This one is all about the scary, crazy stuff...
"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
September 14, 2011 at 10:38 am
bobznkazoo (9/14/2011)
Grant Fritchey (9/14/2011)
Bigger question for me, why are you storing numbers in...
"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
September 14, 2011 at 9:07 am
Ninja's_RGR'us (9/14/2011)
Grant Fritchey (9/14/2011)
Although, the current database was frequently very small and very responsive, the situations where you had to create cross-database joins were a pain.Why?
The syntax is simple, right?...
"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
September 14, 2011 at 4:58 am
That depends, do you know that the values are unique across systems? If not, you will hit problems.
Bigger question for me, why are you storing numbers in a varchar field?
"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
September 14, 2011 at 4:12 am
I'm with you. I think it makes a lot of sense. Especially when you consider how small this particular data set seemed to be. The one big issue for me...
"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
September 14, 2011 at 4:09 am
I'm with Paul. I've done it both ways successfully, but the only way that splitting the database really worked well was if the structure was changed in the archive system...
"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
September 14, 2011 at 4:08 am
Jan Van der Eecken (9/13/2011)
Steve Jones - SSC Editor (9/13/2011)
They could even go to something like cloud services for production data and local servers for historical data.
Steve, please enlighten me,...
"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
September 14, 2011 at 4:05 am
Viewing 15 posts - 11,851 through 11,865 (of 22,227 total)