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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-12-27 : 11:46:21
|
| jon writes "what does sql server do if there are more connections attempted than licenses? Is it an honour thing or are the connections refused.If they are refused is there an error given.Thanks" |
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2002-12-27 : 13:53:41
|
| I belive it's an "honor" type thing. I don't know that I've ever gotten an error message that said not enough licenses. You may get such an error if you run SQL Server on Windows 2000 PRO or Windows NT Workstation 4.0. Those two "desktop" operatiing systems only allow for 10 connections. I think at around 50-75 Connections on a single CPU system the "Per Processor" licensing is the best way to go. If you are worried about licensing, get the Per Processor licences (one for each processor in the machine). As far as I'm concerned, it's the easiest way to get the licenses. You get that, and you have as many connections as you want. if you are using your SQL server in an Application server Provider model (ie you have a webserver connecting to your SQL server) you are supposed to get the Per Processor licenses, because you have N number of "devices" connected to the SQL server.If you use MSDE, you will get a message in the event log when you go over 8 concurrent queries. At that point, everything still works liked you coded it, but MSDE will "slow things down."I think that covers all the bases!Michael<Yoda>Use the Search page you must. Find the answer you will.</Yoda> |
 |
|
|
harshal_in
Aged Yak Warrior
633 Posts |
Posted - 2002-12-28 : 01:22:10
|
quote:
I belive it's an "honor" type thing. I don't know that I've ever gotten an error message that said not enough licenses. You may get such an error if you run SQL Server on Windows 2000 PRO or Windows NT Workstation 4.0. Those two "desktop" operatiing systems only allow for 10 connections. I think at around 50-75 Connections on a single CPU system the "Per Processor" licensing is the best way to go. If you are worried about licensing, get the Per Processor licences (one for each processor in the machine). As far as I'm concerned, it's the easiest way to get the licenses. You get that, and you have as many connections as you want. if you are using your SQL server in an Application server Provider model (ie you have a webserver connecting to your SQL server) you are supposed to get the Per Processor licenses, because you have N number of "devices" connected to the SQL server.If you use MSDE, you will get a message in the event log when you go over 8 concurrent queries. At that point, everything still works liked you coded it, but MSDE will "slow things down."I think that covers all the bases!Michael<Yoda>Use the Search page you must. Find the answer you will.</Yoda>
I am not sure whether the following is about windows lisences or sql server lisences this is what i found in BOL:Error 18458Severity Level 14Message TextLogin failed. The maximum simultaneous user count of %d licenses for this server has been exceeded. Additional licenses should be obtained and registered through the Licensing application in the Windows NT Control Panel.ExplanationThis error occurs when the server is set for Per Server licensing and the number of attempted client connections exceeds the number of Client Access Licenses for this server.ActionObtain additional Client Access Licenses or reduce the number of simultaneous client connection attempts.Expect the UnExpected |
|
|
|
|
|
|
|
|
licensing