Hi again Paul,
1TB sounds like overkill to me, so I think you should be pretty good to go with that much storage. An OS Snapshot and package don't have their data inserted into binary fields of the database--just the metadata that describes the OS or package.
So 100 "average" packages and a few OS snapshots shouldn't take more than a few megabytes of storage. I don't have an exact number to give you, but I wouldn't expect anything out of the order of more than 20mb of space on the DB server.
To use the biggest example I can think of of a production AdminStudio database, it was roughly 9gb in size backed up, with 6000 application requests in Workflow Manager. The application requests had associated packages, so you're probably not looking at much more than a megabyte per package for database growth by my quick and dirty calculations.
And it takes a few years of rather heavy usage to get the database even up to 9gb in size, I can assure you. BUT, 1tb is perhaps a good start for the Software Repository, where all the packages can be stored when you import them into the ConflictSolver database. This is where the full installations go, and so could really use all that space.
For creating the database with scripts, you can tell which scripts run during the catalog creation wizard by just looking at the output:
Executing SQL Script 'AMS_System_Schema'
Executing SQL Script 'AMSCreateIndex'
Executing SQL Script 'AMS_SamplePackagingTemplate'
Executing SQL Script 'AS_System_Schema'
Executing SQL Script 'Seed_Data'
Executing SQL Script 'CustomReportWizard'
Each of these corresponds to *.sql files under:
C:\Program Files\AdminStudio\9.5\Support\SQL_Scripts
