Original Post
Hi Folks, If this is inappropriate, the mods can certainly do as they see fit. I've got a great, and I think marketable, idea for a piece of software. In order to realize how I see the software working, I'll need a database. Now this particular software isnt going to have multiple users, or high traffic to the database by any means. The actual tax on the database is really nothing more then keeping historical data of how the users have used the application so they can retrieve data based on historical uses of the application. In my job I really only work on web application, thus it is natural that I would use a DB of some sort (mySQL most likely since its free). My question to you all is, if my application (of one user on a local machine) is designed to use a database for the data driven backend, is it feasible? When the software is finished, do I package both the software and the database to install at the end users machine? Is there a better alternative to using a database? Obviously you understand Im trying not to delve too much into the application itself. If you all need more information, just let me know. Thanks in advance.