I have a situation whereby I recieve many rows of transactional data from a hardware device. I analyze this data and turn the previous day's data into a report. As a result, my application is often combing the entire table to generate reports, but it only really needs to deal with the previous 72 hours data. I run an indexing script daily (rebuilds and re-organizes), and running this on tables in the same database causes the database to hang quite a bit for my report app. So, My thinking is to get the archived data out into a new database that can be managed seperately to this database, thus reducing the hang-time of this database due to re-organizing and re-indexing multiple indexes of a database consisting of millions of rows.I have a situation whereby I recieve many rows