Still sounds like a monitoring solution looking at stuff, especially since it's against every database.

Turn on query monitoring (Extended Events first, Query Store second, DMVs third, ignore everything else) and see what queries are being run on the system. Done.

Nope. That information isn't provided from AWS. You get what they give you, and that's it. Sorry to be the bearer of sad tidings. However, the information they do give...

TRUTH!

I'd start with the login. Which one is running the query? That'll give you a lot of information. It looks like a monitoring query. It might be SentryOne itself. If...

This is a tough process. First up, testing is your buddy. Plan to test your queries, a lot, before you just disable indexes willy nilly. Next, small changes. Only take...

This is a tough process. First up, testing is your buddy. Plan to test your queries, a lot, before you just disable indexes willy nilly. Next, small changes. Only take...

Are you getting more and more data? If so, that's the challenge (note, not a problem or an issue, just something you have to deal with). And yeah, it may...

Oooh, that's a good idea.

I truly hate hearing the term applied to me. I simply don't believe it. Can't. It's just not true. However, it does happen. And oh boy, you can see the...

The new kids prefer the term data engineer over DBA. Work & responsibilities are the same, but they really don't like the DBA moniker for some reason.

Well, I'll be there. Causing trouble. Saying stupid stuff. You know, the usual.

I see a day coming, and soon, where the work that today is done by a junior, or even a mid-level, DBA, will be readily replaced by AI. My concern...

Following on to what Steve said, when I'm doing sales & support work at Redgate, talking to clients, they'll say something like "You should do this with Product X". My...

Nope.

"The name of the secondary database must be the same as the name of the primary database."

That's from here.