News

SQL Server 2008 Is Here

Microsoft releases new database server, adding support for policy management, encryption and new data types.

It's official: Microsoft has released SQL Server 2008, the culmination of a series of new tools and server product launches by the company this year, including Visual Studio and Windows Server.

Microsoft also released the first Service Pack (SP) of Visual Studio and of .NET Framework 3.5 (see the Aug. 15, 2008, news story, "Visual Studio 2008 Facelift Is Ready"). SP1 includes, among other things, the ADO.NET Entity Framework (EF), Redmond's latest data-access technology for building data-driven applications.

While EF is designed for multiple database platforms, Microsoft says developers will get the most mileage out if its features with SQL Server 2008. Microsoft officials held a conference call last month to hail the new database release.

Key Features
Among the key new features of SQL Server 2008 touted by Microsoft officials: Policy management, improved use of data encryption, the ability to store and query spatial data, a new report builder and improved support for analysis, reporting and administration. The update also boasts new data-compression capability, which the company said makes better use of storage and provides faster queries.

For developers, key features of SQL Server 2008 center around T-SQL and its support for Table Valued Parameters and the new MERGE syntax; support for new data types including date and time, hierarchyID and filestream (storage method); and encryption, in addition to support for the ADO.NET EF and LINQ.

Redmond officials belabored the point that organizations can upgrade from SQL Server 2005 without having to modify their software. "Customers can adopt these enhancements and features without making changes to their applications," said Ted Kummert, corporate vice president of Microsoft's Data and Storage Platform division.

But that raises another question: Will Microsoft's cloud-based incarnation of its forthcoming database platform, dubbed SQL Server Data Services, or SSDS, be just as seamless to developers or will they require new interfaces or development methodologies?

"As we move things forward I think you'll see things change," Kummert said. "Our focus today is on SQL server 2008, I think in the next year, you'll see a lot of clarity emerge around SSDS, and how SSDS relates to our overall data platform. But the overall commitment is clear, that we're spanning this data platform vision to the cloud and we will provide a consistent application model across all tiers -- that's the edge, the data center and the cloud."

Click here to read about "SQL Server 2008's Developer Appeal."

About the Author

Jeffrey Schwartz is editor of Redmond magazine and also covers cloud computing for Virtualization Review's Cloud Report. In addition, he writes the Channeling the Cloud column for Redmond Channel Partner. Follow him on Twitter @JeffreySchwartz.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube