THIS ISSUE SPONSORED BY
What's New in SQL Server 2005?
April 1, 2004—In this issue:
1. SQL Server Perspectives
- SQL Server 2005: Late but Loaded
2. News and Views
- Have Lunch with SQL Server Magazine
- Microsoft Fixes Access-Violation Exception
- Hotfixes Available for T-SQL Errors
- Results of Previous Instant Poll: Active Directory
- New Instant Poll: SQL Server Experience
- SQL Server Experts, Tips, & Content
- SQL Server Magazine Connections: Win a Harley
- What's New in SQL Server Magazine: The Java Connection
- Hot Thread: Logon Failures in Reporting Services
- Tip: Installing SQL Server 2000 on Windows Server 2003
5. Events Central
- Meta-Data/DAMA Conference, Los Angeles, May 2-6
- SQL Web Seminar—Writing and Debugging Great Stored Procedures
6. New and Improved
- Quickly Create Reports in Multiple Formats
- Create a Web Interface for Your SQL Server Database
Sponsor: SQL Web Seminar—SQL Server Backup and Recovery
These days, data availability is crucial for business service. It is important to have the processes and technology in place to reduce the risk of data outages and to recover quickly in the event of a failure. Sign up today for a free, one-hour Web seminar on April 29, sponsored by BMC Software. You will learn about the relevant and executable database Backup and Recovery best practices that are used to minimize the impact of database outages and protect business services that are dependent on data. Register now and get a free SQL-BackTrack License. Click here:
1. SQL Server Perspectives
(contributed by Brian Moran, news editor)
Two weeks ago, I wrote about the delay of SQL Server 2005, formerly code-named Yukon (see "Yukon Delays"). Microsoft has pushed back commercial availability of SQL Server 2005 to the first half of 2005, presumably closer to June than January. In my earlier article, I asked you to share what effect SQL Server 2005's delay might have on you and your organization. This week, I summarize the responses many of you sent me and share some of my thoughts about the delay.
Most readers who sent their responses said the delay won't be a major problem. Many of you prefer waiting to getting a release plagued with significant bugs. Readers noted that SQL Server 2000 has made great strides in gaining enterprise acceptance. However, if customers had to wait to deploy SQL Server 2005 until Service Pack 1 (SP1) fixed major problems in the release, the effect on the perception of SQL Server as a quality product would be disastrous. "The delay is a confidence booster for us," one reader noted. "We interpret the delay to mean that Microsoft is determined to produce a quality product."
Microsoft does want to produce a quality database platform. Many customers don't know that Microsoft rolls out one of the SQL Server final betas to its internal production systems. In addition, several customers will roll out the beta in production as part of the technical adopter program (TAP) before SQL Server 2005 is released to the public. In other words, Microsoft and several large customers will be running their businesses on SQL Server 2005 before the commercial release.
On one hand, readers want a quality product. On the other hand, readers agree that the reasons behind the delay stem more from Microsoft's ambition to add certain new functions than from quality issues. Many readers believe Microsoft is too concerned with developer-oriented features, such as Common Language Runtime (CLR) integration, rather than focusing on core data-management enhancements. From the responses I received, most readers agree that a release between SQL Server 2000 and SQL Server 2005 that didn't contain the CLR but that featured enterprise data-management and T-SQL enhancements would have been a better strategy. One reader put it this way: "Microsoft continues to try and build an enterprise database server product and, at the same time, entertain the development community with 'shiny baubles' that make it nearly impossible for a DBA to keep a server up and running with four nines and three quarters of a million transactions per hour."
Although that statement represents a typical DBA perspective, the developer world might feel differently. A developer might be willing to wait for the tighter integration with .NET. In my opinion, Microsoft is following a wise path by making aggressive moves to increase developer productivity within the database space. You can't have enterprise-class applications without highly reliable and scalable databases. At the same time, the database exists to serve applications (although DBAs sometimes forget that). Is the CLR good for SQL Server? Yes. Was focusing on developer needs in addition to DBA and core engine needs the right thing for Microsoft to do? Yes. Was the developer focus around .NET worth adding 1-3 years to SQL Server 2005's development cycle? No. But hindsight is 20/20.
I talked with Tom Rizzo, Microsoft director of product management for SQL Server, about the SQL Server 2005 delay. Tom admitted that there was a lot more work involved in building the feature set for SQL Server 2005 than originally planned. In addition, the development team took a significant hiatus from SQL Server 2005 to go on a search-and-destroy mission for security vulnerabilities in SQL Server 2000. Tom agreed that a release between SQL Server 2005 and SQL Server 2000 might have been in Microsoft's--and its customers'-best interest. However, he was adamant that SQL Server 2005's rich feature set, including the developer enhancements, is the right long-term approach for the database world. "You don't make great strides in computing by taking tiny steps," Tom said. And I agree.
Perhaps Microsoft should have anticipated a longer development time for SQL Server 2005 considering the number of features being introduced. But making a big leap in the database space is a good long-term strategy for Microsoft and its customers. As long as Microsoft ensures that the product will be reliable at ship time, I don't have a problem with the delay--and most of you agree.
Sponsor: What's New in SQL Server 2005?
SQL Server Magazine offers a library of helpful SQL Server expertise, article archives, endless code listings, valuable tips and an easy-to-use Web site that takes the word "timesaving" to an entirely different level. Our May 2004 issue is dedicated solely to SQL Server 2005, offering the inside scoop on what's new. Serving as just one example, each issue is packed with useful information that can be incorporated into your everyday work life. Subscribe today and experience the benefits of having a go-to SQL Server resource. Click here:
2. News and Views
Are you attending SQL Server Magazine Connections in Orlando, Florida, April 18-21? If so, the editors of SQL Server Magazine would like to treat you to lunch and pick your brain. We are organizing a reader lunch to learn more about your responsibilities, challenges, resource needs, and how you use SQL Server Magazine, SQL Server Magazine UPDATE, and our Web site to help you do your jobs better and faster. The lunch will be Tuesday, April 20, at 11 a.m. Space is limited, so if you'd like to share your needs and help shape the direction of future content, please send an email today with your name, company name, email address, and daytime phone number to [email protected] We look forward to seeing you in Orlando!
When you configure an instance of SQL Server 2000 to use more than 16 processors on a multiprocessor computer and SQL Server runs many parallel query processing operations, an access-violation exception might occur. To see the SQL Server error log file that contains stack information similar to what you might notice when the access-violation exception occurs, read the Microsoft article "FIX: An access violation exception may occur when SQL Server runs many parallel query processing operations on a multiprocessor computer" at
Microsoft released fixes for T-SQL errors associated with SELECT and DBCC CHECKCONSTRAINTS statements. When you run a T-SQL SELECT statement on a view that has many subqueries, you might receive an error message like "Server: Msg 8624, Level 16, State 21, Line 1 Internal SQL Server error." If you've received this error message, read the Microsoft article "FIX: You may receive an 'Internal SQL Server error' error message when you run a Transact-SQL SELECT statement on a view that has many subqueries in SQL Server 2000" at
When you log in to a SQL Server database by using the dbo user, then run the DBCC CHECKCONSTRAINTS T-SQL statement on a table owned by a user other than the dbo user, you might receive the following error message: "Server: Msg 208, Level 16, State 1, Line 1 Invalid object name '