SQL Server 2014 introduced a new cardinality estimation engine. Any migration from a version of SQL Server prior to 2014 to post 2014 has to deal with this issue. In...

It shouldn't matter, but go and get the latest cumulative update. You shouldn't be running RTM at this point.

I'm unsure what the issue is. I do this kind of monitoring...

Look down below in the details. Is there a second tab? I'll bet there is.

Causality tracking won't prevent it from capturing the deadlock graph. I think the issue likely lies in the is_system filter. You're not looking for system issues, you're looking for user...

You can't bypass it. If you really need everything in views (and not seeing your code, I can't support whether that's a good idea or not), then I'd suggest five...

Best to only ask a question once. Most of us look at a lot of forums, so we're likely to see it. Plus, any discussion will take place in more...

Pretty much yes. The index usage stats are just one piece of information. However, it's not dispositive information. It's a part of the whole puzzle. The whole puzzle very much...

The data in the deadlock graph includes the sqlhandle. You can use this against either the DMVs or Query Store (if it's enabled) to retrieve query information. The sqlhandle is...

So, if you're getting lots of deadlocks (massive performance hit by the way, it's not just about the deadlock itself, every time it happens, you're rolling back transactions, causing additional...

Looks like a pretty straight forward issue. You've got two different delete statements running from one process, looks like both reference the same lock_group_str and then the update is running,...

Seeks are great! Don't complain.

However, they're only great when returning smaller sets of filtered data. For very large data sets or no filtering, scans are better. You should see a...

So, the deadlock graph didn't upload. You'll need to do a little more formatting to get it here and/or post it to a file share somewhere and post the link.

Interesting. I've only ever tested it going to Azure SQL Database. I'm not sure why you'd need it for a VM migration unless it's somehow testing the upgrade from some...

Happy to hear that things are working. Come back with questions any time.

Don't reorganize ever. It's a waste of time. However, it's a particular waste of time on columnstore indexes. Rebuild or don't. That's it.