StrataFrame Forum » StrataFrame Database Deployment Toolkit » Database Deployment Toolkit (How do I?) » Develop on SQL Server but Deploy to SQL Server Express

Develop on SQL Server but Deploy to SQL Server Express

Russell Scott Brown — Tue, 08 Sep 2009 10:12:46 GMT

Do most people develop their applications on SQL Server even though they will deploy to SQL Express? I'm using SQL Express because the final application will run on SQL Express on client notebooks and so this will force me to be very familiar with what the express version can and cannot do.

I would like to do everything on SQL Server but I was wondering if there were any "gotchas" I should be aware of. Is this what most people do?

Thanks

RE: Develop on SQL Server but Deploy to SQL Server Express

Russell Scott Brown — Tue, 08 Sep 2009 10:12:46 GMT

Thanks.

Since you even use SQL Express in your medical applications I feel even more confident.

RE: Develop on SQL Server but Deploy to SQL Server Express

Trent L. Taylor — Mon, 07 Sep 2009 11:54:36 GMT

Actually we cover this very topic in our training classes, but the short version is that the express version is the same as the standard with the following limitations:

SQL Express Limitations

Only supports database sizes up to 4 GB
Only uses a single processor core (or thread if using hyperthreading)
Only uses up to 1 GB of RAM

Past that, they are the same. In our medical application, we have many users that stick with the express version for smaller shops until they get close to the limit then purchase a full version of SQL. When this is done, it is just a matter of loading the full version and moving over the database if the instance changes.

During development, we generally stick with the full version. We use the Developer Edition for development usually, but also have a Standard Edition or two loaded as well.