Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dcarva
Posting Yak Master
140 Posts |
 Posted - 2006-04-21 : 17:38:22
|
| I am currently deploying an application for a customer that utilizes his SQL Server. I noticed that he has 5 client licenses installed. I am researching now to see if that is enough for him. However, I have a general question about making ADO database connections and how it affects licenses. In my ASPX pages, I typically connect to the database using Windows Authentication instead of using the SA sql account. Would this somehow use more licenses in SQL rather than if I used the SA account? Or does it have nothing to do with the account I use? Thanks!Danny |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-04-21 : 17:45:01
|
| Which account you use doesn't affect how many connections. And you should never use the sa account anyway. The alternative to Windows Authentication is SQL Authentication but not with the sa account.Tara Kizeraka tduggan |
 |
|
|
dcarva
Posting Yak Master
140 Posts |
Posted - 2006-04-21 : 17:55:43
|
| Makes sense. Thanks for your help!Danny |
|
|
|
Krankensteins
Starting Member
24 Posts |
Posted - 2006-04-22 : 02:31:05
|
How I anderstud MS policy for licensing then ther is needed licensing per procesor ? Web server reduces real users count. I heve sam pay-out with application server  |
|
|
|
R1chard
Starting Member
2 Posts |
Posted - 2006-04-23 : 07:43:42
|
| I understand SQL licensing works as:1 CAL (client access) per named user.or 1 Processor per CPU used.If you have multiple users access the SQL server. Even if you use a single account to access the SQL server, you need to take into account the users being served - this is called multiplexing. So for each user you need a CAL or if deploying a large number of users go processor as it eventually works out cheaper.HTH |
|
|
|
|
|
|
SQL Licenses