The db that table was in already had space allocated but that had not been used yet.  Therefore, SQL can allocate that space to a table without having to get...

RAM doesn't look too short there, but personally I'd add more if you could.  RAM is the cheapest overall performance boost you can get.  And bump up tempdb size if...

dup, removed

Update T --<<-- *must* use T here (the alias and NOT the table name) to be safe
SET ACTIVE=CASE WHEN S.user IS NULL THEN 'N' ELSE 'Y' END
FROM...

(1) Cluster the "FF" table on ( FileDate, ISIN ) (if it's not already clustered that way).

(2) Some of the JOIN conditions are out of place.  Change this code:

            
August 22, 2023 at 2:41 pm
            
#4268207

            
            
                                                
        

Not enough info provided for us to be able to say.  (1) Is SQL indicating that it's short of memory?  (2) How large are  your databases? (3) How many simultaneous...

It's likely the fragmentation is having some effect on overall performance by causing some small additional I/O.

To clarify, for a single keyed lookup, the index performance is not affected at...

Select * from Table T1

JOIN TableT2 on (T1.A IS NOT NULL AND T1.A =T2.A) OR (T1.A IS NULL AND T1.B = T2.B)

Also how do I check if the table has had any options set for SP_TABLEOPTIONS such as 'LARGE VALUE TYPES OUT OF ROW'. I doubt this would be the...

When you ALTER a column, SQL creates a new column to store the data, it doesn't re-use the existing space for the new column.  You'll need to do some type...

My other feeling was that having it run multiple times (2, 3, 4?) at the start of the month could be deceptive / confusing to people looking at...

@jonathan-2:

This method of determining Tuesday:

DATEPART(weekday, @CurrentDate) = 3

requires a specific DATEFIRST setting to work correctly.  Many business have locations around the world, so it's safer to use a...

Fair enough.

In that case, let's create a view that has the merged tables for anyone to use.  That is much cleaner.

Yikes, if a developer can't join/merge two tables with distinct date values to a combined table, they need additional training, and pronto.

Personally I prefer a nonworkdays-only table (I don't call it a "holiday" table because sometimes it's a nonwork day but not a holiday (such as for a power outage, etc.)).

That...