Microsoft Plays Up Open Source
An anonymous reader writes "Recently Microsoft's open source software lab posted PostgreSQL on Windows: A Primer. Postgres is one of the longest running open source databases — it has been around for nearly 11 years. The powerful object-relational database is a direct competitor to other OSS databases, as well as Microsoft's SQL Server 2005. So why is Microsoft promoting it? I get Redmond's interest in boosting anything that runs on Windows as a platform. Is this simply a case of left-hand, right-hand, or is something deeper going on?"
It is widely reported that Microsoft makes its money on Windows and Office. The other products earn little or even lose money. If this is true, it may make sense for Microsoft to attract people to Windows or keep them using Windows, by supporting PostgresSQL, even if it reduces their sales of their own database.
Obviously, MS is interested in weakening the position of any competitor. In this case, Oracle is a bigger player in the databases market than MS ever dreamed to be. Therefore, helping PostgreSQL damages the competition more than it does damage MS itself, which is a win for them, in terms of market share and potential risks due to loss of control over that market. Kind of the same reason why IBM supports PostgreSQL and other OSS in detriment of its own products.
To do list for Windows
Right--This is not news. Nothing is going on here. They are not promoting PostgreSQL at all. There is no real promotion period. I'm not sure how one would come to that conclusion (other than conspiracy fears). The website is simply a set of installation guidelines. A guide to help keep people happy with Windows OS and not leave.
The Custom Mary
"Cygwin is required"? Apparently you haven't actually looked at Postgres in a few years. There's been a native port since PG 8.0.
MSSQL is only free if your database is smaller then four gigs. On the other hand DB/2 is free no matter how much data you have.
evil is as evil does
You're right. You beat me to the comment. Postgres is not a threat in the sense that MySQL is. Also MySQL takes money away from MS and puts it in their own bank account, whereas Postgres does not build up a cash-hoard that can be used against MS later. Postgres is really free, as opposed to GPL, which signifies ownership by "the community". A Few years ago, MS said very publically what their list of okay licences was. That list included BSD, but did not include GPL or the Artistic licence.
My only wish is that they'd produce a PostgreSQL Engine version - basically PostgreSQL without the help or extraneous fluff which automatically installs without icons or anything. The DB is far, far smaller that MSDE (cut down MS SQL Server 2000) or MS SQL Server Express 2005, has most of the same features and no restrictions on use or database capacity. I work on a project that uses MSDE and the thing is a bitch to configure and make work. If I didn't have 1000+ SQL statements and 1 million lines of C++ to port, I would switch to PostgreSQL in an instant.
Still doesn't make much sense that MS should promote it though.
"Again (and again, and again ..) the antitrust case against MS was a civil one. MS hasn't been convicted of anything and isn't a criminal."
s c_sec_15_00000002----000-.html
Riiiiight.
http://www.law.cornell.edu/uscode/html/uscode15/u
Seeya.
--
BMO
Seriously, people who can get by with Postgres wouldn't buy SQL server anyway - it's not even in the same league.
Most people who use databases don't make much use of the advanced features. This is why MySQL is even in the market. I like MS SQL server a lot - it's good DB server, but most of the stuff done on it could just as easily be done on PostgreSQL. Good old select, insert, update, delete covers a lot of ground. The pressure with commercial software is to add new features in new versions, regardless of if they are needed or not.
My Karma: ran over your Dogma
StrawberryFrog
I disagree specifically with "people who can get by with Postgres wouldn't buy SQL server anyway" - I think the problem is that people _do_ use SQL server when they can get by with Postgres.
On a different note, I've never liked the idea of having a heavy database - i.e. one with code procedures etc. It seems to make more sense to keep the database as just a database and implement your model logic in the model classes of what ever access it. That way you can change the database fairly easily and aren't tied completely to one particular database system.