(originally from internetnews.com)

A report from Evans Data shows that FirebirdSQL and MySQL are the most popular open source databases currently in use.

The findings are part of Evans Data’s Database Development Survey of more than 400 developers. According to the survey, 52.9 percent said they are using MySQL and 51.6 percent said they were using FirebirdSQL.

PostgreSQL came in third at 14.8 percent, and Sleepycat’s Berkely DB (4.1 percent), GNU SQL (3.3 percent) and SAP DB (1.2 percent) rounded out the list.
The Firebird name became the subject of heated dispute in the open source community in 2003 when the Mozilla project re-named its next-generation browser Phoenix to Firebird. After bowing to pressure from the community and the FirebirdSQL project, Mozilla changed the name to Firefox last year.

According to Evans Data’s research, MySQL and FirebirdSQL are each fulfilling different niches.
“Firebird has a very strong position in what we define as edge databases that could be embedded databases — databases sitting at the periphery of the enterprise,” Evans Data analyst Joe McKendrick told internetnews.com. “MySQL had a stronger showing on the enterprise level.”

The distant third place showing by PostgreSQL in the Evans Data survey is likely related to its previous lack of proper Windows support, according to McKendrick. PostgreSQL version 8.0 of its database, which now includes native Windows support.
“In our survey, 90 percent of our developers work with or deployed to Windows platforms,” McKendrick explained. “Windows dominates this space, and a database that doesn’t run on Windows or doesn’t run effectively in Windows would have a fairly limited reach.”

Among the other findings of the Evans Data study is that data restoration capabilities have climbed over the past year. In 2003, 41 percent of respondents reported they could restore mission critical data within an hour. That number jumped to 62 percent in 2004.
Security also seems to a strong point for database administrators in 2004. Eighty-nine percent of respondents reported they had no database security breaches.

Article originally from Burnam’s beat (3/16/2005)

Open Source is one of the most important and perhaps the most controversial trends within the software industry. While some see Open Source as a kind of communal catalyst for innovation and creativity others see it as a wildly destructive trend that threatens to undermine the economic viability of the entire software industry.

To date, Open Source projects have largely been focused on broad horizontal platforms within infrastructure software. These projects have been so numerous and so successful that many pundits now talk about building applications on top of the all-Open Source LAMP (Linux, Apache, MySQL, Php/Python/Perl) stack. And that stack continues to get bigger as Open Source projects start migrating to more complex infrastructure platforms, such as applications servers (J-Boss, Zope, JonAs, Enhydra). In fact, there are Open Source projects currently underway for just about every major infrastructure software technology you can think of from Content management, to BPEL, to you name it.

One of the biggest questions facing the software industry in 2005 is whether or not Open Source will “jump the species barrier” and start to become a major factor in the enterprise applications space. A quick look at Sourceforge confirms that to date most Open Source efforts in the applications space have been confined to niche applications in the academic space, but there are now numerous efforts underway, such as SugarCRM, to try and create enterprise-ready Open Source applications. Whether these applications efforts are successful or not is one of the key issues keeping software company executives up at night.

For software executives, Open Source presents three major choices: beat it, join-it, or co-opt it. The conventional wisdom suggests that the way to beat Open Source is to “out-engineer” Open Source by providing a more stable, secure and feature rich product while at the same time “out-servicing” Open Source by providing robust 24/7 support. This strategy appears to be keeping many Global 2000 customers “in the fold” for now, but even at these customers Open Source software is increasingly showing up in non-mission critical areas.

Joining Open Source is an option many companies, especially many small infrastructure software companies, increasingly appear to be taking. These companies typically develop their software in-house and then once finished (or almost finished) declare to their software to be “Open Source”. The strategy is essentially to use “free Open Source software” as a way to acquire customers that can then be charged services and maintenance fees. This strategy sounds great but has several drawbacks, chief of which is that simply declaring a software product to be Open Source does not automatically create a large community of diverse programmers who are willing to devote substantial free time to improving the product, but it definitely does make the company’s IP public domain. Thus, many of these companies face the prospect of getting little or no development leverage from Open Source in return for giving up the copyright to all of their code.

Attempting to co-opt Open Source is probably the most popular and most complicated approach to dealing with the issue. IBM is the poster child of Open Source co-opting. IBM primarily sees Open Source as a way to commodify the main revenue sources of its key competitors. IBM’s bear hug of Linux was largely part of a (arguably wildly successful) strategy to undermine the value of Solaris and Windows NT and thereby stall their push into the glass house. But IBM’s love of OpenSource only goes so far. You don’t see them pushing J-Boss at the expense of Websphere or MySQL at the expense of DB2. Indeed IBM continues to lay out big bucks for “proprietary” software, so their love of Open Source appears to only go as far as they can co-opt it. Taking IBM’s lead, most of the other major software vendors (save Microsoft) now appear to be selectively co-opting Open Source to use as a weapon against their competitors.
For software VCs, Open Source creates a number of tricky investment problems. If one continues to invest in proprietary software, you run the risk of getting “Open Sourced” if the space becomes attractive enough to create either a developer community groundswell or interest from an elephant like IBM. If one invests in Open Source, you run the risk competing with 5 other companies selling the same product and turning software margins into services margins.

However, there is some middle ground. For example, companies that offer software as a service are somewhat protected from Open Source pressures as customers are buying the whole service not just the code. Indeed companies that offer software as a service can leverage a lot of Open Source software to lower their own costs. In addition, while Open Source projects may make some headway into a few large horizontal applications, chances are that it will be very difficult for them to penetrate specialized vertical niches because there just aren’t a lot of developers out there that understand the business logic required for those niches, thus making it much harder for an Open Source project to attain critical mass.

Ultimately the biggest issue for VCs is whether or not Open Source has effectively “capped” the home-run potential of software deals by guaranteeing that any new horizontal software platform that achieves critical mass will inevitably face intense competition from a free, Open Source equivalent.

Personally, I’d like to think that the answer to that issue is “no”, but I also believe that creating a next-generation “home run” platform company is now a whole harder thanks to Open Source.

Although this is not as common as installing it on a *nx machine (since I personally use freebsd and linux, im not going to play favorites), there are still a great deal of people out there that for one reason or another, would like to php scripts on a windows 2003 box (the company I worked for would not allow us to run anything but windows machines).

Steps for installing php 4.4.1 on a windows 2003 machine

note: These instructions are for iis 6.0

Step 1: Download php 4.4.1 (get the binary package, not the installer)
Step 2: Extract the .zip file you just downloaded (I usually extract it to the c drive and rename it php, but the name can be anything).
Step 3: Launch the iis (internet information services) manager
Step 4: Click on “web service Extensions” on the left and right-click on the right and pane and go to “add a new web service extension”. There should now be a new window on the screen. for “extention name” use “.php”. Click the add button on the right, and point it to c:\(the php directory from step 2)\sapi\php4isapi.dll. After this is done, check the box that says “set extension status to allowed” and click ok.
Step 5: