In a nutshell, they can do anything in the cloud (around VMs & AD I mean) that they can locally. There's no reason why it would just utterly fail to...

Implicit transaction is always on. You can't turn it off. You're focusing on the wrong thing. The issue with deadlocks is a combination of performance and coding. From the performance...

I hate rebrands/renames. I think it creates confusion and often doesn't make anything better. Either you execute well or you do not and people know that, regardless of name.

However,...

And Extended Events.

Total agreement on DBATools.

You could look to Change Data Capture as a way to see all the data manipulation on the system. It does require quite a bit of setup & maintenance...

Honestly, look to a 3rd party monitoring solution.

Up front, being clear and open, I work for Redgate who makes a monitoring tool.

However, what you're trying for just isn't available, out...

Damn Johan, great article. I missed that one.

You're not paranoid when they're out to get you. And they're out to get us.

Nothing, anywhere, is perfectly secure. There are always vulnerabilities. We just don't always know what they are until it's far too late.

However, I still land where I always land on...

In addition to changing the capture mode to auto, look to custom to get a little more control, possibly.

When connections do not happen in SQL Server, there's nothing in the error logs because there really isn't anything for SQL Server to report. However, that's not saying that there...

Because of the row size limitation in SQL Server, I had to split the columns of a data warehouse table. The combined size of the rows exceeded the permitted...

What performance problem are you trying to solve by splitting the table? Reads are likely to go up, not down (depending on quite a few details). Writes may go down,...

Nothing jumps out as problematic, so it is going to be down to knowing the structures and execution plan. Without that, we can't even guess.

Strong suggestion.

Restore the database as everyone has suggested. Then, before you change the compatibility level, turn on Query Store. Run the database for some time with Query Store enabled. A...