Reporting Services 2000 Vs 2005

We're planning to use SQL 2005 Reporting Services, but first:

1. Is it as buggy as 2000?
2. Formular field and DTS packages: VBScript or C#?
3. Can you deploy reports built for SQL 2000 on SQL 2005?

Thanks in advance.

Norman Fung

Thy02k,

sorry I am not answering your question.
I am using 2000 at the moment, and I am having all sorts of problems.
You mentioned in your post that it is buggy, I am starting to loose confidence.

I have noticed sometimes that the sql I run within RS fails to run even though it runs ok under Query Analyser and Enterprise Manager.

Alternatively, I have found the SQL running ok but the preview fails with meaningless error messages (I try to guess the fixes, but the messages seem just too vague).

At first I thought the report parameter facility was cool. It made sense and it worked ok. Until I started using parameters to gather year and month information. (I am building the start and end dates based on month range selected by the user).
Using the SQL Convert and Cast statements I have got the SQL extracting data, but the preview fails, so I have yet to successed with my paramenters.

While working with the VS.net editor, it freezes.
The windows task manager shows the application as "running". I have to end the task and restart the project editor.

Finally, I find the export to excel facility disappointing.
Most other reporting tools I have worked with provide you with instant excel exporting that is simple and spot on.
You uaually get detail data as the excel rows. Some applications give you the option to pass on headings and footer, so your spreadsheet replicates the report format.
In RS I have struggled to control these. The basic export gives me meaningless columns, totally different to the report structure? It's like a dogs breakfast.

Anyway, I hope that 2005 is more stable if you are using it.