Number of users of SQL SERVER, connection, connection pool license

SQL Server theoretically has 32,767 logical connections, and SQL Server is self-leveling the connection pool based on the system.

First, the number of users of the operating system: that is, at the same time through the network connected to the computer above the user limit, to 5 user operating system, set up a file server as an example, to access the file server at the same time the network users of 5.

Here is the SQL Server, the purchase of a database in two ways, 1, according to the number of users to buy. 2, according to the number of CPUs to buy.

Depending on the number of users purchased, if you purchase a database of 50 users, then the number of people who can access the database over the network is limited to 50.

Depending on the number of CPUs purchased unlimited database access, the server has a few CPUs to buy several authorized SQL Server, but if you buy only one license, the database can also run normally, but Microsoft thinks your database is not legal. It's like a pirate system.

A connection is not equal to a user, a single user can have more than one connection, and a single connection can have more than one user.

You can run the inside input perfmon and then add the following two counters to compare
sqlserver:general statistics-logical Connections: The number of logical connections established with the system. sqlserver:general statistics-user Connections: number of users connected to the system.

Make a metaphor.

SQL Server is your house.

Number of users is the key to your house.
The number of connections is the one where your house can go.

It's not very appropriate, but it basically explains the problem.

The number of keys in a house is clear, but each key can be used to get more people in.
That is, users of SQL Server can log on to SQL Server, and the number of connections refers to a connection that is logged in with a user name in order to perform a specific operation.

Typically a SQL SERVER query, a adoconnection is a connection.

View the number of online users currently connected in SQL Server
Use master
Select Loginame,count (0) from sysprocesses
GROUP BY Loginame
Order by count (0) desc
Select Nt_username,count (0) from sysprocesses
GROUP BY Nt_username
Order by count (0) desc
If one of the SQL Server user name Test connections is more, view the host name it came from:
Select Hostname,count (0) from sysprocesses where loginame= ' test '
GROUP BY hostname
Order by count (0) desc
If a SQL Server user name Test connection is more, view the time range grouping for its last operation:
Select CONVERT (varchar,last_batch,111), COUNT (0) from sysprocesses where loginame= ' test '
Group by CONVERT (varchar,last_batch,111)
Order by count (0) desc
If you have more connections from the host (WWW), you can view its process details
SELECT * from?? sysprocesses where hostname= ' www '
If the WWW machine mainly provides Web services, it is possible that the ASP program handles the connection when there is a problem, generating the SQL statements that kill these processes:
Select ' Kill ' +convert (varchar,spid) from sysprocesses where hostname= ' www '
If such problems occur frequently, you can write a stored procedure sp_killidlespids.sql,
Write a job that executes it to automatically kill the user connected from the host (WWW) but has not responded for a day.
?
?
?
--------------------------------
Users and permissions for SQL Server?
? Can the sysadmin perform any activity in SQL Server?
ServerAdmin can set server-wide configuration options to shut down the server?
Setupadmin can I manage the linked server and startup process?
Securityadmin can manage logins and CREATE DATABASE permissions can also read the error log and change the password?
Processadmin can I manage the processes running in SQL Server?
DBCreator can I create changes and drop databases?
Diskadmin can manage disk files?
Bulkadmin can execute BULK INSERT statement? ......

Maximum connections refers to the maximum number of concurrent accesses the database can tolerate

How do you understand the number of concurrent users or license SQL Server? China Soft Forum 2005-12-06 13:38:55 in Ms-sql Server/Basic class questions

Is there a limit on the number of concurrent users for piracy? Genuine seems to have 10 users, 50 user version, if the C/s architecture, each client connection is not counted as a user?

Then there was a time when it seemed to change to just the CPU to buy license. Now it's like seeing the license of the number of connections purchased.

To tell you a lot, if you only have 10 users license, there is no limit. This is what Microsoft's marketing staff told me personally. [China Soft NET]

Welcome reprint, but please keep the source, this article to [China Soft net] original link: http://www.huarw.com/db/dbbbs/MSSQLServer/200512/735120.html

You mean the purchase license?

SQL offers 3 ways to buy
1) Processor license. (purchased by CPU)
Requires a license to be purchased for each CPU on the operating system running SQL Server 2000. There is no need to purchase client access Licenses in this way.

2) Server plus device CALs. (Server license plus per Device Client Access License)
A server running SQL Server 2000 requires a license, and each device that accesses SQL Server 2000 requires a Client Access License.

3) Server Plus user CALs. (Server license plus per-User Client Access License)
A server running SQL Server 2000 requires a license, and each user who accesses SQL Server 2000 needs a client Access License

2. Per customer
Per-Customer licensing mode requires that each device that accesses a SQL Server 2000 server has a client Access License. Per-customer mode is typically more cost-effective for networks where clients connect to more than one server.
In the edit box, select the number of devices you want to authorize.


Select the licensing mode:
Use this dialog box to set the authorization mode so that clients can access Microsoft? SQL Server? of this instance. SQL Server 2000 supports two types of client access licensing modes, one for the device and the other for the processor.
The device can be a workstation, terminal, or any other device running a SQL Server application that is connected to an instance of SQL Server.
The processor refers to the central processing unit (CPU) installed on the computer running the instance of SQL Server 2000. Multiple processors can be installed on a single computer, requiring multiple processor licenses.
Once the licensing mode is set, it cannot be changed. You can add a device or processor license after you install SQL Server, which is done using the SQL Server 2000 Licensing installation utility in Control Panel.
1. Licensing Mode
When this dialog box is accessed from the Control Panel, the mode selected during installation is selected by default and displays the number of previously selected devices or processors.
2. Per customer
Per-Customer licensing mode requires that each device that accesses a SQL Server 2000 server has a client Access License. Per-customer mode is typically more cost-effective for networks where clients connect to more than one server.
In the edit box, select the number of devices you want to authorize.
3. Processor License
With processor licensing, a license is required for each processor installed on the computer that is running SQL Server. Processor Licenses allow any number of devices to access the server, whether they are over the Intranet or the Internet.
With processor licensing, SQL Server 2000 can take advantage of each installed processor and support an unlimited number of client devices. Customers who provide access to a SQL Server database over the Internet, or customers who have a large number of users, typically choose a processor license.
In the edit box, select the number of processors you want to authorize.
After the SQL Server installation succeeds, SQL Server starts the service automatically after you restart the computer.

10 users are not referring to connected users

When you create a custom console, you can assign one of two common access options to the console: Author mode or user mode. There are three levels of user mode in turn, so there are four options for the default Access console:

Author mode
User mode-Full access
User mode-limited access, multiple windows
User mode-limited access, Single Window

You install the Enterprise Edition, 10 clients means you can only install 10 SQL clients on the other machine to connect with it