November 14, 2011 at 7:47 pm
This is a general question relating to a .NET app we are building that processes data contained within SQL Server 2008 R2 databases.
Originally, we were anticipating distributing our app to our user base, requiring that our users install the free version of SQL Express 2008 R2 Edition. Unfortunately, our app cannot live with the 1 GB of memory limitation or the 10 GB database size limitation of the SQL Express Edition. The Standard Edition of SQL Server 2008 R2's limitations, however, will work perfectly for the app.
The question is, how do we distribute the app to the user base without requiring them to purchase a full version of SQL Server 2008 R2 Standard Edition (at a hefty price)?
I think I recall that earlier versions of SQL Server provided a SQL Server distributable runtime version that could provided to the users of a .NET app that accessed SQL databases and services, without requiring the user to purchase a full blown edition of SQL Server. I could not find anything like that, however, related to the SQL Server 2008 R2 Standard Edition.
I might mention that the app is a standalone app, which runs only on a user's desktop system (not in a server environment). The app and the SQL databases are all contained on the user's desktop.
Thanks in advance for any help and assistance. Much appreciated!
November 15, 2011 at 12:08 am
I might mention that the app is a standalone app, which runs only on a user's desktop system (not in a server environment). The app and the SQL databases are all contained on the user's desktop.
Well, it's time to reconsider the application architecture. I am suggesting this because the application is not been built, it would hell lot of work after few years.
Unfortunately, our app cannot live with the 1 GB of memory limitation or the 10 GB database size limitation of the SQL Express Edition. The Standard Edition of SQL Server 2008 R2's limitations, however, will work perfectly for the app.
If you are looking for cheap alternatives consider Open Source DBs like MySQL, PostgreSQL as well (I know I am posting in SSC, against SQL Server). I will not forget to mention that they come with their own limitations & configuration issues.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply