You know, now that I think about it I realize: this is a classic de-normalization exercise.

You would have to keep it within the Dynamic Sql batch, as per ksullivan's example.

Utsab: I think that you should just tell the developer that they need a Uniqueidentifier/NEWID().

Jeff Moden (3/21/2008)

---

Heh... I suppose you could convert NEWID() to Varbinary and then BigInt but you'll always end up with 19 digit numbers that may be either positive or negative...

Another thought: You will want this Friends table to contain copies of the information that your site will need to display their friends list. So it should look...

OK, my bad....

Easily remedied, G², just add an attribute column to indicate the direction...

wojo (3/21/2008)

---

thanks guys, my main concern is performance i dont really care about space. this table will be heavily used (inserts and selects). if i go with the indexed view...

This is an ages-old question about any system or service, and although the details are specific to each individual type of system or service, the individual causes of service failures...

As I recall, you want just one hierarchical date dimension which is to be shared by all of the date-based fact columns.

The parameter table trick works as you described it, so long as there is no danger that the receivers of the parameters will get confused about which set of parameters...

How do you know that it "failed"? Maybe it is still running or is hung? Or maybe it it exited without an error, but not when or where...

Good point, I missed the "frequently" in the OP.

In that case, it is almost certainly...

johnsql (3/21/2008)

---

As specified in BOL , from type INT converted to type DATETIME, we do not need to cast or convert because such conversion is implicit. I do not know...

Depends on your priorities and concerns. If performance is your priority, then probably dual entries are the way to go. If disk space is your top concern, then...