Wouldn't you want just the network?  The recipients are email addresses, not phone numbers afaik.

@recipients = @N,

WHERE 
    D >= DATEADD(MINUTE, DATEDIFF(MINUTE, 0, GETDATE()) / 15 * 15, 0) AND
    D <  DATEADD(MINUTE, DATEDIFF(MINUTE, 0, GETDATE())...

For the ~100K rows in the tmp table, what percent range of the DeliveryTimetableID values in the larger tables do they represent?

That is, if the min/max values of DeliveryTimetableID in...

SELECT B.InsDtTime, A.RunDate, A.AID, A.AValue AS NewValue, B.AValue AS OldValue
FROM #tblTest1 A
CROSS APPLY (
    SELECT TOP (1) *
    FROM #tblTest2 B
...

• This reply was modified 5 years, 3 months ago by ScottPletcher. Reason: Corrected bugs in the query

Hmm, unless your data involves most of the table, I would think SQL could use a MERGE join rather than the HASH join for all those rows.  Would you be...

Everything we do today is affected by punchcards, and then by COBOL. Look at how 00 programming still assumes a procedural model.

Are you surprised that all animals have DNA?...

  IF (
        (
            (ABS(SIGN(@Var1-@VarA))) 
 ...

Similar to what Grant mentioned, I'd suggest creating a table to help manage the process. Run a process every day to update the table with...

Similar to what Grant mentioned, I'd suggest creating a table to help manage the process. Run a process every day to update the table with the next...

In the old days, particularly with PL/1, we would do the multiple IF's. Because it was easy to slip a new punchcard in the deck when we found we...

> we renamed the sql error log out file in agent properties <<

I think that would require a recycle of SQL Server.  You don't need to do that.  You should...

Try better clustering in a test system somewhere.  You might be pleasantly astounded by the results.

Table dbo.TSys_Lookup_Date D should almost certainly be clustered first on [Date].

Try clustering dbo.T_DeliveryTimetableItem and dbo.T_DeliveryTimetableItemResolvedCost...

Similar to what Grant mentioned, I'd suggest creating a table to help manage the process. Run a process every day to update the table with the next day's planned...

In a single execution, the gain may be small, bring it up to 100K/Sec and that...

• This reply was modified 5 years, 3 months ago by ScottPletcher.

Waiting for locks is normal in SQL Server (or any other relational db).

Whether the waits are excessive is a different q.

Since you've provided no details, to reduce bad effects of...