Alvin Ramard (12/8/2014)

That's news to me. A quick Google search found sources that agree with you and others that do not. Since one that agreed was a Microsoft...

No, you can't reset that flag on your own. It's done by running a successful backup. The indications are not that the last backup didn't reset the flag, rather that...

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...

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...

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...

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...

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...

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.

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...

Here's some additional info on what you might do to clean things up.

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.

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...

Any chance of posting the XML .SQLPLAN file, not this text plan?

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...

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...