Advice needed: Best way to export SQL database

I find myself with a unique problem in exporting a SQL database.

BACKGROUND:
Our client requires all source material used in the construction of the learning material we develop for them. The newer version of the product we're using, no longer uses a standalone database for each product, but instead places all projects into one database (so it can share questions, instructions). Since multiple projects can exist in the same database, I need to extract only the material for each class, and leave out information not used in any of the classes they didn't pay for.

SOLUTIONS:
1) I could copy the entire database to another server, write a program to remove items from the database that shouldn't be part of the export, and then use the BACKUP command

or

2) I could export all the tables which contain only what I want, as a CSV file, and instruct the client to import them.

THE QUESTION:
Clearly step 2 will be the easier method in the long term for the people who will need to export a project (less setup time, less room for errors). My question is what should a CSV file look like it there are multiple tables within the product. Having never imported a CSV file into a SQL server before, I'm not sure if you have to create a single CSV file for each table (there's like 100 tables for this product, most of them quite small or empty, with maybe a dozen large ones), or if there's some sort of accepted format for combining all the tables into one larger file (CSV or otherwise).

This is something that needs to be burned to a CD-ROM and mailed at the end of the project, and I need to know that it's fairly generic so that if they aren't using a Microsoft SQL server, they still have a chance at importing this later.

Even if you don't know the answer, anything that points me in the right direction is appreciated. This is one of those things, where they tell the sole programmer in the division they need a custom solution to a problem in less than a week, and I have no idea where to begin. I at least now the database structure very well, so spotting what I don't want isn't difficult, it's just a matter of what it should all look like at the end that I'm cluess about.