Reporting Services 2000 with SQL Server 2005 data sources

All,

I apologize for not doing the legwork to see if i can answer my own question, but I am close to a loosely planned SQL 2005 migration and don't have time and resources to test my own theories.

Is there a way for a Reporting Services 2000 server to connect to SQL server 2005 databases? I've tried creating a new data source and changing a report to this data source, but it seems like the report is still using the old data source. I'm guessing i might need to register new data providers on the 2000 RS server and then change the existsing data sources.

Ideas?

Thx in advance,

-Peter

Yes, a report installed on Reporting Services 2000 (SRS) can source data for a report from SQL 2005 by setting the data source with the correct connection string. There shouldn't be a problem.

Larry

|||

The correct connection string seems to be "Data Source=<SQLServerName>;Initial Catalog=<DBNAme>" using the "Microsoft SQL Server" data source type. Fortunately, this was the same as our SQL 2000 data sources, so we had to change nothing. The 2000 BOL docs just aren't very clear on the details of each data source type.

Also, the gigantic document, SQL2005UpgradeTechRef.doc, doesn't really talk much about the dependencies between upgrading the RDBMS and the RS.

Thanks for the reply,

-Peter

sql

Reporting Services

Can anyone tell me if Reporting services has it's own service packs that are
distinct from SQL server?Yes, there is both a service pack 1 and a service pack 2 released.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"beeyule" <beeyule@.discussions.microsoft.com> wrote in message
news:27A8A0DB-9346-44ED-90B3-E5D6164F9946@.microsoft.com...
> Can anyone tell me if Reporting services has it's own service packs that
> are
> distinct from SQL server?
>

reporting licensing

We recently purchased Stockamp's Clinic Ontrac system. The system has a built in crystal reports viewer module with capability to add our own reports... The backend of the product is SQL Server. To create a report you have to potentially create a stored procedure - if parameter is needed - and a crystal report. Stockamp is requesting that we have written approval of these reports as well as any ad-hoc reports and queries that we run before we run them in the production environment.

I'm used to large vendors (those that understand a database is only as good as the data you get out of it) and I've never seen a license agreement like this before. Is this common?What they are trying to do is to ensure that by creating a report you're not going to impact the production environment in such a way that they may be blamed for poor performance while your report is being generated. Also, since they introduced a "report writer," this means that there are not many "canned" reports in the system that they sold you, and they are trying to piggy-bag on your reports and incorporate them in the next release as "canned" reports.|||If possible, you should consider replicating your data on a dedicated report server. This will avoid potential performance issues.|||Unfortunately the data changes constantly, and I suspect if they won't let me add reports, they won't let me replicate. It took me over 2 months to convince them we needed a seperate test server as making a modification to their system (using their own forms and an approved process) required a 4 hour import that completely paralized the system.
The database tables have grown from 2000 rows 9 months ago to over 21 million, so reporting out of the system will soon become too cpu intensive anyway.
I'd love to work with the vendor and introduce them to datawarehouseing, but they're product is so fragile and Stockamp & Associates employees are so unwilling to listen, that I given up on a friendly working relationship.
So the moral is to avoid software with a canned report viewer, regardless of its backend system.