Viewing 15 posts - 18,046 through 18,060 (of 22,219 total)
It sure sounds like that's what you need. Yes, it's running on the server, but so is your database. You just point the scheduler at the DB you want and...
"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
March 10, 2009 at 6:18 am
One thing worth noting, those costs are estimates, even in the actual execution plan. They can accurately portray which parts of the query are most costly, but not necessarily. 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
March 10, 2009 at 6:04 am
The jobs are created in the SQL Server Agent. It's a seperate service that runs along side SQL Server (assuming you're not running Express). It allows for scheduling to run...
"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
March 10, 2009 at 5:59 am
If you use the 2000 and the 5000 field together, you're going to get warnings and potentially errors because you'll exceed the page length limit. MAX bypasses that issue. I'd...
"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
March 10, 2009 at 5:50 am
I suspect using OPEN TABLE is the issue. If you go out & bounce around in Google, there are a lot of people experiencing problems with it. I couldn't find...
"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
March 10, 2009 at 5:28 am
I suspect using OPEN TABLE is the issue. If you go out & bounce around in Google, there are a lot of people experiencing problems with it. I couldn't find...
"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
March 10, 2009 at 5:00 am
Mohit (3/9/2009)
People here on SSC are great in helping, but when posting such large SQL code blog. It makes it difficult for them to help 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
March 10, 2009 at 4:51 am
Jeff Moden (3/9/2009)
Heh... I didn't say anything about evil intent... I just meant to say the original post is correct... the questions are definitely getting worse and more ignorant.
I am...
"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
March 10, 2009 at 4:33 am
Wow. I'm amazed that runs in 54 seconds.
Without reading every single line, the one thing I'm noticing is, you don't really have the concept of JOINS down. Take this:
SELECT ID...
"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
March 9, 2009 at 12:50 pm
All right! Lynn is turning into one of those old school saints who wades in & beats the snot out of the unbelievers.
"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
March 9, 2009 at 11:56 am
Just because the connections are from the same SSMS instance doesn't mean they have the same settings. One of those connections is showing what I consider normal color coding 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
March 9, 2009 at 10:48 am
See, you might get to 80 tables too.
Glad you found it.
"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
March 9, 2009 at 9:46 am
You do need to be very careful about using table variables. But, if you're dealing with very small data sets that would be scanned anyway, regardless of statistics, then table...
"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
March 9, 2009 at 8:32 am
Interesting question... I'm not sure it'll help, but you can get the actual logical and physical reads by query for the queries that are in cache using sys.dm_exec_query_stats. Generally I...
"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
March 9, 2009 at 6:31 am
We once had a query that was joining 80 tables. It took about two minutes to recompile and, because of the nature of the data, it was recompiling about every...
"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
March 9, 2009 at 6:08 am
Viewing 15 posts - 18,046 through 18,060 (of 22,219 total)