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 |
|
scoogie
Starting Member
2 Posts |
 Posted - 2005-04-27 : 13:16:49
|
| i'm from the oracle world, so i may be asking a very elementary question...in oracle, you can set a parameter called "connections", which, obviously, sets a ceiling to how many concurrent connections can be present on the server. from a SQL Server perspective, are the CALs synonomous with "concurrent connections"thanks. |
|
|
Kristen
Test
22859 Posts |
Posted - 2005-04-27 : 14:11:31
|
| You can set up [and, indeed, "license"] a SQL Server to have a maximum number of concurrent connections, or have an "unlimited" number of connections. You have to use the later method for a public-facing web server [AFAIK].Kristen |
 |
|
|
scoogie
Starting Member
2 Posts |
Posted - 2005-04-27 : 14:13:21
|
| do you set up the licenses from the client side or the server side? again, i'm a novice, so bear with me :) |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2005-04-27 : 14:17:07
|
| Server side. But there are cost implications I believe. So [I think] you can license a server to allow [say] 5 concurrent connections, but it may also be a requirement that the clients [who actually connect] have an license [a "CAL"] to do so. So, a "pool" of 50 clients may connect, all of them may have a CAL, but only 5 of them may connect concurrently.This aint my strong-suit, so don't take it as gospel please - hopefully someone will be along in a minute to put me straight!Kristen |
|
|
|
|
|
|
|
|
new to SQL server