Ten reasons why you should upgrade to SQL Server 2005

Most IT pros are working in SQL Server 2000 and still supporting SQL Server 7 databases (a few folks are even supporting SQL Server 6.5 databases). With the arrival of SQL Server 2005, we're often asked: "Should I upgrade?" In this article, we offer the 10 most compelling reasons why you should upgrade to SQL Server 2005.

1. Everything that works now will continue to work (sort of).
SQL Server 2005 Management Studio will let you control SQL Server 2000 and SQL Server 2005 databases. Management Studio will not work for SQL Server 6.5 and 7.0, but it's simple to port to the acceptable versions.

Due to compatibility issues, some things will not port easily to Management Studio. For example, if your SQL Server 2000 database contains diagrams, you won't be able to touch them from SQL Server 2005 without upgrading the database.

2. SQL Server 2005 comes with more components.
Earlier versions of SQL Server packaged the various components in several different ways. For instance, the all-inclusive Enterprise edition bundled everything, but you may not have been lucky enough to access that edition. The Analysis Services component was not included on SQL Server 2000 Standard — you had to buy that component separately.

Microsoft has changed its marketing strategy and bundled all the components into a single package. SQL Server 2005 does cost more than previous editions, but it is still an incredible deal. And, if you attend a SQL Server 2005 launch presentation, Microsoft will give you a free version — no strings attached.

3. Disparate user interfaces have been rolled into one UI.
In the old days of Enterprise Manager and Query Analyzer, Query Profiler, Reporting Services, and Data Transformation Services (DTS) were isolated apps whose interfaces were anything but consistent. SQL Server 2005 Management Studio gives you one clean UI that accesses all of the components, even online analytical processing (OLAP) and SQL Server Integration Services (SSIS), without regard to the server upon which the component of interest resides. This translates into more productivity and cheaper training costs. Even if you choose to keep your databases in the SQL Server 2000 format, you can still use the wonderful new interface to perform your tasks.

4. Let .Net languages do the heavy lifting.
T-SQL is still the tool for doing 90% of your work, but some tasks require special precision; in these situations, T-SQL is ungainly at best. Examples include row-by-row control, particularly when you must compare the current row to a previous row and write to multiple tables within one procedure. You can do this in T-SQL. Therefore, you might find it simpler to let .Net rowsets handle very complex logic. We aren't suggesting that you run off and rewrite all of your stored procedures in .Net; instead, think of this as an added luxury and not as a replacement of T-SQL.

5. You can take advantage of Reporting Services.
We operate on the general principle that everything the back end can do, the back end should do. For example, we think that constructing dynamic SQL Server queries in the application is generally silly. It is necessary from time to time, but a better and more secure option is to have the front-end application assemble the parameters and then call a stored procedure.

SQL Server 2005 Reporting Services extends this concept to another level. In SQL Server 2000 and earlier versions, reports were delivered by...

For more, click here...