Viewing 15 posts - 9,946 through 9,960 (of 22,232 total)
By default, all things being equal, it shouldn't be taking longer with 2008 SSMS. So, you have to figure out what's not equal. Again, are you capturing an execution 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 25, 2013 at 8:45 am
Are you capturing the execution plan in the 2008 version of SSMS? Make sure you have the latest service packs installed on your server and on your client machine. Check...
"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 25, 2013 at 6:34 am
As Gail says, they'll be backed up. Then, when you go to restore, the part of the restore process known as recovery deals with uncommitted transactions, rolling them back as...
"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 25, 2013 at 3:33 am
In addition to backups, if you're developing the databases, I'd get the source for the structures and code into a source control management system. I'm pretty sure there ways to...
"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, 2013 at 4:26 am
It will help some. Who does the maintenance on your SQL Server instance? If no one, you probably need to get that set up. That'll give you a lot more...
"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, 2013 at 4:25 am
I don't quite get how those numbers are laying out. Sorry.
You have max degree of parallelism set to 0, 1024, 0, 0? It's just a single value.
"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 22, 2013 at 11:30 am
Sorry, I can't tell anything from that. You can export an execution plan as a .SQLPLAN file and then load it up to the web site. Then I can see...
"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 22, 2013 at 11:22 am
That's roughly the opposite of what you ought to see. Can you get both actual execution plans and post them so we can see what the optimizer is doing?
"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 22, 2013 at 9:16 am
Nope. That sounds pretty abnormal. I'd be concerned that there was something wrong with the server or the SQL Server instance. Check the configuration to ensure that you have memory...
"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 22, 2013 at 9:14 am
chandan_jha18 (3/22/2013)
As a side note, can you please let me know how to find the tables actually involved in the execution plan so that I can filter the unused ones....
"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 22, 2013 at 8:56 am
First thing, looking at the SELECT operator in your execution plan, you have a timeout. This means that the optimizer gave up on attempting to find a good enough 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 22, 2013 at 6:53 am
You won't be able to show that kind of a time period unless you first set up mechanism for capturing the metrics over time in order to aggregate it. Otherwise,...
"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 22, 2013 at 6:39 am
I'd have to test it to be sure, but you might be able to create an index with LastName as the leading edge and the other columns as part of...
"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 22, 2013 at 6:22 am
Since this is a post to a 2008 forum, you should know that you're already capturing deadlock information in the system_health extended events session that is running on your servers,...
"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 22, 2013 at 4:32 am
Multiple instances will absolutely affect performance, yes. You just need to monitor your systems to understand how much they will affect 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 22, 2013 at 4:29 am
Viewing 15 posts - 9,946 through 9,960 (of 22,232 total)