SQL 2005 Express ok for Web Server? 1

[CathodeRay]

We have a small database we want to make accessible on a web server. It is most definitely *less* than 4gb... but we may have hundreds (thousands?) of people accessing it at one time.

From a *licensing* perspective, would Express be appropriate? And am I correct in that we can download the Management Console for that version?

Another question: what are HTTP Endpoints? Express doesn't offer them, and I'm not sure if we need them or not.

Next question: Express apparently doesn't offer Full-Text Searching...we DO need to search some fields in the database... that is, we need to execute a command similar to: "select all where column1 LIKE (or contains) 'Smith'

Does that necessarily mean we need "full-text searching"? To provide some parameters... this particular column we'll be searching on will be about 40 characters of text... Think we need full-text searching for that? We'll have about 10,000 records, each being about 1000 bytes each.

 

[mrdenny]

With the number of users you are talking about (hundreds to thousands at any one time) you will not be happy with the response from SQL Express. SQL Express will only run up to 10 (I think) commands at any one time. Beyond that the queries have to wait until one of the available slots is available then the next one can run. So if 30 people try to submit queries to the database and each query takes 1 second to execute at best the last person will have to wait an additional 3 seconds for there process to complete.

If you are making standard ODBC connections to SQL Server don't worry about needing the HTTP endpoints. You don't need them.

Based on the info provided you don't need full text searching. Full Text searching is designed to index and search large unformatted text and binary fields using the TEXT, NTEXT and IMAGE data types. You are most likly using the VARCHAR or NVARCHAR data types which do NOT require full text searching to view.

I've written up a FAQ on SQL Server licensing. You can find it here faq962-5153.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[CathodeRay]

Thank you, MrDenny... I was hoping you would respond...

How about Workgroup Edition (per processor licensing)? OK for # of transactions?

 

[gmmastros]

mrdenny,

I read somewhere, on microsoft's site, that they removed the bandwidth throttling from SQL Express. I can't seem to find it again, but I did find this site that also suggests that they removed the bandwidth throttling.

http://www.pcw.co.uk/personal-computer-world/software/2155087/review-microsoft-sql-server

What are your thoughts on this?

-George

Strong and bitter words indicate a weak cause. - Fortune cookie wisdom

 

[CathodeRay]

gmmastros, nice find... am seeking feedback from mrdenny,too.

 

[mrdenny]

I've confirmend that the workload govener has in fact been removed from SQL Express.

http://www.microsoft.com/sql/editions/express/upgrade.mspx

(First bullet under reasons to updated).

Workgroup should be ok. It does support two physical processors, so if you got two dual core processors that should be enough power for you (assuming that your database is indexed correctly, well laid out, etc).

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com