liscensing for client tools?

We bought SQL2K and have it installed on a server. Can I just go and load
the client tools on all the workstations that I want, or are there
liscensing concerns with doing that? If anyone knows of web page links that
outlines this it would be helpful for me to print that to show management to
make them more comfortable.
Scott
I am guessing that you have purchased the appropriate number of licenses, or
you went with per-processor licensing. In either case you should be ok to
install the client tools on the developer machines.
End users do not need the client tools as they will be accessing the
database via a GUI that you guys wrote or purchased.
Keith
"Schoo" <scott.schuman@.nospam.ma-hc.com> wrote in message
news:uOmkIw7fEHA.3556@.TK2MSFTNGP12.phx.gbl...
> We bought SQL2K and have it installed on a server. Can I just go and load
> the client tools on all the workstations that I want, or are there
> liscensing concerns with doing that? If anyone knows of web page links
that
> outlines this it would be helpful for me to print that to show management
to
> make them more comfortable.
> Scott
>
|||If you have a licensed copy of SQL Server you can install the client tools
on as many machines as you want to connect to this SQL Server. The only
limitation is the concurrent number of users that can connect. This is
governed by your license agreement.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thanks, Rand!
I could not have said it better myself!
Keith
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:GWZYLg8fEHA.3212@.cpmsftngxa06.phx.gbl...
> If you have a licensed copy of SQL Server you can install the client tools
> on as many machines as you want to connect to this SQL Server. The only
> limitation is the concurrent number of users that can connect. This is
> governed by your license agreement.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>
|||Rand,
Correct me if I'm wrong, but didn't the "concurrent number of users"
licensing model go away in SQL Server 2000? The original poster didn't
specify what version of SQL Server s/he was using, but in 2000 the only
licensing models are processor licensing and CAL licensing. There is no
license option that simply enforces a limit on the number of concurrent
users. My understanding of the licensing requirements for the tools
(for SQL Server 2000) is this:
1) If the SQL Server license is a processor license, the license allows
unlimited installation of the tools within the organization holding the
processor license, to connect to that licensed server. I'm not sure
where there's an exact definition of "within the organization", but I
assume this means on computers owned by the licensee and used by
employees of the licensee.
2) If the SQL Server license is a server license, then a CAL (client
access license) is required to connect to that server. Whether or not
the tools can be installed and used without connecting to the server,
I'm not sure, but that's likely not the question here. I don't believe
the tools are redistributable, in any case.
http://support.microsoft.com/?id=257716
Steve Kass
Drew University
Rand Boyd [MSFT] wrote:

>If you have a licensed copy of SQL Server you can install the client tools
>on as many machines as you want to connect to this SQL Server. The only
>limitation is the concurrent number of users that can connect. This is
>governed by your license agreement.
>Rand
>This posting is provided "as is" with no warranties and confers no rights.
>
>
|||Steve,
You response is correct. My answer about installing it on an many machines
as you wanted to assumed that the machines would be with in the
organization that owned the license to SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.