Viewing 15 posts - 7,081 through 7,095 (of 22,219 total)
Check the security settings to see how you're connecting to the database and how the view is connecting to the linked server. It sounds like a disconnect is occurring between...
"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
December 15, 2014 at 4:24 am
You need to gather more data. Run a query against sys.dm_exec_requests to see if there are blocked or blocking processes on your server. Also look at sys.dm_os_wait_stats to see what...
"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
December 14, 2014 at 5:00 am
Most especially get the wait statistics while the backup is running in order to understand exactly what is causing things to slow down. sys.dm_os_waits_stats will show you a cumulative view....
"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
December 13, 2014 at 5:23 am
You're still stuck with third party tools for doing this type of thing.
"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
December 13, 2014 at 5:18 am
You can't really undo an in-place upgrade. You would have to uninstall everything and then restore your databases from a backup. You're pretty much making a commitment by doing your...
"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
December 13, 2014 at 5:17 am
Jeff Moden (12/11/2014)
Grant Fritchey (12/2/2014)
npranj (12/1/2014)
The 42% cost is Clustered Index insert cost. There is one CI and 4 NCI on this table.
All the other costs are from...
"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
December 11, 2014 at 9:26 pm
Have you tried clicking on that link? It will open a graphical plan within SSMS.
But, if not, you can always query sys.dm_exec_text_query_plan. That will output just a raw varchar(max) column...
"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
December 11, 2014 at 12:50 pm
That's news to me. I'm not a backupexec expert, but I've worked around it for years. We were able to have it run all sorts of things without automatically running...
"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
December 11, 2014 at 9:28 am
Good gosh, don't do option 1. That will put additional stress on your production system, removing memory, fighting for CPU and disk access. No. Option 2 is pretty much 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
December 11, 2014 at 8:37 am
Yes. You're going to want to have that date value as a date. Otherwise, you'll have to parse that string and it will prevent index and statistics use leading 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
December 11, 2014 at 8:26 am
Glad to hear the solution. I was also going to suggest looking into bad parameter sniffing, but it's probably just the stats.
"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
December 11, 2014 at 8:22 am
Don't do it.
Instead, give them permissions to create extended events[/url]. It's much more lightweight and much less fear of bringing down a production system.
"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
December 11, 2014 at 8:20 am
No, I'm pretty sure that's a code issue. They're not cleanly disconnecting.
"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
December 11, 2014 at 6:57 am
Run a query against sys.dm_os_wait_stats before and after running the query. It'll give you a pretty good idea what the query is waiting on.
Also, when you're running queries against sys.dm_exec_requests...
"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
December 11, 2014 at 6:56 am
You need to check the condition of the server when you're getting the timeouts. Are there lots of connections, or only a few. Of those connections, are any blocked or...
"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
December 10, 2014 at 8:58 pm
Viewing 15 posts - 7,081 through 7,095 (of 22,219 total)