Re: SQL Server 2005 Licensing concern.

On Mar 5, 5:42 pm, "David Portas"
<REMOVE_BEFORE_REPLYING_dpor...@xxxxxxx> wrote:
"Guillermo_Lopez" <g.lo...@xxxxxxxxx> wrote in message

news:327c1c3a-3b92-41a9-b5eb-a4191798ccf1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx





Hello,

Our company has developed several Access applications for our clients
and we wish to expand to use a database server. We wish to use Access
as the front end application and SQL Server 2005 as the back end
Databes Server. Making a Server-Client application database.

I'm very new to SQL Server so my concern is how the licensing works
for a developer like us. I am aware that we can purchase the Developer
edition for $49 USD. Our clients will then have to purchase a their
respective licensing option.

We do not have an issue with this, but i would like a better
understanding of how this works.

1) The developer edition (DE) is the same as the Enterprise edition.
Would our clients have to buy the Enterprise edition ($24,999) if we
develop the SQL server in the DE?  Or can they purchase the Standard
or Workgroup edition if the workload allows it?

2) If the client already has the Enterprise Edition on the Server we
wish to use, will they have to buy the license again if we create the
Database? Can they import our Database to thier SQL Server, and our
application connects to thiers?

3) Is there other options that would require a cheaper option for our
clients?

4) With just the DE, can we develope applications and use the
appropriate edition for our clients whatever it is?

5) To test our products we thought of using the Trial version to
simulate a multi-user test environment? Since thats just a 180 day
trial, perhaps the Worgroup Edition or the Light weight Edition might
work. But these editions might not be compatible with our clients'
requirements. The DE doesn't seem to handle multi-user environments,
so we cant effectively test how the application will perform in the
"real world". Any advices here?

Our clients range from small bussiness to nation-wide to multi-
national companies.

Thanks,

- GL

The client can use whatever edition suits your application and their needs..
It's the client's repsonsibility to ensure they are properly licensed. The
cheapest is Express Edition (free to acquire).http://www.microsoft.com/sql/howtobuy/licensing.mspx

I don't know why you think that DE doesn't handle "multi-user environments".
DE can do everything that Enterprise can do. DE is licensed per developer
and is very suitable for test purposes. The only problem comes if you want
to test against a Standard or Workgroup install because there is no Standard
or Workgroup equivalent of DE (the Trial edition is equivalent to a
time-limited version of DE). I think your cheapest option for a Standard or
Workgroup test environment is to get an MSDN subscription, which gives you
all the editions.

--
David Portas- Hide quoted text -

- Show quoted text -

Thaks for the quick reply both of you. This is pretty much what I
expected, but i needed to clarify some things that weren't said on the
MicroSoft sales pitch.

Its not that I dont think that the DE can't handled multi user
environment. Since we will only license one DE that means that one one
of us can use it at a time. So we wouldn't be able to test how the
application and SQL server responses to several users at the same
time. However, this seems like a non-issue, and I'm sure there are
work-arounds for this.

Thanks

- GL
.

Relevant Pages

  • Re: MS Access DAO -> ADO.NET Migration
    ... William Vaughn ... Microsoft MVP ... Hitchhiker's Guide to Visual Studio and SQL Server ... My migration app works building a SSCE database file with imported data ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Cluster will not fail over.
    ... > As far as the TCP/IP issue goes, you had to rebuild the cluster and were ... > able to restore the master database. ... > a cluster installation you'll have to revisit. ... >> This worked bringing up the sql server in minimal mode. ...
    (microsoft.public.sqlserver.clustering)
  • Re: MS Access DAO -> ADO.NET Migration
    ... full SQL Server and I see the logic you explained in a multi user ... allow two users to access the same database file Read/Write at any given ... The book was a pleasure to read after the gibberish that Microsoft 'puts ... Hitchhiker's Guide to Visual Studio and SQL Server ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: MS Access DAO -> ADO.NET Migration
    ... For that it is much harder to handle the incremental identifier, ... database but although they have the data, they are not connected at the same ... The book was a pleasure to read after the gibberish that Microsoft 'puts ... SQL Server Management Studio is nowhere to be found on my ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Why not Access...?
    ... It well depends how the database is used, such as the data access work load, ... When using Jet database, either VB front-end or Access front/back ... On the other hand, a database server, like SQL Server, gives you a lot more ... > 9i just can't work on these machines, and my clients are having these ...
    (microsoft.public.sqlserver.server)
Loading