If you're not sure which type of database to create for your application, ask yourself the following questions:
□ Will your database grow beyond 2GB?
□ Are there security concerns for the data stored and used by your application?
□ Is the data in your application critical or irreplaceable?
□ Does your application require a large number of transactions at any given time?
□ Does your database need to be accessed by a large number of users simultaneously?
□ How will users work with the data from the database in the application?
Even answering these questions won't provide a definitive solution as to which type of database you should use for any given application. Every application's data storage mechanism should be evaluated on a separate basis by gathering storage requirements and researching the application's purpose to determine which type of database management system to use. For example, if the application will need to store 1.5GB of data, store confidential data, and need to be accessed by thousands of users at any given time, you might consider employing SQL Server 2005. However, if an application requires less than 1GB of data, needs to accommodate 20 users with relatively low traffic, and must maintain low development and support costs, Microsoft Office Access 2007 is the perfect choice.
Whatever database management system you choose, be sure to adequately understand the application requirements and research database system options before beginning work. The cost of redeveloping and porting an existing system can be huge, and in many cases, much more expensive than the cost of developing the proper system initially. Doing a little research and choosing the correct system the first time almost always pays off in long-term development and support costs.
Was this article helpful?