Viewing 15 posts - 7,126 through 7,140 (of 22,226 total)
Well, before you rearrange your table structure, are you hitting a problem? I recognize that the existing cluster is not an optimal choice for the clustered index, but, is that...
"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 9, 2014 at 5:51 am
Because SQL Server doesn't compile a procedure on a line-by-line basis. It compiles the entire procedure, all at once. So, if you have syntax errors, you'll get an error, regardless...
"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 9, 2014 at 5:46 am
Assuming you've configured the multiple files appropriately (see all the blog posts over at SQLSkills.com on how to do this), no, there is no negative impact combining these two. If...
"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 9, 2014 at 5:44 am
You can simply open the system_health output file in the Extended Event explorer window, or just browse to the file from the Open File menu and double-click, SSMS will figure...
"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 9, 2014 at 5:43 am
I do think the risk is small (-ish), but unless we're talking domain hops, most networks these days should be able to handle running the backup across to a shared...
"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 8:24 am
And remember, the conversions, implicit or explicit, are only issues if they occur in HAVING, WHERE, & ON criteria. Data conversion within the SELECT doesn't matter.
"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 8:20 am
You can use the dmv, sys.dm_os_wait_stats. If you query that before and after running your query, you'll get a pretty good idea of what is causing things to slow down...
"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:57 am
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
Viewing 15 posts - 7,126 through 7,140 (of 22,226 total)