Viewing 15 posts - 17,686 through 17,700 (of 22,219 total)
What about the parameters?
Does one of the servers have a different parallelism threshold than the other? How about the parallelism setting? ANSI connection settings? Um, memory allocations, any other kinds...
"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
April 17, 2009 at 6:58 am
If I understand the question, you can this to your code
...
--Previous parts of a procedure
SET STATISTICS IO ON;
EXEC something;
SET STATISTICS IO OFF;
--The rest of the procedure
...
"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
April 17, 2009 at 6:49 am
Another advantage worth considering are licensing costs. Once you've paid for SQL Server and have it running on a given machine, you can create instances to your hearts content. 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
April 17, 2009 at 6:46 am
There's a chance, just a chance, that the queries could still be in the cache. Try querying sys.dm_exec_sql_text to see if you can find the query. From there you can...
"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
April 17, 2009 at 6:43 am
Excellent. Glad I could help. And thank you for posting the solution. I hate wondering what worked.
"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
April 16, 2009 at 8:05 pm
Absolutely use the FK's. They protect the data.
I'm not even sure what you mean by "storing it as text." Do you mean that you'd just record what the relationships should...
"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
April 16, 2009 at 4:41 pm
I would simply run sp_who2 and see if it's being blocked by something and if so, what. If there's a long running transaction or lots of transactions blocking the resources...
"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
April 16, 2009 at 4:35 pm
Jeff Moden (4/16/2009)
Grant Fritchey (4/16/2009)
Jeff Moden (4/16/2009)
Thread softly and carry a big pork chop.You owe my company a new monitor.
Ha!
BWAA-HAA!!! "Let them eat thread!"
Evidently you're not supposed to spit...
"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
April 16, 2009 at 12:35 pm
Tara (4/16/2009)
insert SIRSdata
select R.*
from Budget..Hrbg as R , Revenue..BudHrbg as BD
where R.BudID= BD.BudID and R.servcdate between BD.startDate and BD.endDate
this query is taking too long to run, is there any alternate...
"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
April 16, 2009 at 11:33 am
Jeff Moden (4/16/2009)
Thread softly and carry a big pork chop.
You owe my company a new monitor.
Ha!
"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
April 16, 2009 at 11:26 am
If you know the values of StartDt & EndDt are likely to be, break them down into smaller chunks so that you're only moving certain date ranges.
"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
April 16, 2009 at 11:25 am
Jack Corbett (4/16/2009)
GSquared (4/16/2009)
"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
April 16, 2009 at 9:25 am
Grant Fritchey (4/16/2009)
Bob Hovious (4/16/2009)
First there was.... "The Thread".
Then came the "The Son of Thread".
Future Titles
The Other Thread
Revenge of The Thread
Return...
"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
April 16, 2009 at 8:25 am
Sounds like pressure on the memory. Were you capturing performance counters. Do you have Page Life Expectancy? That's a good measure of what's happening with SQL Server memory management.
"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
April 16, 2009 at 8:12 am
I'm sorry, but I really don't understand the question. Can you post a bit of sample code for what you're trying to do?
"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
April 16, 2009 at 8:06 am
Viewing 15 posts - 17,686 through 17,700 (of 22,219 total)