Viewing 15 posts - 7,126 through 7,140 (of 22,219 total)
Here's some additional info on what you might do to clean things up.
"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 8, 2014 at 4:17 am
Sounds like you've set up a WMI monitor within SQL Server, but you're not managing the data within it appropriately. Here's the documentation on this from Microsoft.
"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 8, 2014 at 4:14 am
I'm just going to pile on and suggest really strongly that you ensure you have backups in place, that you test your backups by running a restore to another server...
"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 7, 2014 at 7:11 am
Any chance of posting the XML .SQLPLAN file, not this text 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
December 6, 2014 at 3:58 am
Just define the JOIN criteria. Let SQL Server handle the rest. It will be best if there is a foreign key between the two tables and that foreign key is...
"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 6, 2014 at 3:55 am
Nope. That's an active log based on stuff currently occurring the system and things in cache within certain dynamic management views within the system. If you want to track those...
"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 6, 2014 at 3:50 am
lmacdonald (12/5/2014)
Do you monitor lock timeouts and does it often go above the default threshold of 1? I am asking because we...
"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 6, 2014 at 3:47 am
Luis Cazares (12/5/2014)
"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 6, 2014 at 3:44 am
I'd suggest putting in a request for it. It might not be that hard to implement. I'll put in a request from my side too.
"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 6, 2014 at 3:40 am
Oh heck, I thought I was on the Data Compare page. Sorry about that.
Yep, no report on the Data Compare command line. Again, sorry.
So script or script file won't work?...
"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 5, 2014 at 8:27 am
something is seriously baked on that server.
It's pretty abnormal. I've been working with VMs in Azure for years. And, because I'm doing lots and lots of testing and development, not...
"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 5, 2014 at 8:22 am
Perry Whittle (12/5/2014)
ian_massey (12/5/2014)
But I don't have any access to the log file...
"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 5, 2014 at 8:19 am
I've usually found single_user to problematic. That's why I prefer restricted_user. But then, you have to have had your apps set up correctly. If everyone is 'sa' or 'dbo' (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 5, 2014 at 7:58 am
You should be able to set a switch that outputs as a report. Here's the documentation showing how that works. You would want /Report.
I didn't know we had a command...
"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 5, 2014 at 7:55 am
I'm with Ed. It looks like they are doing log backups. So, they are right. If you were to introduce a different set of log backups, it could cause issues...
"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 5, 2014 at 5:40 am
Viewing 15 posts - 7,126 through 7,140 (of 22,219 total)