RS 2005 run on SQL Server 2000 Database?

Our product currently works with Cystal Reports but we decided to enhance it so it works with another reporting platform (MS Reporting Services).   We are in the beginning stages of developement and trying to decide which version of RS (2000 or 2005 ) to build the reports and integrate our web UI with.  Most of our clients are using SQL Server 2000 for their database platform and we don't anticpate them upgrading to 2005 in the near future.   
If we built everything using RS 2005 could our clients deploy RS 2005 Report Server on a SQL 2000 Database   
Is the licenses model the same when the Reporting Services and Database versions match vs non-match   
Is the Reporting Service version tied to the Database version  
I'm guessing a report created in 2005 can run on a RS 2000 Report Server once I remove the 2005 features from the RDL and change the namespace.  Is that correct

Thanks,
Robert.


Answer this question

RS 2005 run on SQL Server 2000 Database?

  • kBegemot

    Hi Robert,

    Thanks for the reply, that is my problem... I was installing SSRS 2005 Enterprise on SQL 2000 Developer.

    Thanks again for the help.



  • DGVines

    RS 2005 (report designer and report server) will automatically upgrade RS 2000 RDL files (namespace: 2003/10) to the RS 2005 namespace (2005/01).

    Generally, reports designed for RS 2000 will work the same way when run on RS 2005.

    -- Robert

  • Jeff Cao

    hi all,

    i've installed RS 2005 developer edition on a pc which i've installed SQL Server 2000 developer edition as well.

    i've configured everything using RS Configuration and everything has green tick, except Encryption keys, Email settings and Execution Account which are not compulsory items.

    But when i browse Report Manager using IE , it just wouldn't show - The page could not be displayed.

    No error message. Anything else i should be checking Sad

    Please help.. Thanks!


  • aLoNsO___

    If you ensure that your edition is the same you will not have any problems, i.e: if you are using SSRS Developer Edition, you need to use SQL Developer Edition. Dissimilar versions do not cause problems

  • Jeremy Jarrell

    I am trying to configure MSRS 2005 on a SQL 2000 database, but I get the error message that it is not supported for Enterprise Edition, is this true or am I getting something else wrong

  • teleweb

    Although Reporting Services 2005 is a component of SQL Server 2005, you do not need to use a SQL 2005 relational database for either the report server metadata catalog or the source of data in the reports. From a licensing perspective, if you upgrade a 2000 RS install to a 2005 SQL install, you would need to migrate the relational database if it was on the same machine.

    And, yes, you could move a 2005 report back to 2000. It's not trivial, but possible.



  • Konstie

    If you install the Enterprise Edition of RS 2005, the database backend (SQL 2000 or SQL 2005) will also need to be an Enterprise Edition.

    -- Robert



  • Grant Swan

    Thank you. 
  • AjayG

    I'm new to much of this having recently moved from MySQL to SQL in order to benefit from Reporting Services. I was also trying to establish whether the SSRS 2005 metadata could be stored on SQL Server 2000 and these posts have answered this. All I need to know now is whether the SQL 2000 installation can be on a different box.

    To clarify, I'm in a situation where I want to use existing corporate SQL 2000 servers for the databases and buy a new server to run SSRS and IIS. (I am aware that we will need to purchase the full SQL 2005 license). Will this setup work

    Many thanks.


  • Rajagopal

    Yes, the metadata database can also be stored on a remote SQL 2000 server (assuming your are using RS 2005 Standard, Enterprise, or Developer editions).

    -- Robert



  • bjun

    That sounds like your www service.

    First thing to try is browse the page through IIS (right click reports and select browse).

    Does that work If so then you're entering the wrong URL.

    If not then check your services.

    Is "World Wide Web" service running If not start it.

    Now try to browse...

    If it just hangs and does nothing - check your reporting services service is started.

    If it isn't - start it...

    Hope that helps


  • bbostic

    Using a SQL Server 2005 database engine to store the RS metadata database will give you some performance improvements over a SQL Server 2000 database engine. Other than that, you get the same RS 2005 functionality - regardless of the SQL Server version of the database engine that stores the metadata database.

    -- Robert

  • MARIU5

    I know I might be missing something obvious here but it is critical that I understand the relationship between RS 2005 and SQL server as we trying to make a decision between RS and Crystal and our installed base is SQL 2000. Forcing the move to SQL 2005 will be an impediment if this is a requirement for RS.  If 2005 is not a requirement then are there advantages from a reporting point of view in using SQL 2005.

  • skiluver99

    Based off of the information you supplied it seems like the best approach for us is to develop using Reporting Services 2000, this way when we roll it out to our customer base we are not forcing them to upgrade to SQL 2005 if they wish to switch out the reporting platform from Crystal Reports to Reporting Services.  But here's by question.  What is involved in getting a RS 2000 report to run using RS 2005.  Is it changing only the namespace or its it more   The reason I'm asking is because when we sell our product to new customers they will likely be purchasing SQL 2005 if they don't have an existing database platform.


  • RS 2005 run on SQL Server 2000 Database?