Hi all,
I read different statements below and now I'm totally confused. My case is
as following: We want install SQLServer 2000 Standard Edition on a single
processor server. Our application Saperion is the only application which uses
that SQL instance. For Saperion we have a concurrent licensing model. That
means we have defined about 40 user who could use these applicaton, but at
the same time only 20 user have access. So, in maximum 20 user can work with
Saperion with SQL as the database engine.
Now the question is what kind of license do I have to buy. I understand the
processor licensing model, but the device CAL's and User CAL's not!
Thank you for your kind help in this matter.
Regards,
KE
User and device CAL licensing is based on total numbers rather than
concurrent numbers. On the information given it seems you would need 40 user
CALs if you chose the User CAL model. Device CALs are licensed per end-user
device so if you have multiple users sharing a workstation for example then
device CALs may be more cost effective than user CALs.
That's my understanding, but don't take my word for it. Ask a Microsoft
representative if you want a definitive answer.
Lots of info on licensing here:
http://www.microsoft.com/sql/howtobuy/default.asp
You may find the FAQ helpful.
David Portas
SQL Server MVP
|||Hi David,
Thank you very much for your answer. 40 user CAL's are not logical for me,
because Saperion never allows us to have more than 20 users online. That
means maximum 20 users can use the SQL server at a certain time. Logical for
me would be 20 user CAL's. If I'm wrong, tell me why......
Best regards,
KE
"David Portas" wrote:
> User and device CAL licensing is based on total numbers rather than
> concurrent numbers. On the information given it seems you would need 40 user
> CALs if you chose the User CAL model. Device CALs are licensed per end-user
> device so if you have multiple users sharing a workstation for example then
> device CALs may be more cost effective than user CALs.
> That's my understanding, but don't take my word for it. Ask a Microsoft
> representative if you want a definitive answer.
> Lots of info on licensing here:
> http://www.microsoft.com/sql/howtobuy/default.asp
> You may find the FAQ helpful.
> --
> David Portas
> SQL Server MVP
> --
>
|||SQL Server isn't licensed per CONCURRENT user. The fact that Saperion is
licensed that way wouldn't affect SQL Server licensing.
A user licence grants A USER a licence to use the software so one licence is
required PER USER not per connection or connected user.
David Portas
SQL Server MVP
|||Hi David,
Thank you very much for your explanation. In my point of view the SQL
licensing NOT per CONCURRENT user is very strange. Logical for me would be
only the CONCURRENT approach. However MS can do what they want!?!?!?
I have following additional question. Do we need for each SQL server
installation CAL's for all possible user (40 in our case)?
Example 1:
2 SQL Server Standard with user CAL's, 40 user can work with applications,
which use these servers.
Do we need 2 server licenses and 40 CAL's or 80 CAL's?
Example 2:
1 SQL Server Standard with processor license, 1 SQL Server Standard with
user CAL's.
According to MS homepage for the SQL Server with processor license I do not
need any CAL's. Is that correct? If yes, I assume that we need 1 server
license and 40 CAL's for the second SQL installation?
Thank you very much in advance.
Regards,
KE
"David Portas" wrote:
> SQL Server isn't licensed per CONCURRENT user. The fact that Saperion is
> licensed that way wouldn't affect SQL Server licensing.
> A user licence grants A USER a licence to use the software so one licence is
> required PER USER not per connection or connected user.
> --
> David Portas
> SQL Server MVP
> --
>
|||Inline below:
> I have following additional question. Do we need for each SQL server
> installation CAL's for all possible user (40 in our case)?
> Example 1:
> 2 SQL Server Standard with user CAL's, 40 user can work with applications,
> which use these servers.
> Do we need 2 server licenses and 40 CAL's or 80 CAL's?
2 server licenses. 40 CAL's. You can look at it like each user has a piece of paper that gives
him/her the right to connect to SQL Servers.
> Example 2:
> 1 SQL Server Standard with processor license, 1 SQL Server Standard with
> user CAL's.
> According to MS homepage for the SQL Server with processor license I do not
> need any CAL's. Is that correct? If yes, I assume that we need 1 server
> license and 40 CAL's for the second SQL installation?
Correct.
FYI: To speak to someone regarding licensing:
You can call 1-800-426-9400 (select option 4), Monday through Friday, 6:00
A.M. to 6:00 P.M. (PST) to speak directly to a Microsoft licensing
specialist for licensing problem. Worldwide customers can use the Guide to
Worldwide Microsoft Licensing Sites
http://www.microsoft.com/licensing/index/worldwide.asp to find contact
information in their locations.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"KE" <KE@.discussions.microsoft.com> wrote in message
news:7D9A468D-FB00-4D72-AD37-2324CF8C84AF@.microsoft.com...[vbcol=seagreen]
> Hi David,
> Thank you very much for your explanation. In my point of view the SQL
> licensing NOT per CONCURRENT user is very strange. Logical for me would be
> only the CONCURRENT approach. However MS can do what they want!?!?!?
> I have following additional question. Do we need for each SQL server
> installation CAL's for all possible user (40 in our case)?
> Example 1:
> 2 SQL Server Standard with user CAL's, 40 user can work with applications,
> which use these servers.
> Do we need 2 server licenses and 40 CAL's or 80 CAL's?
> Example 2:
> 1 SQL Server Standard with processor license, 1 SQL Server Standard with
> user CAL's.
> According to MS homepage for the SQL Server with processor license I do not
> need any CAL's. Is that correct? If yes, I assume that we need 1 server
> license and 40 CAL's for the second SQL installation?
> Thank you very much in advance.
> Regards,
> KE
>
>
>
> "David Portas" wrote:
Showing posts with label licensing. Show all posts
Showing posts with label licensing. Show all posts
Sunday, March 11, 2012
Thursday, March 8, 2012
Another licensing question...
Hi,
Here is a brief intro about our application.
1) The client is a Borland C++ application acting as the front
end.
2) The client sends requests to our web server (IIS) over HTTPS.
3) The web server invokes a windows service.
4) The windows service calls a COM+ component.
5) The COM+ component accesses a SQL Server 2000 EE (Cluster). We
have 4 processor licenses.
6) There are few other applications, which run on another server,
accessing the SQL server also.
7) The COM+ component forwards client requests (after some
processing) to these applications.
8) These applications send the requests to external parties,
usually over one/two (not more) TCP connections.
9) The external parties send the responses to our requests
10) The responses from the external parties are routed back to the
clients thru the COM+ component.
When the client is started on the end user's desktop, it throws up
a logon screen where the user enters his user ID and password. This is
the first request from the client to the web server. If the
authentication (the user IDs and paasswords are stored in the SQL
server) is successful, he can send more requests (order entry
application). We have about 20 users right now who access the system
this way.
The client software is available for free download, but the user
ID/password is handed over only to a very restricted set of people. We
charge certain $$ per user per month.
We are duplicating this environment in another data center.
Now my question is since we have only about 20 users accessing the
SQL server, is it enough to get 1 server license and 20 CALs? There
may be other users, who might connect but fail to authenticate, though
that is a very very rare case. Even though they are invalid users, do
they make a genuine case for going for processor licenses?
Thanks & regards
zrb
I suggest you consult a Microsoft representative about this. What you
have described *may* constitute hosting. The standard retail licence
has a "no commercial hosting" clause so you may need to purchase a
service provider licence.
I say "may" because I have no real idea what Microsoft classes as
commercial hosting. In any case an authorised rep should be able to
give you a definitive answer.
David Portas
SQL Server MVP
|||Thanks. I am thoroughly confused now. :-) I'll contact a MS rep on
this.
David Portas wrote:
> I suggest you consult a Microsoft representative about this. What you
> have described *may* constitute hosting. The standard retail licence
> has a "no commercial hosting" clause so you may need to purchase a
> service provider licence.
> I say "may" because I have no real idea what Microsoft classes as
> commercial hosting. In any case an authorised rep should be able to
> give you a definitive answer.
> --
> David Portas
> SQL Server MVP
> --
|||Also, if I have 4 processor licenses (we paid $80,000 for them), but
have 2 Dual Processor servers, does this entitle me to install SQL
server on the two servers? In the same vein, can I go for 4 single
processor servers? :-)
|||Yes. A processor licence is just that - per processor. You just need a
licence for each processor in each server.
David Portas
SQL Server MVP
Here is a brief intro about our application.
1) The client is a Borland C++ application acting as the front
end.
2) The client sends requests to our web server (IIS) over HTTPS.
3) The web server invokes a windows service.
4) The windows service calls a COM+ component.
5) The COM+ component accesses a SQL Server 2000 EE (Cluster). We
have 4 processor licenses.
6) There are few other applications, which run on another server,
accessing the SQL server also.
7) The COM+ component forwards client requests (after some
processing) to these applications.
8) These applications send the requests to external parties,
usually over one/two (not more) TCP connections.
9) The external parties send the responses to our requests
10) The responses from the external parties are routed back to the
clients thru the COM+ component.
When the client is started on the end user's desktop, it throws up
a logon screen where the user enters his user ID and password. This is
the first request from the client to the web server. If the
authentication (the user IDs and paasswords are stored in the SQL
server) is successful, he can send more requests (order entry
application). We have about 20 users right now who access the system
this way.
The client software is available for free download, but the user
ID/password is handed over only to a very restricted set of people. We
charge certain $$ per user per month.
We are duplicating this environment in another data center.
Now my question is since we have only about 20 users accessing the
SQL server, is it enough to get 1 server license and 20 CALs? There
may be other users, who might connect but fail to authenticate, though
that is a very very rare case. Even though they are invalid users, do
they make a genuine case for going for processor licenses?
Thanks & regards
zrb
I suggest you consult a Microsoft representative about this. What you
have described *may* constitute hosting. The standard retail licence
has a "no commercial hosting" clause so you may need to purchase a
service provider licence.
I say "may" because I have no real idea what Microsoft classes as
commercial hosting. In any case an authorised rep should be able to
give you a definitive answer.
David Portas
SQL Server MVP
|||Thanks. I am thoroughly confused now. :-) I'll contact a MS rep on
this.
David Portas wrote:
> I suggest you consult a Microsoft representative about this. What you
> have described *may* constitute hosting. The standard retail licence
> has a "no commercial hosting" clause so you may need to purchase a
> service provider licence.
> I say "may" because I have no real idea what Microsoft classes as
> commercial hosting. In any case an authorised rep should be able to
> give you a definitive answer.
> --
> David Portas
> SQL Server MVP
> --
|||Also, if I have 4 processor licenses (we paid $80,000 for them), but
have 2 Dual Processor servers, does this entitle me to install SQL
server on the two servers? In the same vein, can I go for 4 single
processor servers? :-)
|||Yes. A processor licence is just that - per processor. You just need a
licence for each processor in each server.
David Portas
SQL Server MVP
Another licensing question...
Hi,
Here is a brief intro about our application.
1) The client is a Borland C++ application acting as the front
end.
2) The client sends requests to our web server (IIS) over HTTPS.
3) The web server invokes a windows service.
4) The windows service calls a COM+ component.
5) The COM+ component accesses a SQL Server 2000 EE (Cluster). We
have 4 processor licenses.
6) There are few other applications, which run on another server,
accessing the SQL server also.
7) The COM+ component forwards client requests (after some
processing) to these applications.
8) These applications send the requests to external parties,
usually over one/two (not more) TCP connections.
9) The external parties send the responses to our requests
10) The responses from the external parties are routed back to the
clients thru the COM+ component.
When the client is started on the end user's desktop, it throws up
a logon screen where the user enters his user ID and password. This is
the first request from the client to the web server. If the
authentication (the user IDs and paasswords are stored in the SQL
server) is successful, he can send more requests (order entry
application). We have about 20 users right now who access the system
this way.
The client software is available for free download, but the user
ID/password is handed over only to a very restricted set of people. We
charge certain $$ per user per month.
We are duplicating this environment in another data center.
Now my question is since we have only about 20 users accessing the
SQL server, is it enough to get 1 server license and 20 CALs? There
may be other users, who might connect but fail to authenticate, though
that is a very very rare case. Even though they are invalid users, do
they make a genuine case for going for processor licenses?
Thanks & regards
zrbI suggest you consult a Microsoft representative about this. What you
have described *may* constitute hosting. The standard retail licence
has a "no commercial hosting" clause so you may need to purchase a
service provider licence.
I say "may" because I have no real idea what Microsoft classes as
commercial hosting. In any case an authorised rep should be able to
give you a definitive answer.
--
David Portas
SQL Server MVP
--|||Thanks. I am thoroughly confused now. :-) I'll contact a MS rep on
this.
David Portas wrote:
> I suggest you consult a Microsoft representative about this. What you
> have described *may* constitute hosting. The standard retail licence
> has a "no commercial hosting" clause so you may need to purchase a
> service provider licence.
> I say "may" because I have no real idea what Microsoft classes as
> commercial hosting. In any case an authorised rep should be able to
> give you a definitive answer.
> --
> David Portas
> SQL Server MVP
> --|||Also, if I have 4 processor licenses (we paid $80,000 for them), but
have 2 Dual Processor servers, does this entitle me to install SQL
server on the two servers? In the same vein, can I go for 4 single
processor servers? :-)|||Yes. A processor licence is just that - per processor. You just need a
licence for each processor in each server.
--
David Portas
SQL Server MVP
--
Here is a brief intro about our application.
1) The client is a Borland C++ application acting as the front
end.
2) The client sends requests to our web server (IIS) over HTTPS.
3) The web server invokes a windows service.
4) The windows service calls a COM+ component.
5) The COM+ component accesses a SQL Server 2000 EE (Cluster). We
have 4 processor licenses.
6) There are few other applications, which run on another server,
accessing the SQL server also.
7) The COM+ component forwards client requests (after some
processing) to these applications.
8) These applications send the requests to external parties,
usually over one/two (not more) TCP connections.
9) The external parties send the responses to our requests
10) The responses from the external parties are routed back to the
clients thru the COM+ component.
When the client is started on the end user's desktop, it throws up
a logon screen where the user enters his user ID and password. This is
the first request from the client to the web server. If the
authentication (the user IDs and paasswords are stored in the SQL
server) is successful, he can send more requests (order entry
application). We have about 20 users right now who access the system
this way.
The client software is available for free download, but the user
ID/password is handed over only to a very restricted set of people. We
charge certain $$ per user per month.
We are duplicating this environment in another data center.
Now my question is since we have only about 20 users accessing the
SQL server, is it enough to get 1 server license and 20 CALs? There
may be other users, who might connect but fail to authenticate, though
that is a very very rare case. Even though they are invalid users, do
they make a genuine case for going for processor licenses?
Thanks & regards
zrbI suggest you consult a Microsoft representative about this. What you
have described *may* constitute hosting. The standard retail licence
has a "no commercial hosting" clause so you may need to purchase a
service provider licence.
I say "may" because I have no real idea what Microsoft classes as
commercial hosting. In any case an authorised rep should be able to
give you a definitive answer.
--
David Portas
SQL Server MVP
--|||Thanks. I am thoroughly confused now. :-) I'll contact a MS rep on
this.
David Portas wrote:
> I suggest you consult a Microsoft representative about this. What you
> have described *may* constitute hosting. The standard retail licence
> has a "no commercial hosting" clause so you may need to purchase a
> service provider licence.
> I say "may" because I have no real idea what Microsoft classes as
> commercial hosting. In any case an authorised rep should be able to
> give you a definitive answer.
> --
> David Portas
> SQL Server MVP
> --|||Also, if I have 4 processor licenses (we paid $80,000 for them), but
have 2 Dual Processor servers, does this entitle me to install SQL
server on the two servers? In the same vein, can I go for 4 single
processor servers? :-)|||Yes. A processor licence is just that - per processor. You just need a
licence for each processor in each server.
--
David Portas
SQL Server MVP
--
Another licensing question...
Hi,
Here is a brief intro about our application.
1) The client is a Borland C++ application acting as the front
end.
2) The client sends requests to our web server (IIS) over HTTPS.
3) The web server invokes a windows service.
4) The windows service calls a COM+ component.
5) The COM+ component accesses a SQL Server 2000 EE (Cluster). We
have 4 processor licenses.
6) There are few other applications, which run on another server,
accessing the SQL server also.
7) The COM+ component forwards client requests (after some
processing) to these applications.
8) These applications send the requests to external parties,
usually over one/two (not more) TCP connections.
9) The external parties send the responses to our requests
10) The responses from the external parties are routed back to the
clients thru the COM+ component.
When the client is started on the end user's desktop, it throws up
a logon screen where the user enters his user ID and password. This is
the first request from the client to the web server. If the
authentication (the user IDs and paasswords are stored in the SQL
server) is successful, he can send more requests (order entry
application). We have about 20 users right now who access the system
this way.
The client software is available for free download, but the user
ID/password is handed over only to a very restricted set of people. We
charge certain $$ per user per month.
We are duplicating this environment in another data center.
Now my question is since we have only about 20 users accessing the
SQL server, is it enough to get 1 server license and 20 CALs? There
may be other users, who might connect but fail to authenticate, though
that is a very very rare case. Even though they are invalid users, do
they make a genuine case for going for processor licenses?
Thanks & regards
zrbI suggest you consult a Microsoft representative about this. What you
have described *may* constitute hosting. The standard retail licence
has a "no commercial hosting" clause so you may need to purchase a
service provider licence.
I say "may" because I have no real idea what Microsoft classes as
commercial hosting. In any case an authorised rep should be able to
give you a definitive answer.
David Portas
SQL Server MVP
--|||Thanks. I am thoroughly confused now. :-) I'll contact a MS rep on
this.
David Portas wrote:
> I suggest you consult a Microsoft representative about this. What you
> have described *may* constitute hosting. The standard retail licence
> has a "no commercial hosting" clause so you may need to purchase a
> service provider licence.
> I say "may" because I have no real idea what Microsoft classes as
> commercial hosting. In any case an authorised rep should be able to
> give you a definitive answer.
> --
> David Portas
> SQL Server MVP
> --|||Also, if I have 4 processor licenses (we paid $80,000 for them), but
have 2 Dual Processor servers, does this entitle me to install SQL
server on the two servers? In the same vein, can I go for 4 single
processor servers? :-)|||Yes. A processor licence is just that - per processor. You just need a
licence for each processor in each server.
David Portas
SQL Server MVP
--
Here is a brief intro about our application.
1) The client is a Borland C++ application acting as the front
end.
2) The client sends requests to our web server (IIS) over HTTPS.
3) The web server invokes a windows service.
4) The windows service calls a COM+ component.
5) The COM+ component accesses a SQL Server 2000 EE (Cluster). We
have 4 processor licenses.
6) There are few other applications, which run on another server,
accessing the SQL server also.
7) The COM+ component forwards client requests (after some
processing) to these applications.
8) These applications send the requests to external parties,
usually over one/two (not more) TCP connections.
9) The external parties send the responses to our requests
10) The responses from the external parties are routed back to the
clients thru the COM+ component.
When the client is started on the end user's desktop, it throws up
a logon screen where the user enters his user ID and password. This is
the first request from the client to the web server. If the
authentication (the user IDs and paasswords are stored in the SQL
server) is successful, he can send more requests (order entry
application). We have about 20 users right now who access the system
this way.
The client software is available for free download, but the user
ID/password is handed over only to a very restricted set of people. We
charge certain $$ per user per month.
We are duplicating this environment in another data center.
Now my question is since we have only about 20 users accessing the
SQL server, is it enough to get 1 server license and 20 CALs? There
may be other users, who might connect but fail to authenticate, though
that is a very very rare case. Even though they are invalid users, do
they make a genuine case for going for processor licenses?
Thanks & regards
zrbI suggest you consult a Microsoft representative about this. What you
have described *may* constitute hosting. The standard retail licence
has a "no commercial hosting" clause so you may need to purchase a
service provider licence.
I say "may" because I have no real idea what Microsoft classes as
commercial hosting. In any case an authorised rep should be able to
give you a definitive answer.
David Portas
SQL Server MVP
--|||Thanks. I am thoroughly confused now. :-) I'll contact a MS rep on
this.
David Portas wrote:
> I suggest you consult a Microsoft representative about this. What you
> have described *may* constitute hosting. The standard retail licence
> has a "no commercial hosting" clause so you may need to purchase a
> service provider licence.
> I say "may" because I have no real idea what Microsoft classes as
> commercial hosting. In any case an authorised rep should be able to
> give you a definitive answer.
> --
> David Portas
> SQL Server MVP
> --|||Also, if I have 4 processor licenses (we paid $80,000 for them), but
have 2 Dual Processor servers, does this entitle me to install SQL
server on the two servers? In the same vein, can I go for 4 single
processor servers? :-)|||Yes. A processor licence is just that - per processor. You just need a
licence for each processor in each server.
David Portas
SQL Server MVP
--
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
>
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
>
Another licensing question
I have a software (weblogic) that users (I have 2500 users) connect to.
Behind Weblogic I run a SQL 2000 server standard edition.
It is only Weblogic that connects to SQL (require 5 connections)
My question is, I was told to buy a SQL processor license instead of a User
or Device CAL?
Why spend 15000$ for a processor license when I can only get 5 CALS ?
Thanks for any help
JP
JP Breton wrote:
> I have a software (weblogic) that users (I have 2500 users) connect
> to.
> Behind Weblogic I run a SQL 2000 server standard edition.
> It is only Weblogic that connects to SQL (require 5 connections)
> My question is, I was told to buy a SQL processor license instead of
> a User or Device CAL?
> Why spend 15000$ for a processor license when I can only get 5 CALS ?
> Thanks for any help
> JP
Q. How do I license SQL Server 2000 CALs in a multiplexed
environment?
A. In most cases Microsoft requires a CAL for every device that
accesses or uses the services of SQL Server 2000. If you are unsure
whether a CAL is required, you should contact your Microsoft sales
representative or account manager. Inquires can be directed to Microsoft
Licensing by calling (800)426-9400.
David Gugick
Quest Software
www.imceda.com
www.quest.com
Behind Weblogic I run a SQL 2000 server standard edition.
It is only Weblogic that connects to SQL (require 5 connections)
My question is, I was told to buy a SQL processor license instead of a User
or Device CAL?
Why spend 15000$ for a processor license when I can only get 5 CALS ?
Thanks for any help
JP
JP Breton wrote:
> I have a software (weblogic) that users (I have 2500 users) connect
> to.
> Behind Weblogic I run a SQL 2000 server standard edition.
> It is only Weblogic that connects to SQL (require 5 connections)
> My question is, I was told to buy a SQL processor license instead of
> a User or Device CAL?
> Why spend 15000$ for a processor license when I can only get 5 CALS ?
> Thanks for any help
> JP
Q. How do I license SQL Server 2000 CALs in a multiplexed
environment?
A. In most cases Microsoft requires a CAL for every device that
accesses or uses the services of SQL Server 2000. If you are unsure
whether a CAL is required, you should contact your Microsoft sales
representative or account manager. Inquires can be directed to Microsoft
Licensing by calling (800)426-9400.
David Gugick
Quest Software
www.imceda.com
www.quest.com
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 b
y
> "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 throug
h
> 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 copi
es
> of MyApplication (PC1 and PC2 and PC3)).
> Each installation of MyApplication is using this connection string to acce
ss
> SQL Server:
> ConnStr = "User ID=DEP_1;Password=abc;Persist Security Info=True;Connectio
n
> 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 al
l
> 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 t
hree
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/downl.../>
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:
>
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: [url]http://www.microsoft.com/mvp" target="_blank">http://download.microsoft.com/downl...crosoft.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[vbcol=seagreen]
> access
> Info=True;Connection
> for all
>
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 b
y
> "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 throug
h
> 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 copi
es
> of MyApplication (PC1 and PC2 and PC3)).
> Each installation of MyApplication is using this connection string to acce
ss
> SQL Server:
> ConnStr = "User ID=DEP_1;Password=abc;Persist Security Info=True;Connectio
n
> 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 al
l
> 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 t
hree
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/downl.../>
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:
>
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: [url]http://www.microsoft.com/mvp" target="_blank">http://download.microsoft.com/downl...crosoft.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[vbcol=seagreen]
> access
> Info=True;Connection
> for all
>
Another licensing question
I have a software (weblogic) that users (I have 2500 users) connect to.
Behind Weblogic I run a SQL 2000 server standard edition.
It is only Weblogic that connects to SQL (require 5 connections)
My question is, I was told to buy a SQL processor license instead of a User
or Device CAL?
Why spend 15000$ for a processor license when I can only get 5 CALS '
Thanks for any help
JPJP Breton wrote:
> I have a software (weblogic) that users (I have 2500 users) connect
> to.
> Behind Weblogic I run a SQL 2000 server standard edition.
> It is only Weblogic that connects to SQL (require 5 connections)
> My question is, I was told to buy a SQL processor license instead of
> a User or Device CAL?
> Why spend 15000$ for a processor license when I can only get 5 CALS '
> Thanks for any help
> JP
Q. How do I license SQL Server 2000 CALs in a multiplexed
environment?
A. In most cases Microsoft requires a CAL for every device that
accesses or uses the services of SQL Server 2000. If you are unsure
whether a CAL is required, you should contact your Microsoft sales
representative or account manager. Inquires can be directed to Microsoft
Licensing by calling (800)426-9400.
David Gugick
Quest Software
www.imceda.com
www.quest.com
Behind Weblogic I run a SQL 2000 server standard edition.
It is only Weblogic that connects to SQL (require 5 connections)
My question is, I was told to buy a SQL processor license instead of a User
or Device CAL?
Why spend 15000$ for a processor license when I can only get 5 CALS '
Thanks for any help
JPJP Breton wrote:
> I have a software (weblogic) that users (I have 2500 users) connect
> to.
> Behind Weblogic I run a SQL 2000 server standard edition.
> It is only Weblogic that connects to SQL (require 5 connections)
> My question is, I was told to buy a SQL processor license instead of
> a User or Device CAL?
> Why spend 15000$ for a processor license when I can only get 5 CALS '
> Thanks for any help
> JP
Q. How do I license SQL Server 2000 CALs in a multiplexed
environment?
A. In most cases Microsoft requires a CAL for every device that
accesses or uses the services of SQL Server 2000. If you are unsure
whether a CAL is required, you should contact your Microsoft sales
representative or account manager. Inquires can be directed to Microsoft
Licensing by calling (800)426-9400.
David Gugick
Quest Software
www.imceda.com
www.quest.com
Another licensing question
I have a software (weblogic) that users (I have 2500 users) connect to.
Behind Weblogic I run a SQL 2000 server standard edition.
It is only Weblogic that connects to SQL (require 5 connections)
My question is, I was told to buy a SQL processor license instead of a User
or Device CAL?
Why spend 15000$ for a processor license when I can only get 5 CALS '
Thanks for any help
JPJP Breton wrote:
> I have a software (weblogic) that users (I have 2500 users) connect
> to.
> Behind Weblogic I run a SQL 2000 server standard edition.
> It is only Weblogic that connects to SQL (require 5 connections)
> My question is, I was told to buy a SQL processor license instead of
> a User or Device CAL?
> Why spend 15000$ for a processor license when I can only get 5 CALS '
> Thanks for any help
> JP
Q. How do I license SQL Server 2000 CALs in a multiplexed
environment?
A. In most cases Microsoft requires a CAL for every device that
accesses or uses the services of SQL Server 2000. If you are unsure
whether a CAL is required, you should contact your Microsoft sales
representative or account manager. Inquires can be directed to Microsoft
Licensing by calling (800)426-9400.
David Gugick
Quest Software
www.imceda.com
www.quest.com
Behind Weblogic I run a SQL 2000 server standard edition.
It is only Weblogic that connects to SQL (require 5 connections)
My question is, I was told to buy a SQL processor license instead of a User
or Device CAL?
Why spend 15000$ for a processor license when I can only get 5 CALS '
Thanks for any help
JPJP Breton wrote:
> I have a software (weblogic) that users (I have 2500 users) connect
> to.
> Behind Weblogic I run a SQL 2000 server standard edition.
> It is only Weblogic that connects to SQL (require 5 connections)
> My question is, I was told to buy a SQL processor license instead of
> a User or Device CAL?
> Why spend 15000$ for a processor license when I can only get 5 CALS '
> Thanks for any help
> JP
Q. How do I license SQL Server 2000 CALs in a multiplexed
environment?
A. In most cases Microsoft requires a CAL for every device that
accesses or uses the services of SQL Server 2000. If you are unsure
whether a CAL is required, you should contact your Microsoft sales
representative or account manager. Inquires can be directed to Microsoft
Licensing by calling (800)426-9400.
David Gugick
Quest Software
www.imceda.com
www.quest.com
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:
> 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!|||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/download/5/E/7/5E7B79D4-90B8-4A3D-B964-8A72F49A21A9/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.
> Thanks!
> "Mike Epprecht (SQL MVP)" wrote:
> > 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!|||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/download/5/E/7/5E7B79D4-90B8-4A3D-B964-8A72F49A21A9/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.
> >
> > Thanks!
> >
> > "Mike Epprecht (SQL MVP)" wrote:
> >
> > > 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!
>
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:
> 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!|||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/download/5/E/7/5E7B79D4-90B8-4A3D-B964-8A72F49A21A9/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.
> Thanks!
> "Mike Epprecht (SQL MVP)" wrote:
> > 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!|||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/download/5/E/7/5E7B79D4-90B8-4A3D-B964-8A72F49A21A9/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.
> >
> > Thanks!
> >
> > "Mike Epprecht (SQL MVP)" wrote:
> >
> > > 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!
>
Subscribe to:
Posts (Atom)