SQL Server 2005 Express
March 4, 2009 by Jason Bean
Filed under Computers
One of the current projects we’re working on involves a large database. The initial project was to optimize and clean-up an existing Access database application. However, as we’ve gotten involved in the project it’s expanded to include more features, larger requirements and more potential users.
We initially asked about migrating the database over to a full SQL Server 2005 solution, but ran into some resistance for a variety of concerns, one of which was cost of setting up and installing SQL Server 2005.
We then started to take another look at potentially using SQL Server 2005 Express edition as the solution for this application. By comparison to other full-blown SQL Server 2005 this database requirement is fairly small. However, it’s pushing the boundaries of what can reliably be delivered with the Access Jet database performance.
I’m curious as to what other people’s real-world experience has been with developing application to be hosted with SQL Server 2005 Express as the backend database solution?
What hurdles have you had to jump, or have they stopped you completely in your tracks? Do you feel you’ll outgrow the Express version anytime soon. If so, are you prepared to migrate to the full SQL Server 2005 version.
Compare Features of SQL Server 2005 Versions
I work at a place where we routinely use SQL Express 2005 to drive the database requirements. As long as you’re doing nothing fancy inside SQL, then you should be fine. Basic queries, stored procedures, and views all work great. The only thing that you have to consider is the fact that the DB can’t get over 4GB, and you don’t get to do cool stuff like maintenance plans or SSIS packages.