|
Home > Archive > microsoft.public.sqlserver.server > June 2002 > SQL License question
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SQL License question
|
|
|
| Hi,
I am looking at developing an application that will use a SQL server
Database, and I would like to understand the licensing rules for SQL server.
I noticed that on a Microsoft Office CD, you can install a SQL Service
Manager onto a local machine (not SQL enterprise manager). Does this mean
that this user can legitimately connect to a server on the LAN that is
running an SQL Database.
If this is true, then surely if all users on the LAN have licensed versions
of Microsoft Office, they can all legitimately connect to a Server on their
LAN that is running an application using SQL server. This should mean that
the company using my application would not have to buy SQL Server Enterprise
Manager, since they would never want to open the database ever. Rather, I
would be able to buy the SQL Server Enterprise Manager, and could remotely
connect to my clients databases if there was a need to.
Is this true? It makes sense to me; otherwise what is the reason for one
being able to install SQL Service Manager onto a local machine via Microsoft
Office installation CD.
Is SQL Server Enterprise Manager Licences therefore applicable only to users
that need to open the Enterprise Manager for database administration
purposes?
Thanks
David
| |
| ben brugman 2002-06-30, 5:25 am |
| Having the technical capability to connect, and
having a licence to connect are two very different things.
To my knowledge there are no licences for SQL Server Enterprise Manager.
If you are allowed to connect to a SQL-server you are allowed to use
the SQL SEM.
With all kinds of software (which is fairly standard) you can connect to
a SQL-server. (Most development systems have connectivity (using ODBC or
otherwise)).
For each user you should have a CAL. (Client Access Licence).
Or you should have a server licence for the SQL-server.
This is how I understand it. But it is far more complex than I have
represented here.
(Microsoft uses a lot of text to describe the exact licensing issues).
Please do not crosspost to so many newsgroups.
ben brugman.
"David" <News@lala.la> wrote in message
news:3d1ee23d$0$18848@hades.is.co.za...
> Hi,
>
>
>
> I am looking at developing an application that will use a SQL server
> Database, and I would like to understand the licensing rules for SQL
server.
>
>
>
> I noticed that on a Microsoft Office CD, you can install a SQL Service
> Manager onto a local machine (not SQL enterprise manager). Does this mean
> that this user can legitimately connect to a server on the LAN that is
> running an SQL Database.
>
>
>
> If this is true, then surely if all users on the LAN have licensed
versions
> of Microsoft Office, they can all legitimately connect to a Server on
their
> LAN that is running an application using SQL server. This should mean
that
> the company using my application would not have to buy SQL Server
Enterprise
> Manager, since they would never want to open the database ever. Rather, I
> would be able to buy the SQL Server Enterprise Manager, and could remotely
> connect to my clients databases if there was a need to.
>
>
>
> Is this true? It makes sense to me; otherwise what is the reason for one
> being able to install SQL Service Manager onto a local machine via
Microsoft
> Office installation CD.
>
>
>
> Is SQL Server Enterprise Manager Licences therefore applicable only to
users
> that need to open the Enterprise Manager for database administration
> purposes?
>
>
>
> Thanks
>
>
>
> David
>
>
>
>
>
| |
| Mary Chipman 2002-06-30, 1:25 pm |
| In future, do not post the same question to a zillion groups.
See the following resources for licensing questions:
http://www.microsoft.com/licensing/
http://www.microsoft.com/permission/
-- Mary
Microsoft Access Developer's Guide to SQL Server
http://www.amazon.com/exec/obidos/ASIN/0672319446
On Sun, 30 Jun 2002 12:49:09 +0200, "David" <News@lala.la> wrote:
>Hi,
>
>
>
>I am looking at developing an application that will use a SQL server
>Database, and I would like to understand the licensing rules for SQL server.
>
>
>
>I noticed that on a Microsoft Office CD, you can install a SQL Service
>Manager onto a local machine (not SQL enterprise manager). Does this mean
>that this user can legitimately connect to a server on the LAN that is
>running an SQL Database.
>
>
>
>If this is true, then surely if all users on the LAN have licensed versions
>of Microsoft Office, they can all legitimately connect to a Server on their
>LAN that is running an application using SQL server. This should mean that
>the company using my application would not have to buy SQL Server Enterprise
>Manager, since they would never want to open the database ever. Rather, I
>would be able to buy the SQL Server Enterprise Manager, and could remotely
>connect to my clients databases if there was a need to.
>
>
>
>Is this true? It makes sense to me; otherwise what is the reason for one
>being able to install SQL Service Manager onto a local machine via Microsoft
>Office installation CD.
>
>
>
>Is SQL Server Enterprise Manager Licences therefore applicable only to users
>that need to open the Enterprise Manager for database administration
>purposes?
>
>
>
>Thanks
>
>
>
>David
>
>
>
>
|
|
|
|
|