SQL Server 2008 licensing.... good grief

[freshfruitinc]

I've just been on the phone to Microsoft and clarified their licensing costs for SQL Server 2008 standard... here it is for anyone else who wants to know (from the horses mouth)...

Per Processor model: Here the server is the licensed entity and you pay for each physical CPU in the machines (cores don't count towards an extra CPU). The cost is $7171 per CPU serving up SQL. This is more cost effective when your user is Joe Public (and you can't count them) or you have more than 8 users.

Per user/CAL: Here each user who benefits from your SQL server is licensed. Now this is where it gets grey. M$ say that every user that benefits from your SQL instance includes anyone receiving / sending data to / from that server via a proxy... e.g. you have a windows form or web app that connects to SQL and updates / serves up data via a web service or web server.... anyone who interacts with that win forms or web app is considered a SQL client and must pay.... $898 to use the service. So it's $898 per user of the service.

That SUCKS but now it makes more sense to me at least. I can't just develop a client/server app and get away with 1 CAL simply because the server is the only machine interacting directly with the SQL instance... every user of that app must pay too.

 

[Necuno]

wow that's a lot of whining :erm:

 

[Grim147]

go open source

 

[tortured]

wow that's a lot of whining :erm:

I don't really see that as whining tbh...good info for people who did not know.

Now if we go look in the ADSL/ISP sections, there we see whining.

 

[Viper25]

One solution -> MySQL

 

[TheGuy]

wow that's a lot of whining :erm:

Wow that's a lot of trolling :erm:

@OP thanks for the info.

 

[TKD01]

- SQL 2008 is geared towards your big corporates who has the bucks to pay for it...
- MS SQL is VERY reasonable priced compared to other products like Oracle for example, especially considering that SQL comes with Integration Services, Reporting Services, Analysis Services et al... With Oracle you have to buy these seperately as 3rd party products as well

go open source

One solution -> MySQL

Absolutely - if you're working with small apps. SQL's true power shows when you're working with gigabytes of data - which you will usually only get in big corporate environments anyway... No use running a one-man point of sale with 10000 transactions per day on MS SQL

 

[bk.ru]

wow that's a lot of whining :erm:

wow you really are a world class prick. Most of us found his post informative and then you come along trolling. how do you like it?

 

[Necuno]

wow you really are a world class prick. Most of us found his post informative and then you come along trolling. how do you like it?

irrelevant to my position as we have special ms license agreement with our multi tiered international company. however i suppose it might be useful for the average joe, but still it seemed to me imho that the op was just whining away at microsoft, especially with the use of m$ instead of properly writing it out - you think ?

 

[Viper25]

Absolutely - if you're working with small apps. SQL's true power shows when you're working with gigabytes of data - which you will usually only get in big corporate environments anyway... No use running a one-man point of sale with 10000 transactions per day on MS SQL

If facebook can utilize MYSQL to process terabytes of data, I'm sure implementing a solution for a big corporate wouldnt be too difficult.

http://www.mysql.com/customers/view/?id=757

 

[TKD01]

If facebook can utilize MYSQL to process terabytes of data, I'm sure implementing a solution for a big corporate wouldnt be too difficult.

http://www.mysql.com/customers/view/?id=757

Depends on the requirements. Usually the database (SQL) servers form part of a much bigger infrastructure setup, with security and accessibility considerations, usually supporting various applications like sharepoint, data mining apps, reporting etc. Though MySQL might compare on the data volume, it will not compare on performance, as well as provide flexibility usually required within the bigger infrastructure scheme of things

 

[davemc]

You're absolutely insane to go the CPU model.

How many users are actually connecting to the SQL server instance directly?
I'd bet the answer is: About 5 database administrators.

So, throw in another CAL for each software program that connects to the database, you'll probably be fine with a 10 CAL agreement.
It's the wording around what a USER is that's key here. The public accessing a website that accesses the database are not SQL server users, the website is.

Well, that's what it was last time I read the agreement.

 

[tortured]

irrelevant to my position as we have special ms license agreement with our multi tiered international company. however i suppose it might be useful for the average joe, but still it seemed to me imho that the op was just whining away at microsoft, especially with the use of m$ instead of properly writing it out - you think ?

 

[spiderz]

Ouch...and don't forget, you need a windows server license too !