Posted by peterc on 06/22/06 23:56

I have an existing database with approx 500,000 rows and accessed by a
few hundred users per day creating approx 1,000 new records per day
plus typical reporting - relatively low volume stuff for SQL Server.

I'm about to add a process that will be importing data daily from
legacy databases and summarizing it for reporting purposes, integrating
it with the existing database. This volume of data will be considerably
higher, perhaps 100,000+ rows per day, which will be deleted once it
has been summarized and the results written to some intermediate
tables.

Is there any concern about mixing different levels of volume within one
database? As I'll be creating lots of rows daily and then deleting them
I was wondering about fragmentation, transaction logging etc. and
whether having this processing in a separate database from the main
application would be 'better'.

[Back to original message]