MS SQL Server man lets betas have it
CTP or bust
With the first service pack for SQL 2005 Server due in the next two weeks, Microsoft has been laying down the law on future development plans for the database.
In short, that means no return to beta editions for new versions of its database and regular product updates every two- to two-and-a-half years, according to the vice president of Microsoft's server applications group. Paul Flessner was speaking after Microsoft last week outlined four key themes for investment in the SQL Server roadmap, that included a re-branded edition of SQL Server Mobile Edition called SQL Server Everywhere Edition due later this year.
According to Flessner, investments in SQL Server will now focus on availability and automation, going beyond storage of purely relational data, synchronization, and end-to-end insight. As such, SQL Server Everywhere Edition is promised as a small footprint, client - not merely mobile device - database that can store data locally and replicate with server-side editions of SQL Server when an online connection is resumed. The first community technology preview (CTP) is due this summer.
In many ways, Microsoft is late to the game with SQL Server Everywhere Edition. IBM helped feed today's growing demand for light-weight, client-side databases when it open sourced its Cloudscape database to the Apache community as Project Derby in 2004. Oracle, meanwhile, this year bought Sleepycat to add a popular, small footprint, embedded alternative to its existing enterprise database line.
IBM has also been setting the trend in others areas. The up-coming edition of DB2 codenamed Viper is slated to become the industry's first database with native support for XML. Viper will allow users to store, search and retrieve unstructured data - in addition to structured data - for use in business analytics, without breaking the XML data down into rows or columns, a move that slows performance and causes a loss in the fidelity of data. IBM believes 35 per cent of business data is currently stored in an unstructured XML format.
IBM has been releasing full versions of DB2 roughly every two years. Flessner, though, last week dismissed IBM's track record saying the company had issued what he considered to be "feature updates."
Flessner appears to be placing his faith in plans to deliver updates of SQL Server every two- to two-and-a-half years. A key part of that is to streamline delivery of SQL Server using small, feature-specific CTPs instead of bigger code drops epitomized by the beta process. SQL Server was one of the first Microsoft products to adopt the CTP approach, an approach now spreading across other Microsoft groups, even though the CTP approach didn't avert delays to SQL Server 2005. The database finally shipped last November, more than four years after its predecessor.
"I'm convinced we can do it," Flessner said of the new delivery cycle. "The key is keeping the main product build stable. The CTP is the key. The beta process was very large, but the CTP is much smaller. As long as I'm in charge of SQL Server, we will never go back to betas."®
Sponsored: DevOps and continuous delivery