Which is better: stand-alone databases or an optional “code” table?

Question

I have a database designed to store card data from various trading card games. Until that moment, there was only one card game that I tracked, but I use the attribute table, since not all attributes apply to each card.

Now I am expanding into several card games and have a lot of data ready for migration. However, I'm not quite sure how to import this data. Should I just clone the circuit into a new database for each card game, so I can manage things in separate buckets? Or just I have to add a new table called "CardGame" and use a unique identifier for this as a foreign key to the card and have one massive database for everything.

If it matters for situtation, this main database is published on the website for the users who need a request, and is also split into smaller data modules (for each game) for the WinForms application that people can use.

Answer 1

:

• .
• DRY, "" , , ""?

...

Answer 2

:

• , - , , . - , , .

• , .

• , . , , .

• ...

Answer 3

, , .

, , , , .

, , .

Answer 4

. , . , , , db, , . , , , , /. . SO, , FogBugs . ( , , - 20- ).

, (, RedGate) .

- , , , , dbs . , , db, .

, dbs. dbs , . , .

EDIT: - . , . 200 , . .

, , , .

• , , ? (, , , ). . . , , , . . , .

• , - - ? .

, : " ". : " , , -?" , ( , - , ) - , 10 , , - .

Answer 5

DRY. . , DRY . . db, , , , , , , , , Road Runner Wily Coyote!

Answer 6

, , , , , ( ), , , - .

Answer 7

, - .

, , - . , , . SP, , .

You can also distribute games, several to the database. There are many reasons for this segregation. This probably does not apply to you, but for extremely large databases it sometimes makes sense in terms of a maintenance window to have multiple databases with multiple tenants. For example, by country or time zone.

In SQL Server, since the ACID external integrity and backup unit is the database, having extremely large databases with multiple tenants can make it difficult to run small maintenance windows.