Another licensing question

Hi,
I have a question about SQL Server plus user CALs. What exactly is meant by
"user"? Is it a person that logs into my application or is it a user id
specified in connecion string?
Can I have one user CAL for X people, that are accessing SQL server through
identical userid in connection string?
for example:
users: John [logged into MyApplication at PC1], Mark[logged into
MyApplication at PC2], Bob[logged into MyApplication at PC3]
MyApplication is installed on everybody's PC (that is there are three copies
of MyApplication (PC1 and PC2 and PC3)).
Each installation of MyApplication is using this connection string to access
SQL Server:
ConnStr = "User ID=DEP_1;Password=abc;Persist Security Info=True;Connection
Timeout=15;Data Source=XXX;Initial Catalog=YYY"
Can I have one user CAL for user DEP_1 or do I need three user CALs for all
three users?
Thanks!
Hi
You needs CALS for all 3 users.
DEP_1 is just a security user and does not count in for CALS.
Regards
Mike
"Marek" wrote:

> Hi,
> I have a question about SQL Server plus user CALs. What exactly is meant by
> "user"? Is it a person that logs into my application or is it a user id
> specified in connecion string?
> Can I have one user CAL for X people, that are accessing SQL server through
> identical userid in connection string?
> for example:
> users: John [logged into MyApplication at PC1], Mark[logged into
> MyApplication at PC2], Bob[logged into MyApplication at PC3]
> MyApplication is installed on everybody's PC (that is there are three copies
> of MyApplication (PC1 and PC2 and PC3)).
> Each installation of MyApplication is using this connection string to access
> SQL Server:
> ConnStr = "User ID=DEP_1;Password=abc;Persist Security Info=True;Connection
> Timeout=15;Data Source=XXX;Initial Catalog=YYY"
> Can I have one user CAL for user DEP_1 or do I need three user CALs for all
> three users?
> Thanks!
|||Thanks Mike for quick answer!
1. Does this mean, that user CAL is nothing more than a paper?
2. Is user CAL somehow entered into SQL Server licensing properties? (I
found only licensing per-seat (device CAL) or per processor in my SQL Server
licensing setup)
3. How will Server know, if there are more users accessing server than are
defined in server licensing properties? (I will have only one CAL for DEP_1
and server will never know, who is currently logged into MyApplication)
4. Is user CAL always "mapped" (=issued) to real person?
5. What if MyApplication from previous post will be a windows service with
no UI interraction [no user logs into it. It will run on background on three
PCs and process some results]. Could it use only one user CAL then?
Bweh, I know, silly questions, but I'm lost in all these licensing options.
Thanks!
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> You needs CALS for all 3 users.
> DEP_1 is just a security user and does not count in for CALS.
> Regards
> Mike
> "Marek" wrote:
|||1. Yes, but if you don't follow the paper rules, you get very expensive
paperwork from Microsoft layers when they catch you.
2. On The server, go to Administrative Tools > Licensing
3. It does not know, but you are responsible. Point 2 can help you report on
it.
4. A CAL can be for a physical user or device and by the licensing terms, it
can only be transferred once to another user/device.
5. As long as the service does not get used by another program or service to
connect through it to the SQL Server (multiplexing)
http://www.microsoft.com/sql/howtobuy/default.asp
http://www.microsoft.com/sql/howtobuy/faq.asp
The CAL actually says a lot:
http://download.microsoft.com/downlo...A9/caleula.pdf
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Marek" <Marek@.discussions.microsoft.com> wrote in message
news:F588172A-B890-4D60-962B-8B211B7CD9C8@.microsoft.com...
> Thanks Mike for quick answer!
> 1. Does this mean, that user CAL is nothing more than a paper?
> 2. Is user CAL somehow entered into SQL Server licensing properties? (I
> found only licensing per-seat (device CAL) or per processor in my SQL
Server
> licensing setup)
> 3. How will Server know, if there are more users accessing server than are
> defined in server licensing properties? (I will have only one CAL for
DEP_1
> and server will never know, who is currently logged into MyApplication)
> 4. Is user CAL always "mapped" (=issued) to real person?
> 5. What if MyApplication from previous post will be a windows service with
> no UI interraction [no user logs into it. It will run on background on
three
> PCs and process some results]. Could it use only one user CAL then?
> Bweh, I know, silly questions, but I'm lost in all these licensing
options.[vbcol=seagreen]
> Thanks!
> "Mike Epprecht (SQL MVP)" wrote:
meant by[vbcol=seagreen]
id[vbcol=seagreen]
through[vbcol=seagreen]
copies[vbcol=seagreen]
access[vbcol=seagreen]
Info=True;Connection[vbcol=seagreen]
for all[vbcol=seagreen]
|||Prior to one of the service packs, not 3 or 3a, the number of CALs
restricted the number of concurrent user connections. You'd get errors
similar to those you see in MSDE when you exceed 8. Since the service pack,
however, the concurrent connections is limited only by a sp_configure
setting. However, there is nothing but paper that says you can't run
Developer Edition in production, but, then, that's why the paper was
written. The U.S. Constitution is nothing but paper, but if they catch you,
there's all sorts of pleasures waiting for you and your wallet.
Sincerely,
Anthony Thomas

"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uYtjOLCyEHA.3976@.TK2MSFTNGP09.phx.gbl...
> 1. Yes, but if you don't follow the paper rules, you get very expensive
> paperwork from Microsoft layers when they catch you.
> 2. On The server, go to Administrative Tools > Licensing
> 3. It does not know, but you are responsible. Point 2 can help you report
on
> it.
> 4. A CAL can be for a physical user or device and by the licensing terms,
it
> can only be transferred once to another user/device.
> 5. As long as the service does not get used by another program or service
to
> connect through it to the SQL Server (multiplexing)
> http://www.microsoft.com/sql/howtobuy/default.asp
> http://www.microsoft.com/sql/howtobuy/faq.asp
> The CAL actually says a lot:
>
http://download.microsoft.com/downlo...A9/caleula.pdf[vbcol=seagreen]
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Marek" <Marek@.discussions.microsoft.com> wrote in message
> news:F588172A-B890-4D60-962B-8B211B7CD9C8@.microsoft.com...
> Server
are[vbcol=seagreen]
> DEP_1
with[vbcol=seagreen]
> three
> options.
> meant by
> id
> through
three[vbcol=seagreen]
> copies
to
> access
> Info=True;Connection
> for all
>