Viewing 15 posts - 19,516 through 19,530 (of 22,219 total)
Well, I'd say you have to reign it in. First, you need to get the core code into source control. After that, you can start working to label builds 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 30, 2008 at 12:19 pm
Jeez. I read the question twice and I still don't notice this:
But virtually all of the selects are based on a Datetime column.
That should probably be the leading edge...
"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 30, 2008 at 11:40 am
The question I would ask myself in order to answer your question, what is the most common access path? What will be used more often than anything else to 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 30, 2008 at 11:37 am
Personally, I'd suggest using a tool that works well with scripts and source control. The three that come to mind are DBGhost, in which I have no experience, Red Gate...
"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 30, 2008 at 11:09 am
How about disappointed. I was hoping for more. I guess I've been spoiled by Red Gate's SQL Prompt.
"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 30, 2008 at 11:04 am
Are you kidding, thank you. I hate posting bad information.
"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 30, 2008 at 10:13 am
I must be regurgitating bad stuff again. Sorry. It's when it's a delimited list that it behaves like that, right?
However, I did a little looking around IN clauses don't work...
"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 30, 2008 at 9:49 am
It depends...
IN basically is an OR statement. It's one of those hidden RBAR (row-by-agonizing-row, TM: Jeff Moden) operations because it's going to check each row of the IN clause against...
"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 30, 2008 at 8:32 am
ruyfigueiredo (9/30/2008)
I have an database with 250MB and a Log File with 24GB.
After i reconfigure the Autogrowth i have to made...
"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 30, 2008 at 8:24 am
On top of what these guys have very correctly told you, put a limit on the growth of the database so that it won't fill the drive. A full file...
"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 30, 2008 at 6:11 am
You'll have to drop all foreign key constraints against the table first by using
ALTER TABLE OtherTableName DROP CONSTRAINT ConstraintName against all the related tables. Then you can use ALTER...
"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 30, 2008 at 6:06 am
You have to have a way to differentiate which value belongs with which row. I know this is probably not exactly what you're looking for, but something like this 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
September 30, 2008 at 6:01 am
With these estimated plans, there's almost no difference. Some of the estimated costs are slightly different and the location of the table scan of 'RO' changes between the two, but...
"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 30, 2008 at 5:36 am
I guess I don't understand the question. The storage engine does the data retrieval, including sorting and aggregating the data, as you said. What is the concern with where 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
September 29, 2008 at 1:12 pm
The proc doesn't look so complicated that a RECOMPILE would take six seconds... Hmmm.... You may have to go to old-fashioned tuning. What do the execution plans look 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
September 29, 2008 at 1:09 pm
Viewing 15 posts - 19,516 through 19,530 (of 22,219 total)