Hi - have you tried testing...

I'd suspect that hte problem is the clustered index on hte GUID.

Try changing the clustered index to a monotonic value - such as an IDENTITY column

SSIS into a reporting database, and do your reporting from that a viable option?

Google "Dimensional Modelling" (specifically, "A dimensional modelling manifesto" for a kick off) and Kimball.

That's your starting point

Oh, oh - can't believe this one's been missed so far? Or did I just bang my head on the desk 'till it went away?

"Well - it's obvious that...

Bob Hovious (4/8/2009)

---

How about?

1. Everyone knows that databases don't scale.

2. Everyone knows that SQL Server is slow.

3. We...

More like way too many programmers with way too little clue in their...

Don't use Table or View as your data access method when loading or transferring data. This apparently uses a cursor behind the scenes, and as a result kills your...

May I ask why, exactly, you would be doing that rather than have a quantity column containing the number of items?

CrazyMan (1/22/2009)

---

100 k/Day not that much data, this shouldn't cause any problems, the way you do is fine, other ways are having a backup and restore, which will leave you...

Could you also post the production and reporting table definitions please?

the advice about driving off a cliff

GilaMonster (1/14/2009)

---

This is not the first time that you've criticised the free help that you're getting here. If you...

sqlservercentral (1/6/2009)

---

We have a table which will be subject to large volumes of INSERTs from web transactions - e.g. several per second at busy periods of the day. We need...

GilaMonster (1/7/2009)

---

And to add to that.

Any backup not tested cannot be considered a valid backup. If it's worth...