Did anyone adjust the checkpoint interval?

WHY is it inefficient? Did you look at the query plan? How many records? What metrics are you using to determine inefficient?

If you are doing only a few rows...

No. The MAX will get the highest existing one and then the ROW_NUMBER will add a sequence from 1-N to that as an increment.

I asked my question because this...

1) Spread out your schedule to minimize overlap. I can't tell you how many times I see umpteen jobs starting at 00:00 (or on the hour) at clients!!! NEXT-NEXT-NEXT and...

No time to deal with all of your questions, but:

1) get the query plan that is running and see what it looks like. Compiled vs actual parameters? estimated vs actual...

I don't think they are off by that much, especially given the DISTINCT. How many total rows in the table? Did you check dbcc showstatistics to see how the numbers...

Luis Cazares (5/20/2016)

---

This should fix the concurrency problems, and a few pet peeves I have.

WITH cte AS (

SELECT o.*,

...

sql-lover (5/20/2016)

---

Thanks for reply

I...

I don't have your tables, so those queries are not useful to me to create the data. Like I said, you need to provide create table statements and inserts for...

David Burrows (5/20/2016)

---

DECLARE @InvoiceNo int = ISNULL((SELECT MAX(o.InvoiceNo) FROM Orders o),0);

WITH cte (ID,InvoiceNo)

AS (

SELECTo.ID,@InvoiceNo+ROW_NUMBER() OVER (ORDER BY o.ID ASC)

FROMOrders o

JOIN SetupAccountTypes a

ON a.ID = o.AccountTypeID

AND a.AccountType = 'COD'

AND o.DeliveryDate >=...

IO is not getting into RAM fast enough.

1) How much memory on the server? If it isn't the max allowed for your version of SQL Server that is the...

I read your post and I have absolutely no idea what you are looking for. Please provide some create tables, inserts for some data and expected outputs from said data....

Variables in ad hoc sql statements don't behave as you would think. Put this in a sproc and try it to see what happens. Then try both sproc and ad...

I strongly recommend you start with an actual value and not NULL, and make the column NOT NULL by definition. Otherwise you have the NULL bit dereference and MUCH worse...

I have no idea about your Nimble stuff, but the backup start and end times should be set by the actual backup process in SQL Server.