Setting up an Active and a Historical database
I would like to configure our installation to have multiple databases. The purpose of this would be to seperate the "active and planned" projects from the "Historical" data, and to set up a testing and training database that could be purged or overwritten and set back to a known backup status. We do not want to share activity or project codes between the "active and planned" database and the history because we want to purge all the project specific codes that got set up as global codes when we converted from P3.
We want to move projects from the "active and planned" database once or twice a year and then purge the unused codes that are no longer relevant. We are using MS SQL as the database. I need to set this up, and then move projects to the "Historical" database, and then run a report that tells me what codes are no longer in use in the "active and planned" database for deletion.