[cavebutter]

MySQL Considerations
OOTP is a very data intensive game, and the OOTP development team makes much more efficient use of data within the application than it does with the data dumps it generates. This creates some complications and forces some choices between performance and completeness of data.

In testing on a modern Windows 10 laptop, for example, a test data load of 5 years worth of data for 2 major leagues with full minors took just over 3 minutes for a localhost. I was unable to complete a load or update on a remote host programmatically, becuase the packet size exceeded the server's limit and I do not have permission to change that limit.

This is the reason for the strong recommendation for a local MySQL server. The other utilities will work fine with a remote server, but you will have to get your data into it outside of this toolset.

Future versions of this application may make some concessions in terms of completeness to accommodate remote servers.

The database is currently set up with WAY more data than it needs for depth charts and gameday books- but I think it's worth it to have that data there for more intricate stuff later on. I am thinking of ways to streamline the load for ONLY depthcharts and gameday books, but the fact remains that some sort of load will be necessary each time the data is updated. It's tricky, especially when this utility is not tied into the database that serves an online league.

Lastly, I would love feedback on what works and what doesn't, and suggestions for new features.