Like any other problem in the system, most of the time it's queries. I'd use either Query Store (set up per database) or Extended Events to capture query metrics. Identify...

Mmmmm... Not digging that answer, but I'm not stupid enough to start an argument with Kendra.

That doesn't even remotely cover just how horrific performance gets with these things. I would...

If you lock it, no one can access it. That will stop the deadlocks. But then, the phone calls start "WHY CAN'T I GET MY DATA".

I'm with Mike. What is...

Nope, nope, nope. That book is either wildly wrong, or you may have misread a section of it. A database only has to have two files, data & log. You...

Well, your drive has 93.6gb free. Assuming you have auto-growth enabled on your files, you have room inside the database too. Take a look at sys.dm_db_file_space_usage to determine the...

1. Nope. The multi-statement UDF is effectively a table variable. It lives within the context of the query it runs within. The in-line table function is just a parameterized view,...

Not going to lie, I was hoping more people got this wrong.

Just remember, while this may be tough, constraints are what keep us from getting dirty data, and you are already dealing with dirty data. Cleaner data means better analysis. Better...

I have not implemented this, but I believe what you're looking for is covered in the Activity Logs. If you were only monitoring a given "server" within Azure, you...

Honestly, for a few documents, probably filestream. For lots of documents as you're describing, don't use SQL Server. It's not going to do a good job. Determine if you need...

There's no easy way to do this other than querying all the tables... Or, ensuring that the code that is generating your inserts is using appropriate data. The application shouldn't...

Not enough to go on.

First, fundamentally a deadlock is a performance problem. If all the locking occurs so fast that there's no interference, you will never see deadlocks. So, I...

It's funny that the biggest concern is actually guaranteed to happen. You are going to disrupt your existing work flow. That's sort of the point. I also see this as...

SQL Server doesn't manage it's memory in one giant pool. It segments the memory management into different areas with different purposes for efficiency of the management.

The plan cache is the...