advertisement
Login | Register   
  Include Code  Search Tips
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   TIP BANK
Browse DevX
Did you read the first article in this series? Do you have any comments on the changes described in this article or do you know of any additional changes that you think others should know? Let us know in the DevX Database Developer forum.
Partners & Affiliates
advertisement
advertisement
advertisement
advertisement
 

Analysis Services Comparison: SQL 2000 vs. SQL 2005

Major changes to Business Intelligence (BI) features in SQL Server 2005 promise (or threaten) to alter the way you develop BI applications. Read this comparison article to find out what's changed and start planning today. 


advertisement
any SQL Server developers eagerly anticipate the long-awaited release of SQL Server 2005, formerly code-named "Yukon." Major goals for Business Intelligence (BI) in the 2005 release are better integration of the somewhat loosely-coupled BI components of SQL Server 2000, provide enterprise reporting capability in the form of Reporting Services, and enable faster and easier development of "pervasive" BI, which can reach people at every level of the organization. To achieve these goals, each existing component of the SQL Server suite has been changed or replaced in the 2005 release. Reporting Services, originally slated to debut as a new component of SQL Server 2005, has recently been released independently—but remains an integral component of the SQL Server 2005 vision.


SQL Server BI developers are well-advised to learn as much as possible about these changes and to start planning how to capitalize on them. This article focuses on some of the most basic differences between the 2000 and Beta 1 2005 versions of Analysis Services, and addresses these differences in three overlapping areas:

It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com.
Already a member?



advertisement