Question

I have a database designed to hold card data from various trading card games. Up to this point, there has only been one card game I’ve been tracking, but I’m using an attribute table since not all attributes apply to every card.

I’m now expanding into multiple card games and have a slew of data ready to migrate in. However, I’m not quite sure how to import this data in. Should I simply clone the schema into a new database for each card game, so I can manage things in separate buckets? Or should I simply add a new table called ‘CardGame’ and use the unique identifier for this as a foreign key to the card and have one massive database for it all.

If it matters anything to the situtation, this master database is published to a web site for users to query against, a well as broken down into smaller data modules (per game) for a WinForms application that people can use.

Answer 1

My general preference in these situations is to use one database for the following reasons:

• Comprehensive reporting is made significantly easier
• As with code, DRY applies – if you have multiple ‘cloned’ schema what happens when you need to make a ‘core’ change?
• Maintenance is simplified

But the decsion ultimately rests on your specific requirements…