Players Database Structure

[Kivlehan]

I have a number of ideas to improve OOTP Baseball 2006 that I would like to share, but the most important comment and concern I have from playing the game frequently is how the players database table operates.

The beautiful thing about OOTP Baseball 2006 -- the thing that makes its scope and ambition so breathtaking and amazing -- is how you can have a really huge baseball universe run. For example, I created a baseball universe with about 20 different leagues, spanning pretty much every major city in the world. Unfortunately after 70 years of game simming, the league crashed and burned because the player database became unwieldy.

Some might say I should be happy I got that far. They might point out I couldn't do so with any other game. I grant that. But OOTP has been about pushing the envelope and I think there is a way to design the players database structure that could relive this size problem: Go back to having separate databases for active and retired players.

Call only on the retired players database when running historical reports. Let them game only read and process active players. This will greatly help speed and keep the active players database from getting unwieldy like it can now. I believe this structural change would make a huge difference. If I am not mistaken, the previous OOTP engine actually did have separate active and retired player databases.

Thanks,
Chris

[1998 Yankees]

I would like to vote emphatically for this suggestion and I am taking the liberty of linking it to Kivlehan's earlier post about the need for manually deleting retired players in order to keep the player database and the screens that address it manageable:

Any way to mass delete players from the database?

Note that I go through the procedure that I described in that thread despite having only MLB in my universe and despite having the "Delete retired players who never reached the Majors" option selected.