Why should I upgrade from SQL2000 to SQL2005?

Question

I am looking for the only reason you are glad that you have already made the transition from SQL2000 to SQL2005.

Answer 1

• Recursion without creating temporary tables.
• Support for Native Exception (Try / Catch, not if @Error goto)

Answer 2

Because:

Microsoft would like to remind customers that support for SQL Server 2000 Service Pack 3a (SP3a) will end on July 10, 2007.

Answer 3

Native XML support is great for us here.

Answer 4

SSIS support. Removes DTS and is very handy. :)

Answer 5

• SSRS - a really huge advantage for my organization is the availability of free reporting tools that come with SQL Server 2005. Reporting Services allows me to create nice reports that have exactly the fields that our managers need in a very short time. It has a built-in tool, so It can convert to Excel, PDF or several other formats. There is a lot of value.

• SSIS The integration services in 2005 are very effective for ETL functions (export, conversion, loading). You can configure automated processes to run as scheduled.

• SSAS - Analysis services look promising. I have not done data cubes yet because I want to organize an actual data warehouse. Once you do, robust data mining algorithms are already built in.

Take a look at these three tools that are included in SQL Server 2005. If I needed to choose one of them as the only reason for switching to 2005, it would be SSRS.

At this point, I would suggest looking at SQL Server 2008.

Answer 6

Pagination without (manually) creating temporary tables is a major but significant improvement.

However, if you are going to drag some GridViews into your ASP.NET application directly from the data table, you will be paging in the application ...

Answer 7

CLR integration

Answer 8

Version Based Versioning Transaction Isolation

Answer 9

I think the biggest reason is that SQL 2000 is not supported in Vista. Because of this, I had to switch to SQL 2005.

Answer 10

I don’t know if this is the only thing, but Linq2SQL doesn’t work very well with SQL 2000. Usually it should automatically generate and populate child collections based on the outputs from your schema keys, foreign keys, RI, etc. Works great in 2005, but I was not very lucky in 2000.

Answer 11

Common table expressions have proven incredibly useful.

Answer 12

Exception handling ... how did we deal with SQL 2000 ...?

Answer 13

PIVOT . This beautiful little expression saved me more time than any other SQL Server 2005 enhancement.

Answer 14

YOU CAN'T EXPORT TABLES with a "right click". This is more of a problem than a good reason.

Answer 15

Dynamic management views to optimize and quickly determine server status.