G2, your issue seems to be different in nature from my client's. They took the hierarchy as an initial set of data and then joined it to between 3...

I have a client with a similar situation. On their system we developed an orghierarchy table that gave both the up and down listing for each org and use...

Here is my take on reusability:

1) most code doesn't actually GET reused because a) all devs don't know about it, b) devs don't bother checking to see if their particular...

To be most correct, you should update all statistics using the fullscan option.

GSquared (3/31/2008)

---

I've used UDFs in cases where the select logic was so insanely complex that a single query just couldn't do it (which leaves out views) and it needed to...

1) the first reponse to this type of question is we need to see the code and table scripts.

2) how many rows are being updated by the code?

3)...

I advise my clients to avoid UDFs (other than very simple, non-table-accessing scalar ones) like the plague. They FAR too often lead to row-by-row processing under the covers. ...

I have read that article several times over the years and missed that VERY important section every time!! What a nugget of info to remember!

If you mean truncate as in BACKUP LOG mydb...

Mirroring suffers from the same crippling amount of a deltas that index maintenance can cause and in addition cannot be compressed either automatically or manually. This is rectified in...

You have not given us nearly enough information to answer the question.

1) Raid level (given subsequent to OP).

2) Stripe size.

3) did you sector align the partitions?

4) ntfs allocation...

1) Log shipping will die a horrible death the first time you do an index maintenance on a fragmented database.

2) If you DO go with log shipping, roll...

For the sake of completeness, ApexSQL Diff also does data syncing. Embarcadero has ChangeManager, but this doesn't to my knowledge do data (yet). IIRC I have stumbled across...

Tobi White (3/25/2008)

---

Actually after rereading what I originally posted and rereading TheSQLGuru's post I don't know why I took offense at all. My bad TheSQLGuru, it actually does look like...

See here (http://sqlblog.com/blogs/linchi_shea/archive/2007/08/07/reduce-the-contention-on-tempdb-with-trace-flag-1118-to-enable-or-not-to-enable.aspx) and read the associated links too. T1118 doesn't seem to affect performance on 2005 like it did with 2000.

Also, unless you have a REALLY amazing I/O...