It's a bit early in the morning for me to be thinking this hard but here goes...

Use a left outer join

then use a case to decide what data you want...

I dont think you want to use fetch prev, I think you want to create a temporary variable that holds the previous batch start time.  then you can use this...

There is a good explantion of different raid levels at

http://www.acnc.com/04_01_05.html

quote:

---

Mikey:

Say you have like in David's example a big amout of records containing dates... Say that the joins on that table still...

Something like that. I like to have the joined element clustered, it definitely helps join performance. Also, when you are using a where clause it is helpful to...

If you are 80% of the time joining on the identity then you will probably want that to be your primary key

If you are joining on identity and using the...

David, quick question. When you select from this table are you joining to it or from it? When you join is it based on the identity column?

If you...

I thought it was common knowledge/best practice to always put text columns last. No one is saying we should rearrange the table design at all, just explicitly select like...

someone said

I tend to save my clustered index for something that would benefit from it. Normally this would be the primary key but I don't feel there is much to...

It is going to be dependent on what you are trying to accomplish. The best bet is to use the execution plan and see which you beleive is better...

Some motherboards send interrupt requests to one CPU only. This can cause this issue.

First: With a Clustered PK the data is *always* returned in the natual table order, so order by is not necessary. Second: why do we need to get the...