January 19, 2007 at 18:11Microsoft must open SQL Server
Former Microsoft employee Stephen Whalley (Stephen Walli) left the company about two years ago to found his own start-up (he has not said which one). At Microsoft, he worked as a Product Unit Manager at Interix, and before that he founded Softway Systems, a startup that developed an Interix environment for porting UNIX programs to Windows NT. Microsoft bought Softway Systems in 1999, and Stephen Wally worked there for about five years, and then moved to the position of vice president of open source strategy development at Optaros.
On his blog, Stephen Wally posted two interesting posts with practical tips on what Microsoft should do in the open source field. In his opinion, those small experiments that Microsoft carried out earlier are clearly not enough. More bold, significant steps must be taken.
In his first post, Stephen Wally advises Microsoft to start publishing SQL Server source codes, and change the business model for this product to a paid subscription to SQL Server Network. In other words, it is recommended that you adopt the model that Red Hat Network successfully applies to MySQL Network. The fact is that now SQL Server buyers do not buy a program at all, but a solutionbased on SQL Server, and support is an integral part of it. Based on this, it can be assumed that a subscription to the SQL Server Network will be in demand. Source code is best published under the GPL2 license, rather than GPL3.
Over the next two years, someone will definitely try to make a “cross between” MySQL and SQL Server . After all, an open DBMS has a modular structure, so it encourages such experiments. Moreover, a situation is often encountered when MySQL databases work under Windows .
In a second post, Stephen Wally gives similar advice on SharePoint Server. It can also be published under the GPL2 license, open source, and profit from a paid subscription to the SharePoint Server Network.
Wally also recommends Microsoft establish a relationship with the Eclipse Foundation and the Mono community and release Visual Studio and Rotor 2.0 under the Eclipse Public License and under the (Rotor) ECMA Base Class under MIT X11 so that it is compatible with the rest of the Mono Base Class library.
On his blog, Stephen Wally posted two interesting posts with practical tips on what Microsoft should do in the open source field. In his opinion, those small experiments that Microsoft carried out earlier are clearly not enough. More bold, significant steps must be taken.
In his first post, Stephen Wally advises Microsoft to start publishing SQL Server source codes, and change the business model for this product to a paid subscription to SQL Server Network. In other words, it is recommended that you adopt the model that Red Hat Network successfully applies to MySQL Network. The fact is that now SQL Server buyers do not buy a program at all, but a solutionbased on SQL Server, and support is an integral part of it. Based on this, it can be assumed that a subscription to the SQL Server Network will be in demand. Source code is best published under the GPL2 license, rather than GPL3.
Over the next two years, someone will definitely try to make a “cross between” MySQL and SQL Server . After all, an open DBMS has a modular structure, so it encourages such experiments. Moreover, a situation is often encountered when MySQL databases work under Windows .
In a second post, Stephen Wally gives similar advice on SharePoint Server. It can also be published under the GPL2 license, open source, and profit from a paid subscription to the SharePoint Server Network.
Wally also recommends Microsoft establish a relationship with the Eclipse Foundation and the Mono community and release Visual Studio and Rotor 2.0 under the Eclipse Public License and under the (Rotor) ECMA Base Class under MIT X11 so that it is compatible with the rest of the Mono Base Class library.