Can SQL Server Express 2005 handle personalization for hundreds of users on a production server, or do you need to upgrade to another version of SQL Server 2005?
When using forms authentication, I guess there's only a single connection to the SQL Server under the NETWERK SERVICE identity (Windows 2003 Server), but with Windows authentication, each user has his own connection. Can SQL Server Express handle this, and
does the license permit it?
Thanks for any info (I couldn't find a quick answer with Google).
If you use Sql Server Express you should use it as a regular SQL Server instance - i.e. connect to .\SQLExpress as opposed to using the default user instancing connection string that ships in machine.config. If you do this you will be using Sql Server Express
just as you would be using any other version of Sql Server 2005. The main difference is that Sql Server Express has some limitations versus other Sql Server SKUs - I don't know all the specifics, but for a site with users in the low hundreds you probably
won't run into any space issues unless you are storing lassive quantities of personalization data.
Jos Branders
Contributor
5210 Points
822 Posts
Is SQL Server Express OK for personalization on a production server?
Jan 03, 2006 07:50 AM|LINK
Can SQL Server Express 2005 handle personalization for hundreds of users on a production server, or do you need to upgrade to another version of SQL Server 2005?
When using forms authentication, I guess there's only a single connection to the SQL Server under the NETWERK SERVICE identity (Windows 2003 Server), but with Windows authentication, each user has his own connection. Can SQL Server Express handle this, and does the license permit it?
Thanks for any info (I couldn't find a quick answer with Google).
Jos
sschack
Contributor
3085 Points
617 Posts
AspNetTeam
Moderator
Re: Is SQL Server Express OK for personalization on a production server?
Jan 04, 2006 03:56 PM|LINK
If you use Sql Server Express you should use it as a regular SQL Server instance - i.e. connect to .\SQLExpress as opposed to using the default user instancing connection string that ships in machine.config. If you do this you will be using Sql Server Express just as you would be using any other version of Sql Server 2005. The main difference is that Sql Server Express has some limitations versus other Sql Server SKUs - I don't know all the specifics, but for a site with users in the low hundreds you probably won't run into any space issues unless you are storing lassive quantities of personalization data.
For more details see:
http://www.microsoft.com/sql/editions/express/features.mspx
And then scroll down towards the bottom of the page.
----------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.