January 12, 2004 at 1:37 pm
I am new to SQL server (primarily an Access Developer) and am wondering about the most cost effective way to license SQL as the data store for a web application(.asp). I have a customer that puts on an event once per year where we register perhaps 10,000 visitors. However, probably 5000 of them will register within the 48 hours of the deadline. Currently, we are not online. Our registration process is very complex (about 30 different entry forms are available depending on the programs they register for and we collect A LOT of info on each entrant). If we ran this process with say 2 web servers connected to a SQL database and we figure there may be as many 200 people hitting our site concurrently, what would be the most cost effective way to license sql server.
We may also have 1 other process connected to the SQL server which may have at most 10 people logged into the server. It is not a high power application at all and currently runs in Access reasonably well but if we install SQL, it will get moved. I have looked at using MSDE for one or both applications but have security, scalability, and performance concerns. Any comments or things to look out for would be appreciated, especially in regard to the web application.
January 12, 2004 at 1:49 pm
Your only choice is a per CPU license. As soon as you authenticate anonymous users, whether directly, through a website, or using MTS, you must license per CPU. Only when you have employees authentiating from your company, can you use CALs.
January 18, 2004 at 6:07 am
Do you have a microsoft reference for that?
I'm not disputing it, but it addresses a discussion I have had internally and I have not seen that written down from Microsoft.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply