Don't forget about views: if you prefer that some people see a combined result as a table, you can use a view so they can see it as table, without...

Have you tried PAGE compression rather than going all the way to a columnstore format?

Agreed, you don't need nor want a separate table.

If you're having performance issues with the existing table generating your result using the PIVOT, then let's fix that issue, not create...

I'm with Phil.  Whenever I've seen this error it relates to the DEFAULT db specific for the user (or group).

The indexes could be critical.  Would you be able to post the DDL for the tables and the SQL queries?

SQL 2016 could be a big help in another way, it...

Exactly.  Just this:

SELECT MIN(StartDate) AS MinDate

FROM Schedule

WHERE WorkCenterID = 'LAY-W' AND ScheduleID = '5'

If there are potential index(es) on col_a and/or col_b, then I'd stick with the first style.  If not, the second is ok too.

OK. By default you'll always read the last committed value, using standard READ COMMITTED (hence the name, I guess :-)).

...or you will be blocked if RCSI is not enabled.

Your...

Yes, if userB uses WITH (NOLOCK) on the table(s), or READ UNCOMMITTED isolation level

But Scott, "IT Researcher" asked "is it possible for userB to read last committed values" and...

I'd just say "by accident".  If they want more details, they'll ask.

OMG !!

Wow .....the cross apply worked like a Charm.  and it was quick , even though now checking the table index is Clustered on identity, I...

Tell them.

Don't beat around the bush. Don't try to cover up. Just say it. "I messed up. I took the server down. Here's what I did by accident. I'm...

Yes, if userB uses...

Apologies, Scott.  You're correct.  You were talking only about the non-clustered indexes... but so what?  Same differences.  You're using twice as much disk space for those and for why? ...

I'd say it's still better to use 50% just to be safe.  For a non-clus index that is used only to get the clus key to do a...