Viewing 15 posts - 12,961 through 12,975 (of 22,232 total)
Krasavita (3/23/2011)
2000 records in table total. Nothing wrong with my machine
OK. but if you're still looking for an answer, can you supply some more information. Fine, you're pulling 2000 rows,...
"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 23, 2011 at 3:37 pm
annasql (3/23/2011)
And also when I right click the job, I can see manage schedule. But how can I export the list 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 23, 2011 at 3:35 pm
Brandie Tarvin (3/23/2011)
A-Kon 22, the biggest Anime convention in the U.S., will be throwing a launch party for The Ladies of Trade Town anthology (edited by Lee Martindale)....
"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 23, 2011 at 12:23 pm
It really depends on the query, the structure of the table, the indexes on the table, the number of users on the system and the queries they're running, memory 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 23, 2011 at 11:14 am
Depending on the query, the optimizer is blazingly fast. But, it's still not zero, I get it. Usually when you hit a limit based on how a tool behaves 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 23, 2011 at 10:26 am
No, you can't really avoid the compile process. If you try plan forcing you're at least guaranteed which plan you get.
"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 23, 2011 at 9:44 am
Not without execution plans to compare. It's just too hard to know what's going on since we're not sitting there.
"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 23, 2011 at 9:24 am
Jack Corbett (3/23/2011)
Grant Fritchey (3/23/2011)
SQLkiwi (3/23/2011)
Grant Fritchey (3/23/2011)
"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 23, 2011 at 8:36 am
I still think something occurred during the restore. It looks like litespeed was functioning and the server had access, but something happened. Get to the full error log and 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 23, 2011 at 8:35 am
Yeah, I'd say it sounds fairly reasonable. As long as the Posh script isn't adding to the overhead on your systems. You can just use perfmon to spit out 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
March 23, 2011 at 8:10 am
That doesn't look like a complete error message. Since the error is from LiteSpeed, I'd check the log there and see what you have.
"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 23, 2011 at 8:07 am
Jeff Moden (3/23/2011)
Grant Fritchey (3/23/2011)
...duck tour should be a blast.Heh... not sure duck hunting season is open right now. 😛
The last time I spelled it properly, DUKW, people were confused.
"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 23, 2011 at 7:35 am
SQLkiwi (3/23/2011)
Grant Fritchey (3/23/2011)
"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 23, 2011 at 7:13 am
And if you toss in something like multi-statement table valued functions the cost can be shown as zero when it is in fact extremely high.
Costs are indicators, but they 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
March 23, 2011 at 5:55 am
Well, you can try plan forcing. that allows you to take a valid plan and make the engine use it when you run the query. It's not executing the plan,...
"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 23, 2011 at 5:53 am
Viewing 15 posts - 12,961 through 12,975 (of 22,232 total)