My company is creating a new Umbraco site, and will need to buy a new database server. They would like to hear the different options available to them to make the best decision.
First off, the website itself won't be overly complex. It's a marketing site with a couple of forms that will get data from a web service. So over-all, I'd say that it's pretty basic. It will be a very well traffic'd site with well over a million hits a month.
The best decision in my mind is that they buy a SQL Server 2008 R2 license and equipment for that. The problem is that it's expensive.
The next best option is that they pay for hosting it.
The third best option is using Sql Express.
The worst option is using SQL CE.
I'd like to accurately describe the experience of the 3rd and 4th options. If we cache most of the pages, will this have a major speed impact on end-users?
Seems the biggest differences between CE and Express are CE doesn't support stored procedures, which shouldn't be an issue if you aren't creating any custom tables, or writing custom sections.
The number of concurrent connections on CE is apparently 256 whereas Express is unlimited.
There's absolutely no difference between the speed of SQL Server and SQL Server Express, barring some memory and storage limitations and not being able to scale to a webfarm of sql servers.
For most sites, I've never seen a need to buy a full SQL Server license, SQL Express works just fine. If you KNOW that you're going to have very specific very custom needs then maybe you should look into full SQL Server. Doesn't sound like it though.
While not Umbraco-specific, SQL Server Express also does not support transparent data encryption, which may be required in some situations (such as for HIPAA compliance, common for instance with health care websites).
Using SQL CE vs. SQL Express in Production
My company is creating a new Umbraco site, and will need to buy a new database server. They would like to hear the different options available to them to make the best decision.
First off, the website itself won't be overly complex. It's a marketing site with a couple of forms that will get data from a web service. So over-all, I'd say that it's pretty basic. It will be a very well traffic'd site with well over a million hits a month.
The best decision in my mind is that they buy a SQL Server 2008 R2 license and equipment for that. The problem is that it's expensive.
The next best option is that they pay for hosting it.
The third best option is using Sql Express.
The worst option is using SQL CE.
I'd like to accurately describe the experience of the 3rd and 4th options. If we cache most of the pages, will this have a major speed impact on end-users?
Thanks,
Chad
Seems the biggest differences between CE and Express are CE doesn't support stored procedures, which shouldn't be an issue if you aren't creating any custom tables, or writing custom sections.
The number of concurrent connections on CE is apparently 256 whereas Express is unlimited.
I've always found this site to be very useful for SQL related questions and it has proved as such again : http://blog.sqlauthority.com/2009/04/22/sql-server-difference-between-sql-server-compact-edition-ce-and-sql-server-express-edition/
There's absolutely no difference between the speed of SQL Server and SQL Server Express, barring some memory and storage limitations and not being able to scale to a webfarm of sql servers.
For most sites, I've never seen a need to buy a full SQL Server license, SQL Express works just fine. If you KNOW that you're going to have very specific very custom needs then maybe you should look into full SQL Server. Doesn't sound like it though.
Ps. Our.Umbraco runs on SQL Express.
Would there be any harm in explicitly stating that in the documentation?
https://our.umbraco.org/Documentation/Getting-Started/Setup/Requirements/
While not Umbraco-specific, SQL Server Express also does not support transparent data encryption, which may be required in some situations (such as for HIPAA compliance, common for instance with health care websites).
Thanks!
is working on a reply...