The bookmark lookup on TRNDTL_BTS08 is chewing up 90% of the cost of the query. The actual update changes a single row (according to this execution plan) but it has...

PeterG (9/15/2008)

---

bskt_skudtl has 650k rows. the specific week i am updating has approx. 17k rows.

The table i am retrieving from (trndtl_bts08) has 150mil rows.

i know how to display...

Matt Miller (9/15/2008)

---

Make sure to go after the multi-threaded aspect of testing. Meaning load-testing with single threads or single connections won't show some of the real uglies out there...

Jeff Moden (9/15/2008)

---

Heh... must be a parallel universe... going through the same thing just now. Our guys are writing a bunch of ETL using C# because they think it's...

Have you looked at the execution plans to verify that the indexes were used at all?

For the clustered index, be sure that the column (or columns) that you put...

Jeff Moden (9/15/2008)

---

Must be the same "sun" our guys are singing to. I talked with a couple of the more senior C# developers at this new job of mine......

Different situations can cause either one to operate in a more optimal fashion.

Take the advice offered above. Do as proper a normalized design as you can to start. Then worry...

True, but use it the way Peso posted it.

jay holovacs (9/15/2008)

---

This is such a silly turf war.

I spent a number of years doing C++ (and loved it). TSQL and C# are very different tools and they solve very...

One thing I'm aware of in our organization, and I think it's universal. Object oriented developers loathe TSQL. I've watched blood pressures visibly rise in meetings when the discussion comes...

With only a little modification, you could use the code in this article:

http://www.sqlservercentral.com/articles/T-SQL/61461/%5B/url%5D

Performance, assuming a proper data design, good indexes, well written queries, etc., is not an issue. Supporting hundreds of users running queries is supporting hundreds of users running queries. It...

True.

The problems...

As long as those two databases live forever side-by-side... None.

As soon as you put them on...

If the applications are not sharing substantial portions of data, different databases. Further, when you put them on different databases, don't allow cross-database queries. This is PAINFUL experience speaking.