Re: Developer licensing in 2005
- From: "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
- Date: Thu, 23 Oct 2008 20:36:45 -0400
Answers inline:
"jdb" <jdb@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:94F4BF3F-E0CB-493F-9036-906D0D1D3408@xxxxxxxxxxxxxxxx
Hi,
I'm a bit unclear from the forum posts and the MS site.
Is it true that:
* You can use a developer license for a server that is used just for
development purposes and that it isn't limited to just a developers
workstation.
Depends on what your definition of a server is. If you are talking about a
SQL-Server instance then yes, a developer license can access this
sql-server; even if this sql-server comes from a MSDN subscription.
However, you must also take a look at the underlying Windows OS running this
machine. If this is a production server (Windows Server 2000, 2003, 2008,
SBS, etc.) and the developer has a CAL to access it, then there is no
problem. If this is a development server coming from a MSDN subscription,
then the developer which has only a SQL-Server developer license (ie., is
without a MSDN subscription license of a sufficient level for himself)
cannot access it and by the same token, cannot access any of the SQL-Server
instance running on it. If this Windows OS is not a server version but a
production workstation, then up to 10 external users (or devices) can
connect to it simultaneously, so your developer with a sql-server developer
license can access any sql-server developer running on it at the condition
that there is no more 10 users/developers accessing this machine at the same
time. (And by accessing this machine, this could be in any way, for example
accessing a file on it. This doesn't have to be 10 access to the sql-server
developer instance itself.). If Terminal Server is used to access this
server, then a CAL for TS is also required.
A production workstation is simply any ordinary copy of Windows; ie., one
that doesn't come from a MSDN subscription and that is not a Windows Server
OS.
Notice also that a production server (either for SQL-Server or for Windows
Server) is not necessarily a server that is used only or partially used as a
production server. It's a server which has been bought with a production
license; which mean that it remains a production server forever even if your
intent is to use it exclusively for development. Any production server can
be used for development as much as you like and any user with all the
necessary CALs can access it for whatever use he/she want. Also, a
developer license cannot replace a CAL.
* The client tools to connect to that don't have to be licensed unless the
developer also has a sqlserver copy installed on their local workstation
as
well.
True and False. The client tools don't need to be licensed but you can use
them only to access a server for which you are licensed (ie., for which you
have all the required developer licenses, MSDN licenses and/or production
CALs (including TS if necessary) and/or this is a server licensed on a Per
Processor basis; without forgetting the Windows OS underneath).
* Users can connect to the development server to test the application code
as long as they aren't using it as a production or reporting environment.
True and False. The only exception is for users to access it in order to
perform a *stress performance test*; ie., to test it under an heavy load.
Any other form of testing are not permitted; which mean that any user
accessing a development server must also have all the required developer or
MSDN licenses (for the SQL-Server and for the Windows Server underneath if
this is not a workstation. More details below.).
* Lastly that the developer version isn't by processor or user cal - it
covers all connection types for the development/testing environment.
True, all developer versions (including the various MSDN subscriptions) are
licensed exclusively on a per user basis.
And is it also true that:
* If you have a server that is 99% development with 1% production database
mixed in then it can not run developer version. (Bad practice I know, but
it
happened and this will help me convince parties to move the tindy
production
database it to a production server when we upgrade and therby let me
switch
to a developer lisence on the server instead of standard.)
True if this is not a production server or an ordinary (production)
workstation. With a production server, you can do whatever you like; at the
condition that you have all the required licenses/CALs to access it. With a
workstation that is not from a MSDN subscription, you have to respect the
limit of ten simultaneous users connections. (If the workstation comes from
a MSDN subscription, then any user accessing it must also have a MSDN
subscription of a sufficient level. The same thing if this is a Windows
Server coming from a MSDN subscription.).
You can install the developer edition of SQL-Server on a production Windows
Server: people accessing it must have a developer license or a MSDN license
(of a sufficient level) for accessing the SQL-Server and a CAL for accessing
the Windows Server (because this is production server). If it's installed
on a Windows Server or a Workstation that comes from a MSDN subscription,
then everyone accessing the SQL-Server must also have a MSDN subscription; a
developer license won't make the cut in this case and you cannot replace the
MSDN subscription with a CAL. For an ordinary (retail) workstation (one
that doesn't come from a MSDN subscription), then you have to respect the
limit of 10 simultaneous users.
Thanks for the help!
You're welcome.
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
.
- References:
- Developer licensing in 2005
- From: jdb
- Developer licensing in 2005
- Prev by Date: RE: How to hook up TFS Source Control in Management Studio
- Next by Date: Re: How does one manage sql 2005 Licensing?
- Previous by thread: Re: Developer licensing in 2005
- Next by thread: Install of sql server 2008 express with advanced services fails without specific error
- Index(es):
Relevant Pages
|
