>lets may application uses only one SQL account internally.and created a database for my application users.so the counting of license is by concurrent? or the no no of users in SQL databse we Created?. lets say i have 4 user created in our SQL server.But when the application run it uses on 1 user for 10 concurrent connection.DO i have to register the 10 concurrent even they are using the same user name in SQL server? tnx bob
Yes!
It's not even 'concurrent' users... it's total ULITMATE end users (people) that will use your app that talks to the server.
It doesn't matter how many physical connections you use, or logins you set up, or concurent users you have.
Here is an excerpt from the article at:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/sql/reskit/sql2000/part2/c0461.aspLicensing in Multi-Tier Environments (Including Multiplexing or Pooling)
Sometimes organizations develop network solutions that use various forms of hardware and/or software to reduce the number of devices that directly access or use the software on a particular server. This particular solution is often called multiplexing or pooling hardware or software. It is particularly common in multi-tier environments. For example, say a client computer is using a server application that calls Component Services, available with Microsoft Windows 2000 Server, on one server, which in turn pulls data from a SQL Server database on another server. In this case, the only direct connection to SQL Server is coming from the server running Component Services. The client computer has a direct connection to the server running Component Services, but the client computer also has an indirect connection to SQL Server because it is ultimately retrieving and using the SQL Server data through Component Services. Use of multiplexing or pooling hardware and/or software does not reduce the number of CALs required to access or use SQL Server. A CAL is required for each distinct input to the multiplexing or pooling software or hardware front end. If, in the above example, 50 client computers were connected to the server running Component Services, 50 SQL Server CALs would be required. This is true no matter how many tiers of hardware or software exist between the SQL Server and the client devices that ultimately use its data, services, or functionality.
