Re: Licensing Questions

From: Geoff N. Hiten (SRDBA_at_Careerbuilder.com)
Date: 08/18/04


Date: Wed, 18 Aug 2004 15:46:38 -0400

First you need to decide which edition of SQL you need. Standard Edition is
probably the best default choice. You then need to determine if your
organization has an Open or Select licensing agreement with Microsoft. If
so, you need to work with your licensing person and possibly a Microsoft
sales contact. Other factors include whether your organization has other
SQL servers or might have other SQL servers in the near future. Lotsa
servers usually means CALs are cheaper A few servers and lotsa clients
generally favors per-processor licensing. You will need to price multiple
ways and see which is cheaper. Licensing is confusing but it is much better
than the older way which made it prohibitively expensive to use SQL in
certain circumstances.

You can also work with some major hardware vendors (Dell, HP, etc.) to help
size and price servers and licensing for SQL. Most will be happy to offer
assistance. Of course they will recommend their particular platform. :)

-- 
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Cheryl" <Cheriiac@hotmail.com> wrote in message
news:%23OaoYJVhEHA.2848@TK2MSFTNGP10.phx.gbl...
> That's the page I read that got me confused to begin with =) I was
> hoping someone could give me a rough estimate of what it would cost for
> both the server that runs it and the SQL database for approximately 100
> users.
>
> Cheryl
>
> Geoff N. Hiten wrote:
>
> > Comments Inline
> >
> > Here is a link that may help;
> > http://www.microsoft.com/sql/howtobuy/default.asp
> >


Relevant Pages

  • Re: Performance
    ... Scale out is generally a matter of adding more ... SQL servers and distributing (usually via code but distributed partitions is ... also an option) your database and/or functions across them. ...
    (microsoft.public.dotnet.framework.performance)
  • Re: authentication
    ... that is connected to a SQL 2005 backend. ... for example on one of our SQL servers. ... This is the dialog box that has the checkbox for trusted connection, ID, ... This is not how this inherited db app has worked. ...
    (microsoft.public.access.formscoding)
  • Wierd connection problem
    ... Having an issue connecting to one of my SQL Servers that I just cannot ... uses a remote SQL Database with no problems. ... Using the identical connection string, my ASP.Net page can connect to ...
    (microsoft.public.sqlserver)
  • Merge Agent error number 53 for replication
    ... I am trying to setup replication between 2 SQL Servers across ... on both the distributor and subscriber to interact with each other. ... I've given the Snapshot folder UNC path and Administrative share the ...
    (microsoft.public.sqlserver.replication)
  • Merge Agent error number 53 for replication
    ... I am trying to setup replication between 2 SQL Servers across ... on both the distributor and subscriber to interact with each other. ... I've given the Snapshot folder UNC path and Administrative share the ...
    (microsoft.public.sqlserver.connect)