The newest version of Collections Management now includes CDA Express as a thank you for using Collections Management. CDA Express lets you archive your GL and PM company data into an archive company database. This has several advantages, such as speeding up your system, freeing up resources on your SQL and GP servers, and dramatically reduce the amount of time it takes to run complex reports in GP.
You can read more about CDA Express at the following article:
With both CDA Express and the full featured CDA, you can actually place your archive database on a completely separate data server. There are a few steps to do this, as you’ll need the SQL server to “see” the network location as an attached hard drive.
First, find the location where you will be saving your archive database on the shared network. Map this location to a drive letter on your computer.
Next, open up Computer Management (Control Panel —> Administrative Tools —> Computer Management). Go to Storage —> Disk management.
Click on Action —> Create VHD
Select the newly mapped drive, and name the file something easy to remember, such as Archive.vhd. Choose if you want it to be Dynamically expanding or Fixed (Dynamic saves space by using only what it needs, but Fixed tends to have slightly performance) and entering how big you would like the drive to be.
Using the Dynamically expanding size means that it will only take up to the amount specified as it needs it. The Fixed size option will required the whole 500 GB right away.
Next, right click on the newly created Disk and initialize it.
Choose the partition style. Most often it will be MBR:
Right click in the new opened area and choose “New Simple Volume…”
Go through the Wizard and choose the drive letter you will be using and complete the wizard:
Now I have a new drive to save the database files to:
Go back into SQL Server Management Studio. Make a backup of your Archive database. Then make as you are going to restore the database, but change the Files to the new location:
You will now see the archive database sitting on the virtual hard disk:
The archive database took up only as much space as it needed since in this example we set it to expand Dynamically: