Viewing 15 posts - 12,151 through 12,165 (of 22,227 total)
I'm with Gail on this one. Fixed values are much better. You always know exactly how much will be added and you can anticipate the additional load that will place...
"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
August 5, 2011 at 4:57 am
Nope. Especially not a unique index. If it's unique, it's unique. If someone types Heme, Hem or Ham, they're all going into the database.
"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
August 4, 2011 at 3:14 pm
I have to ask, why no backups?
"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
August 4, 2011 at 3:13 pm
After you read the manuals, and that really should be where you start, you might swing by this article[/url].
"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
August 4, 2011 at 3:13 pm
Rebuilding every six weeks or so might be OK. The real question is, how often are your statistics maintained? Those age much quicker than indexes fragment.
"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
August 4, 2011 at 11:50 am
Chris Kitchen (8/4/2011)
Thanks for all your replies, at the moment there is nothing set in stone, we are just reviewing the different options available:
1. Set "Identity" to "Yes" for...
"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
August 4, 2011 at 6:43 am
danymorales17 (8/4/2011)
Let me ask you all this, what about Developer/QA servers. What if 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
August 4, 2011 at 5:52 am
I'd start with a search in the web site that you're on. We've got years of articles, published 5 a week. I'll be there are a ton of SSIS 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
August 4, 2011 at 5:47 am
I generally don't worry about how much I'm reading or writing on a database, but whether or not the reads or writes are slowing down. Instead of focusing on 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
August 4, 2011 at 5:44 am
If you don't get everything you need from Gail's excellent articles, you might want to pick up a copy of my book on query tuning. It might help.
"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
August 4, 2011 at 5:41 am
No difference at all. You run a server side trace output to a file, then you open the output file using Profiler. That's it. You can then open the perfmon...
"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
August 4, 2011 at 5:39 am
You should check for open transactions. You might have a process that isn't committing properly. I ran into some rogue code that did that & it filled the drive before...
"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
August 4, 2011 at 5:38 am
My first choice in this situation would be SSIS as well.
But, you could look at third party tools. For example, Red Gate Data Compare[/url] could be scheduled to move 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
August 4, 2011 at 5:26 am
Connections come from the application, so that's where the code for reconnecting would have to reside.
"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
August 4, 2011 at 5:24 am
If you're programmatically determining the key value(s), then no, having identity values isn't going to help that I can see.
Now, how you're determining that value could lead to issues. Are...
"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
August 4, 2011 at 5:23 am
Viewing 15 posts - 12,151 through 12,165 (of 22,227 total)