If this db is tightly bound to the user databases, maybe so. If not, it might warrant it's own AG. Either way, as Beatrix noted, if this depends on reading...

Ignore these stats. If they are useful and always created, you could drop them and recreate them with better names, but it's really not worth the effort.

Overall, this seems reasonable to me. I like separation of each server/instance to its own account and its own backups. Anyone logging into a server could run IE, and someone...

Added: https://www.sqlservercentral.com/Forums/Database-Design/Security-and-Auditing

There isn't a general "performance is worse" statement that I've seen, or that I think can be made. The impact is very workload dependent. It seems some of the other...

Thanks, post updated.

This gives you an upper bound on backup speed/lower bound on completion.

I hate any rules on passwords. I can understand some length limit, but let's get that > 100.

Also, don't break on $[~, etc.