Viewing 15 posts - 11,851 through 11,865 (of 22,219 total)
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
It could be bad parameter sniffing (differentiated because parameter sniffing is going on constantly and helps you). You need to get a copy of the execution plan when the query...
"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:01 am
Read my book. It's down there in my signature.
"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 3:59 am
In general, a correlated sub-query in the SELECT list can lead to poor performance. You're usually better off finding some way to move that down into the FROM clause.
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
September 14, 2011 at 3:57 am
Of the year? I think I'd put it down to of the decade, but that's not what the contest was. Regardless, congratulations Jeff. You earned it! Can't wait for 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 3:40 am
A single file also means if the file gets corrupted, you lose one backup, not all of them.
"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 13, 2011 at 8:26 am
Jpotucek (9/13/2011)
I AM doing regular Databases backups Full nightly Database backups and Transaction Log backups where appropriate and depending on the SLA with 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 13, 2011 at 8:21 am
Piling on a bit, because it's a point worth making.
Most backup products are not aware of the fact that SQL Server has this pesky little function called a transaction. So,...
"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 13, 2011 at 6:54 am
Bob Fazio (9/12/2011)
The reason why we are leaning towards the patch, is because I think everyone agrees, one bad...
"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 12, 2011 at 3:41 pm
Viewing 15 posts - 11,851 through 11,865 (of 22,219 total)