SQL Server How many users do you really need?

Question

I am setting up an application and I am looking for a license purchase for SQL Server. My question is pretty simple (although there may be a tricky answer ...)

How many user accounts do I really need for SQL Server?

As I see this, I would give one administrator account, possibly 2 or 3 user accounts, and then one application-based account.

My application will probably have about 30-40 users, with the rare possibility of using 4-5 people at a time. But, as I see it, I created a BLL with 30-40 accounts - and the BLL will have an SQL account that all 30 accounts will use to query DB through ...

I'm just wondering what people take over. Is this the way, or am I having the wrong idea of ​​architecture here?

Answer 1

Your case is called Multiplexing ans, which is considered for special reasons. Using Middleware, transaction servers, and a multi-tier architecture:

Sometimes organizations develop network scenarios that use various forms of equipment and / or software that reduce the number of devices or users that have direct access or use software on a particular server, often “multiplexing” or “combining,” hardware or software. Using such multiplexing or combining equipment and / or software does not reduce the number of client access licenses (CALs) required to access or use SQL Server software. CAL is required for each individual device or user of a multiplex or pool or hardware front end. This remains true no matter how many levels of hardware or software exist between the SQL Server startup server and the client device that ultimately uses its data, services, or functionality

On the bottom line: you need one CAL per user, up to 35-35 licenses.

Answer 2

I understand that you need a CAL for each individual user or device that uses SQL Server this way 30-40 in your case. Accounts are just a set of credentials that are authenticated on the server, while users are bags of meat. Licensed bags of meat, not bills.

This is an easily mistaken area, although I would advise contacting Microsoft Licensing to find out the real deal.

Answer 3

Do you know that commercial use of SQL Express 2005/2008 is permitted and may be ideally suited to your scenario?

You can always upgrade to Standard Edition at any time if you need it.

For a comparison of MS SQL Server editions, see here . It also includes their limitations. I am convinced that SQL Server Express will be very good for your scenario (assuming your database does not exceed 4 GB).

Answer 4

Simple answer:

Each individual user or device that connects to SQL Server requires a CAL, regardless of multiplexing or a web server or proxy between the end user and the SQL Server installation.

If you cannot physically calculate and quantify them (for example, a public website), you will need processor licenses.

More details ...

• What if you expand the store or user base?
• Client licenses are becoming more expensive than the processor at some point.
• You rarely license one box.
• How about fault tolerance in production?
• Non-prod licenses (test / dev-boxes) → get MSDN

My advice: talk to MS or someone who deals with your licenses in your store. You already have an agreement with MS for OS and Office at least.

Answer 5

If your application uses BLL, which proxies many users to an instance of SQL Server, I think that you cannot get a license based on the number of accounts.

Microsoft will tell you that you need a processor license. (And it's cheaper than buying 30-40 CALs)

Answer 6

In this section, which asks a question about MS Sql Server:

For applications oriented to an external server. Processor licensing is the best choice for external server oriented applications such as Internet scripts and extranets. It is often difficult to count devices or users in these scenarios, so hardware-based pricing is simpler.

For mixed use servers. For mixed-use servers that will be available both inside and outside the organization’s firewall, processor licensing is usually beneficial. Since processor licenses are probably necessary for external users, there is no need to purchase access separately for internal users through client licenses.

For environments inside the firewall. For environments inside the firewall, where the relationship between servers and processors is relatively low, the licensing model of the CAL server and the device is likely to be a more economical choice if there are several users for each device (for example, in the call center), while the model CAL licensing for the server and user is likely to be more cost-effective if there are multiple devices for each user. For environments inside the firewall where the relationship between servers and processors is high, the processor licensing model is likely to be more cost-effective.

Answer 7

If you do not do something complicated with proxy authentication and auditing , you will only have input for the application. Otherwise, I would get a license from the processor.