I'd recommend trying the approach below.

Specifically, the code below:

1. Changes the fillfactor to 99.  80 is way too small (unless you do massive updates to almost the entire table later?!...

• This reply was modified 5 years, 3 months ago by ScottPletcher. Reason: Added ONLINE = OFF to list of changes I made. I forgot to mention this before, but I did make the change

1. Not generally available. If an index was created by adding a PRIMARY KEY constraint, sys.objects would have the create time of that index.

2. Yes. For example:

SELECT

t.name AS table_name, i.name...

Something like below is what you need to do.  If the column names are the same, you will need to make sure each has a different name in the final...

Why not create the clustered index on the temp table before it gets loaded?  That would save extra writing / rewriting of data, I would think.

Do you mean a separate row for every column that changed?  That's massive overhead.  And if you get the column name(s) dynamically, that's really insane overhead.

Have the first step in the job start another job that monitors the starting job.

For example, if you're trying to monitor JobA, the first step in JobA starts job JobA_monitor...

Wouldn't "total invoices - total payments received" be the receivable...

I assumed by "for each Discharge", you wanted to see every discharge, with only their before and after appointments.  If that's not what you wanted, please clarify your requirements.

            
December 3, 2020 at 6:18 pm
            
#3816632

            
            
                                                
        

Are you using data compression?  If not, that should be the first thing to check toward reducing total table size.

If you want to improve overall performance, we'd need to look...

I prefer this method too, with the minor change that the column name should be used rather than a hard-coded value:

SELECT CONVERT(CHAR(8),...

I think a synonym would allow you to create a completely new view without affecting the current one.  Then, when you had the new view fully tested out, with all...

I'd say use CDC as that will require no changes to any existing table that already has a unique index.  Presumably the vast majority of your tables already have at...

I don't know if SQL Server still allows cpu affinity to be used, but if it does, you might look into that and thus licensing fewer than 32 cores.  That's...

I think you will have to drop them and re-create them (once/if sp_refreshview doesn't work).

Script them out, being sure to include any permissions or other system table / metadata entries...

Look in the SQL error log, you might be able to at least some more details about what task timed out, though admittedly not a lot of details.

Typically timeouts are...