If you've got QueryStore enabled, you could confirm if you are in fact experiencing regressed plans. From there you can force SQL Server to use a plan that worked better...

Oh I made a dumb mistake. I had something else in the where clause for the list of IDs that would indeed make particular accounts have a sum of zero,...

It sounds like you already have it set, but mixed mode authentication is on, right?

The only other thing I would suggest doing is running a trace and setting up checks...

As a fellow standard user, I feel your pain 🙂

We use logshipping for one server at our DR datacenter and replication from our production server to our reporting server. So,...

I was worried about that. I ran the below script which didn't list the report server DB.

SELECT 
   [rs].[destination_database_name], 
   [rs].[restore_date], 
 ...

This article states you should keep MAXDOP at or below 8 with 8 processors with 1 NUMA node. In my experience with a server with near identical resources, I've...

Thank you Jeffrey Williams,

The last two columns in yours is exactly what I was after.

Phils would also work with a little bit of tweaking.

I appreciate you two

Thanks for the reply, ScottPletcher. That is indeed what I plan to do for the most part: have a secondary copy of the original table to make my changes. Sounds...

I wanted to follow up with this in case someone else runs into this issue.

The 'fix' if you can call it that ended up being dropping the columnstore index on...

Thanks HandyD,

I can't believe I missed these articles. Your four scenarios are exactly what I want to account for. The only...

Thank you Jeffrey! That was exactly what it is. The user is a member of another group that happens to have admin access to this server.