Tuesday, March 27, 2012

Determine Licenses currently in use.

How do I determine total client coneections that are currently being used by
the SQL Server?
We are developing an application that connects to a DB Server and downloads
the information particlular to that workstation, and then never hits the SQL
server again until the next user logs on.
We will have about 130 workstations that will hit the database at one point
via our application.
The question is; Do we need/require a CAL for each workstation? If not then
why? If so, if the server is only registering one connection to the server
at any given time, why have all the CAL's?
Brian CookSounds like you would be better off with per processor licensing (unless you
have a large number of CPUs, or are running enterprise edition)
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Brian Cook" <anonymous@.discussions.microsoft.com> wrote in message
news:8EE3CFCC-EBBF-4095-A99A-67B3B85AC309@.microsoft.com...
> How do I determine total client coneections that are currently being used
by the SQL Server?
> We are developing an application that connects to a DB Server and
downloads the information particlular to that workstation, and then never
hits the SQL server again until the next user logs on.
> We will have about 130 workstations that will hit the database at one
point via our application.
> The question is; Do we need/require a CAL for each workstation? If not
then why? If so, if the server is only registering one connection to the
server at any given time, why have all the CAL's?
> Brian Cook|||Hi,
How do I determine total client coneections that are currently being used
by the SQL Server?
Execute the below script in Query analyzer to identify the mode of license
used and the count.
select serverproperty('LicenseType')
go
select serverproperty('NumLicenses'
The question is; Do we need/require a CAL for each workstation? If not then
why?
I feel that you need to get seperate licenses for each user connectiong even
though they wint access concurrently
Thanks
Hari
MCDBA
"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:u9jCUoLHEHA.2744@.TK2MSFTNGP10.phx.gbl...
> Sounds like you would be better off with per processor licensing (unless
you
> have a large number of CPUs, or are running enterprise edition)
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> "Brian Cook" <anonymous@.discussions.microsoft.com> wrote in message
> news:8EE3CFCC-EBBF-4095-A99A-67B3B85AC309@.microsoft.com...
used
> by the SQL Server?
> downloads the information particlular to that workstation, and then never
> hits the SQL server again until the next user logs on.
> point via our application.
> then why? If so, if the server is only registering one connection to the
> server at any given time, why have all the CAL's?
>|||http://www.microsoft.com/sql/howtobuy/default.asp
There are device CALs and user CALs. I don't know the retail price of an
individual CAL, but if it is even as low as $50, you have already passed
what the cost would be for a one CPU processor license.
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Brian Cook" <anonymous@.discussions.microsoft.com> wrote in message
news:8EE3CFCC-EBBF-4095-A99A-67B3B85AC309@.microsoft.com...
> How do I determine total client coneections that are currently being used
by the SQL Server?
> We are developing an application that connects to a DB Server and
downloads the information particlular to that workstation, and then never
hits the SQL server again until the next user logs on.
> We will have about 130 workstations that will hit the database at one
point via our application.
> The question is; Do we need/require a CAL for each workstation? If not
then why? If so, if the server is only registering one connection to the
server at any given time, why have all the CAL's?
> Brian Cook|||Cost wise, it would be cheaper to purchase licenses for each client. This be
ing an Enterprise application we are designing, and the SQL Servers are inte
nded to be Quad processor computers, it would not be cost effective to run t
he per processor version. A
lthough the unlimited amount of licenses is attractive, I do not see the jus
tification/need for the expense. (god I sound like an accountant! Ack! Ack!
plaaaa!).
Thanks,
Brian
-- Kevin3NF wrote: --
http://www.microsoft.com/sql/howtobuy/default.asp
There are device CALs and user CALs. I don't know the retail price of an
individual CAL, but if it is even as low as $50, you have already passed
what the cost would be for a one CPU processor license.
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Brian Cook" <anonymous@.discussions.microsoft.com> wrote in message
news:8EE3CFCC-EBBF-4095-A99A-67B3B85AC309@.microsoft.com...
> How do I determine total client coneections that are currently being used
by the SQL Server?
downloads the information particlular to that workstation, and then never
hits the SQL server again until the next user logs on.
point via our application.
then why? If so, if the server is only registering one connection to the
server at any given time, why have all the CAL's?|||Hari, thanks for the script, however it does not tell me how many licenses a
re currently in use by the users/computer connections. This tells me how man
y licenses are INSTALLED to the SQL server. I need to know/validate how many
are being used at any give
n time.
Thanks,
Brian
-- Hari Prasad wrote: --
Hi,
How do I determine total client coneections that are currently being used
by the SQL Server?
Execute the below script in Query analyzer to identify the mode of license
used and the count.
select serverproperty('LicenseType')
go
select serverproperty('NumLicenses'
The question is; Do we need/require a CAL for each workstation? If not then
why?
I feel that you need to get seperate licenses for each user connectiong even
though they wint access concurrently
Thanks
Hari
MCDBA
"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:u9jCUoLHEHA.2744@.TK2MSFTNGP10.phx.gbl...
> Sounds like you would be better off with per processor licensing (unless
you
> have a large number of CPUs, or are running enterprise edition)
> Kevin Hill
> President
> 3NF Consulting
> news:8EE3CFCC-EBBF-4095-A99A-67B3B85AC309@.microsoft.com...
used
> by the SQL Server?
> downloads the information particlular to that workstation, and then never
> hits the SQL server again until the next user logs on.
> point via our application.
> then why? If so, if the server is only registering one connection to the
> server at any given time, why have all the CAL's?|||I spoke with Microsoft this morning, and there is no way built into SQL to d
etermine how many current client access licenses, so the answer is that I mu
st have a CAL for each workstation.
Individual CAL's are cheaper than the Per Processor model in this instance.
Thanks for the suggestions guys.
Brian
-- Brian Cook wrote: --
How do I determine total client coneections that are currently being used by
the SQL Server?
We are developing an application that connects to a DB Server and downloads
the information particlular to that workstation, and then never hits the SQL
server again until the next user logs on.
We will have about 130 workstations that will hit the database at one point
via our application.
The question is; Do we need/require a CAL for each workstation? If not then
why? If so, if the server is only registering one connection to the server
at any given time, why have all the CAL's?
Brian Cook

No comments:

Post a Comment