What would be the best way to split a pkg file up?  Just doing some testing, I created a pkg file with 2 tables, and 2 data deployments and am trying to get the tables and data deployed.  Leaving all of the files in one pkg file everything works fine.  Taking out say one of the data .bin files, it never gets deployed to the server.

Is there any easy way to do this, or do I need to make one big pkg file, create copies and delete out the .bin files I won't want to deploy again leaving the structure ?

Thanks

Robin Giltner

When you split up the .bin files that are located within the .pkg file, you'll also have to take along the Deployment Data record and the table needed to deploy the data.  So, say your database has Table1, Table2, and Table3 and the .bin files that hold the records for these 3 tables are too large to keep together.  You'll need to create a separate profile for each of the Deployment Data items.  So, create a profile for the Table1 data, create the database and import Table1 from your main profile.  The profile only needs to be able to see that one table, then you can create the Deployment Data record for Table1.  Package it up, repeat the steps for the rest of your Deployment Data items that you want to separate and just deploy each package separately. 

Alternatively, you could pull the .bin files into separate .pkg files and before you call the DeployData method on the DatabaseMigrator, extract all of the .bin files to the same folder that all of the XML files were extracted to.  I'm not positive, but I believe that it creates a %Temp%/MicroFour folder to house the .bin files.  That would also do the trick with less profile maintenance, but you would have to pull out the .bin files by hand...

Thanks Ben, that's what I needed to know.

Robin Giltner