SQL often "parses ahead" for errors.  SQL detects that the db doesn't yet exist and so can issue errors.

I usually use dynamic SQL to get around these types of errors:

Since we have NO previous knowledge of your tables and how they're used, we need specifics to make any reasonable judgements.  It's rather frustrating when we ask such things to...

We have dedicated Sr. People for optimization and they have been doing it for more than a decade for some good clients. So we trust their understanding for...

That's correct.  You don't even need to include Operations.OpOrder in the SELECT results and you can still ORDER BY it.

In general, you can exec the proc that way.

However, since that proc does absolutely nothing, you'd be better just removing all the code that execs it.

I still have my doubts on the clus index keys.  But you could be right.

By the way, are most of the tables clustered on an IDENTITY column?  If so, you...

Yes, you're quite right, it will use more CPU. ...

• This reply was modified 4 years, 11 months ago by ScottPletcher.

Oracle used to use Grid (which is much more powerful than just the cluster setup in SQL Server).  But big $$$$$$$.

Could you use SQL Developer Edition?  If it's business prod, you can't, but if it's just something you're doing on your own, you can.  And that edition has full capabilities.

that is where some disagree.

on my 1500 production db's 220 have RCSI enabled - and most new db's are being created with it enabled unless the team requesting...

Oh BTW, On top of compression, you may also want to fiddle around with following settings to see what works best for you !

--Media Set Options
...

(1) As always, the first step is to make sure you have the very best clustered index on every table of significant size.  That is not an easy thing to...

Hmm, the first part of the Answer you chose is correct.  But keep in mind that the second part, the "P.S.", is not.

that is where some disagree.

on my 1500 production db's 220 have RCSI enabled - and most new db's are being created with it enabled unless the team requesting it...

(1) Have you page compressed any (or better yet all) of the really large tables?  And used COMPRESS/DECOMPRESS if it's clob data? [If you're on SQL 2016+ then even Standard...