SQL Server Express for production website?

Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

centurian replied

13 February 2010, 19:48
SQL express does lack a few features as you have mentioned. Profiler is another that springs to mind.

There are ways around these things, but any workaround will have it's own learning curve, so bear this in mind if you think it will be an issue.

But yes, the majority of small applications will run fine on SQL Express. Current ClientCo has a few production apps running it.
Leave a comment:
thunderlizard replied

13 February 2010, 17:51
Good stuff. I'll give it a go.
I'll also look forward to lots of data migration projects for small businesses, when Microsoft revises that particular license option.
Leave a comment:
DimPrawn replied

12 February 2010, 09:05
You'll have no problems.

The biggest limitation in my mind is the 4GB database limit, but actually for most web sites/ web applications this is not an issue unless you are storing lots of binary objects (images, video, etc) directly in the DB.

And of course you have a simple and seamless upgrade to the full standard edition which costs about £4000 per processor.

And people say MS are greedy.
Leave a comment:
Zippy replied

11 February 2010, 23:52
Originally posted by thunderlizard View Post

Am trying to find a home for a website with a SQL server database. Lots of hosting services are planning on using the Express edition (mainly 2005, but some 2008). At first I thought that looked like very shabby shenanigans, but now I'm not so sure.

Let's say I can cope with the missing functionality (Agent and Full Text Search); can keep under the 4GB size limit; and can get by on daily backups...is there any reason why we shouldn't use it in prod?

No.
Leave a comment:
Durbs replied

11 February 2010, 23:43
Originally posted by thunderlizard View Post

is there any reason why we shouldn't use it in prod?

Nope. It is licensed to do so and assuming the hardware limitations aren't an issue (and realistically for 90% of apps it wont be, certainly not a website unless you are running Amazon) then go for it.

Worked for permi Co for a while and they were running very high volume, very busy ecommerce apps on Express - no problems at all.

Last edited by Durbs; 11 February 2010, 23:51.
Leave a comment:
PAH replied

11 February 2010, 22:58
I imagine the RAM limit (1gb), single CPU (though can be multi-core) and no parallel queries would be the issues to worry about. Depends how heavy your usage is likely to be and if it's a shared environment where others will be trying to also share the same instance of SQL Server.

BTW 'SQL Server Express 2008 with Advanced Services' has Full-Text search included:

http://www.microsoft.com/downloads/d...displaylang=en
Leave a comment:
thunderlizard started a topic SQL Server Express for production website?

11 February 2010, 21:32
SQL Server Express for production website?

Am trying to find a home for a website with a SQL server database. Lots of hosting services are planning on using the Express edition (mainly 2005, but some 2008). At first I thought that looked like very shabby shenanigans, but now I'm not so sure.

Let's say I can cope with the missing functionality (Agent and Full Text Search); can keep under the 4GB size limit; and can get by on daily backups...is there any reason why we shouldn't use it in prod?
Tags: None