Eric Brown Discusses SQL Server—Past, Present, and Yukon

It's been a busy year for SQL Server. Not only did it celebrate its 10th anniversary last winter, Microsoft is preparing a new version, code-named "Yukon," that's currently undergoing a round of early beta testing. MSDN Magazine recently talked to Eric Brown, a product manager for SQL Server, about the product's past and future.

MSDN  This year was the 10th anniversary of SQL Server. How did you celebrate it?

Brown  We marked the 10th anniversary with celebrations at the Professional Association of SQL Server (PASS) in November last year, and at Tech•Ed in Dallas, with parties and games. You can learn about the 10 years of innovation by visiting SQL Server 10-Year Anniversary.

MSDN  Explain the significance of writing stored procedures in any language that compiles to Microsoft Intermediate Language (IL) and the significance of native XML support.

Brown  SQL Server "Yukon" is empowering a new era of database applications. We see more and more customers asking for greater interoperability, greater flexibility and choice in programming models, and the ability to use developer skills in more areas. The integration of SQL Server "Yukon" with the .NET Framework represents the delivery of a more symmetrical programming model between the middle and database tiers. Writing database logic in either Transact SQL (T-SQL) or any .NET-compliant language means greater productivity for developers. Not only will they be able to take advantage of the Microsoft .NET Framework, they will also be able to create data types, functions, and aggregates—thus extending the data tier beyond the types and functions that are included in SQL Server.

XML integration is as important as the .NET Framework integration. SQL Server "Yukon" will ship with a full-fledged XML data type that will support XSD for schema validation. Moreover, support for existing and emerging open standards such as HTTP, XML, SOAP, and XQuery. This will allow SQL Server "Yukon" to facilitate communication across extended enterprise systems.

MSDN  Are there any major trends you see emerging?

Brown  More and more, we see customers using XML. I've talked to customers who are using Web Services to overcome application interoperability hurdles. I've seen some of our large customers using the XML features currently available in SQL Server 2000—the FOR XML clause and the Web Service Toolkit, for example—to extend their databases into the Web Services frontiers. Another big trend is in the area of reporting applications. The demand for the SQL Server 2000 Reporting Services Beta has been overwhelming. Customers are looking to improve and extend their current applications, and Reporting Services provides a natural extension.

MSDN  When can we expect to see Yukon?

Brown  SQL Server "Yukon" has just entered Beta 1. We will do more betas as we get feedback from customers. Our current goal is to have a public beta in the first half of 2004.

MSDN  What kind of community efforts are you planning to set up around SQL Server?

Brown  Community is important to us. We want to make sure that we're providing those who run and develop against SQL Server easy access to the people and information that will make their jobs simpler. We're working with PASS to hold SQL Server University classes on different SQL Server topics. Plus, don't be surprised if you see people from the SQL Server development team answering your questions in the newsgroups. We've set up a community lounge so that our customers get answers directly from the designers, program managers, developers, and testers who build SQL Server at Microsoft. Finally, we're working closely with our MVPs and the MSDN Regional Directors to make sure they're ready to answer all of the community's questions around both SQL Server 2000 and SQL Server "Yukon".

MSDN  A lot of readers got hit with the Slammer virus last year. What advice can you give to help them keep servers secure?

Brown  Customers should make sure that they're aware of the tools available for protecting themselves from Slammer and also from future attacks. For Slammer, we rereleased SQL Server so that by default you will not get infected by the worm. Also, we have a number of tools available for download from the Web site that will find and remove the Slammer worm from existing SQL Server installations. Finally, customers should use tools like Windows Update, the SUS Server, and the Microsoft Baseline Security Analyzer (MBSA). MBSA is a great tool to ensure that your SQL Server systems have the right security practices, and it works with Windows, IIS, and Exchange Server.