Jeff Moden (7/7/2009)

---

Paul,

Very cool. The additional sequence table prevents the need for a SELECT or comparison in the code at all and that's important for both concurrency and...

GilaMonster (7/7/2009)

---

Exclusive table locks.

Sequence table has much the same problems as the MAX(ID)+1 solution. Either you...

Tao Klerks (7/7/2009)

---

So, the follow-up question: can anyone think of or provide any cases/examples where inequalities might perform worse than other logically equivalent queries, for any given limited dataset, in...

Tao Klerks (7/7/2009)

---

I'm still very interested to see whether anyone can tell me more about the difference between the following three cases though:

- WHERE (Type > 1...

No, because I don't think it's a great fit for your problem.

Consider Gsquared's idea first.

Sequence tables can work well in some cases, but they require great care to...

If by 'helping you out' you mean 'write it for you' then...no - not me 😛

(I already have a job!)

The best way to learn stuff is to take an idea...

For SQL2K5, memory usage per connection is roughly (3 * network_packet_size + 94) KB. So for a 4096 byte network packet size (the default), that's around 106KB per connection,...

No that's not right at all...what you should do...

😀 heh 😀

Just...

SET XACT_ABORT ON is one approach - though it has behaviour quirks of its own.

TRY...CATCH is your friend here.

Paul

You could also use a 'sequence table' - that is, a separate table that holds the next sequence value for each combination.

I'm just saying you could.

Whether it makes sense or...

I only looked quickly, I admit, but if you want to preserve log information over a transaction boundary, why don't you use a table variable instead?

Table variables aren't affected by...

😀 That's...

So Elliott,

Which isolation level would you use to avoid that problem 😉

Paul

You'll like this Jeff 🙂

Code windows mangle it a bit so it is attached too - recommend anyone interested opens that instead.

Paul

-- Creates and drops objects in tempdb only

-- Requires...

Just in case anyone is in any doubt, the specific error "Non-Yielding IOCP Listener" is indeed directly related to an inappropriate setting for server max memory - though I have...