We're adjusting the server's memory by turning it off, adding or removing memory chips and turning it back on again. We're trying to make it as realistic a test as...

I think that's it! I should have realised that there would be one execution plan for the "If Exists () Or Exists ()" statement rather than two.

If I have the...

Thanks, that makes perfect sense, but I forgot to mention that neither condition A or B were met when the code was run, which means that both A and B...

The client's database has a nightly maintenance job to reindex.

Really, I was just wondering if there was a well known reason why

If A Or B

{Something}

might be massively slow while

If A

{Something}

Else...

It has only been reported on a client's live server, so getting the execution plan would be tricky, the wait type less tricky. But I'm afraid I don't have either...

Apologies. That should be comparing

If A Or B

{Do something}

with

If A

Begin

{Do something}

Goto EndIt

End

If B

{Do something}

EndIt:

Thanks for that. However, I'm not sure I understand its relevance. I haven't got an OR in a WHERE clause. What I'm comparing is

If A Or B

{Do something}

with

If A

{Do something}

If...

Really? Do you have any links to further details? That would be very helpful.

I'm working on a fairly large database where we have implemented data validation by a combination of unique indexes, check constraints, foreign keys and, where the validation is between data...

Oooh yes, that looks like it might be just the ticket. Thanks very much.

Thanks for the reference. I'm not sure that explained why you'd get fragmentation on an index consisting solely of an increasing identity column where only inserts were being carried out...

"Or defeated the Nazis."

Wow - that's some achievement! Did you need any help doing that?

The reason I'm interested is that I'm working on a project which was initially written in SQL 2000. Then, our use of temporary tables seemed to be causing a lot...

Gail,

Thanks for your comments. When I said "real table", I meant a permanent one, not one created as and when required in the way that you would with a temporary...

Would anybody like to outline the pros and cons of using a real table instead of a temporary table or a table variable? Surely SQL is better at managing these...