Microsoft adds SQL Server 2005 Workgroup Edition

February 25, 2005

Microsoft is Expanding their SQL Server 2005 Product Line, with the introduction of SQL Server Workgroup Edition. These new price points are no doubt in response to open source database competitors such as MySQL and PostgreSQL.

Here's an overview of the SQL Server 2005 editions, and their pricing:

	Express	Workgroup	Standard	Enterprise
Price	Free	$3,899/processor OR $739/5 users	$5,999/processor OR $2,799/10 users	$24,999/processor OR $13,499/25 users
Max CPUs	1	2	4	Unlimited
Max Ram	1 GB	2 GB	Unlimited	Unlimited
Features	Simple Management Tool Report Wizards & Controls Replication & SSB Client Replaces MSDE 2000	Management Studio Import/Export Limited Replication Publishing Backup Log Shipping	Database Mirroring OLAP Server Reporting Server New Integration Services Data Mining Full Replication & SSB Publishing	Advanced DB Mirroring Complete online and parallel operations DB Snapshot Advanced Analysis Tools OLAP, Data Mining Customized & High Scale Reporting Advanced SSIS
Previous Prices	Free	N/A	$4,999 per processor or $2,249 (server + 10 users)	$19,999 per processor or $11,099 (server + 25 users)

As you can see while the low end is easier to get into, but Microsoft has raised the prices on the high end (Standard and Enterprise versions of Microsoft SQL Server).

eWeek has also published an article on the new edition.

Permalink | Add Comment |

add to del.icio.us | Tags: microsoft, sqlserver, workgroup

Related Entries

Try Catch for SQLServer T-SQL - April 7, 2008
SQL Server Express 2005, Finally Installed - September 7, 2005
I give up! Installing SQL Server 2005 Express - February 25, 2005

3 people found this page useful, what do you think?

Trackbacks

Trackback Address: 250/25DDBCFE75498E0CABC0E684A6000079

Comments

On 02/25/2005 at 2:11:18 PM EST dave ross wrote:

what I never understood is the named user/device licensing in relation to web applications. You obvoiusly only need ONE user account to make a MSSQL database accessible to a web app, but is that a EULA violation (do you need a license for each user that hits a web-app that asks MSSQL for data?) I'm still not clear, although most places I encounter just buy the proc license and don't worry about it.

On 02/25/2005 at 6:48:39 PM EST Steven Ringo wrote:

M$ states you *have to* buy the processor licence in order to use it in a web application, be it inernet or intranet.

On 02/26/2005 at 12:11:55 AM EST gideon marken wrote:

>>> what I never understood is the named user/device licensing in relation to web applications

If your app provides 'services and/or hosted applications' with MSSQL Server, then you'd need to look into the MS SPLA: Spervice Provider License Agreement

http://www.microsoft.com/serviceproviders/licensing/acquirespla/spla.mspx

This license depends on the # of processors and the # of authenticated users. It's a monthly fee and you 'DO NOT' need to buy a copy of SQL Server, I was recently sent this quote:

-------------

For an unlimited number of anonymous users, each month you would report:

Windows Srv Std Unauthenticated Processor License is $18/mo SQL Std Processor License is $169/mo

For a two Processor box: 2x $18 win 2x $169 Win ------------- $374/mo

========================

12*374= $4,488

and MSSQL 2000 = $4,999 per processor

2 processors = $9,998 which is a bit more than $4,488

I suggest contacting MS, the representative I spoke with was helpful, and responded very fast.

//============================//

As to the real subject of this blog posting...

I think it's excellent that they are making these kinds of moves and expanding the line.

If you are going to run a Web service of any type... you'll have to get this SPLA, which I believe will give you the "Standard" edition. Based on those 2005 prices - you'd pay less with the SPLA if you are running a CF site with MSSQL 2005 on a dual processor where your users are not being authenticated by MS software/system.

It's worth looking into.

Sorry I babbled so long :)

- Gideon

On 11/17/2005 at 7:21:47 AM EST Jack London wrote:

Any tip to connect SQL Server 2005 from CFMX?

On 11/17/2005 at 9:27:50 AM EST Chris wrote:

Jack: SQL2005 has network connections disabled by default... you need to enable the TCP/IP protocol (SQL Server Configuration Manager). And, you can NOT use Windows authentication for SQL2005, if you use the standard CFMX drivers. You'll have to set it to Mixed Authentication

Best,

Chris

On 01/24/2006 at 11:45:22 PM EST Dave wrote:

For SQL 2005 std edition what is meant by $2,799/10 users? Do you get 10CALS with SQL when you pay $2799? OR is it limited to 10 users only?

On 04/04/2006 at 11:59:33 AM EDT anon wrote:

FREE VERSION HAS LTD REPLICATION SERVICES.

DO NOT USE IF YOU VALUE YOUR DATA

On 07/23/2006 at 9:35:44 AM EDT Vijay wrote:

Hi, I've a problem with installing sql server 2005 and Visual Studio 2005 on Windows Server 2003, will you give some instruction to do it properly. thanks...

On 11/26/2007 at 12:49:57 PM EST vanpooler wrote:

a. Does it make sense to try to install SqlServer05[version workgroup]in a "virtual" environment?

b. Does this question make any sense?

On 11/26/2007 at 1:05:46 PM EST Pete Freitag wrote:

Depends what you mean by a virtual environment - I am assuming you mean on a VPS type setup like Microsoft Virtual Server, or VMWare. Yes it would make sense to do that, you probably wouldn't get the best performance, but if hardware was limited it would make sense to do that.

On 11/26/2007 at 3:56:24 PM EST vanpooler wrote:

Thanks for the response. Please endulge my tweaking the question further.

When considering costs are a big factor. Could I get by cheapest using only one license of "SqlServer+5cal WorkGroup" and not using a virtual environment? Or, does the virtual environment continue to be a good idea? (Of course,I could upgrade later when more cash becomes available.)

On 11/26/2007 at 4:15:05 PM EST Pete Freitag wrote:

If cost is a big concern I would look into using SQL Server Express edition which is free. If it meets your needs that would work best. You aren't really going to save any money by using a virtual environment since you could can install SQL Server along side other applications as well.

On 03/11/2008 at 7:14:37 AM EDT Chris wrote: