Just to add to Bruce's very good comments:
* CTP September includes already a preview of the upgrade functionality
* While the object/metadata store for RS 2005 can be located on a SQL Server
2000 database engine, the actual database schema for the metadata store
between RS 2000 and RS 2005 is different and will get upgraded during the RS
2005 upgrade.
* I strongly recommend to always backup the encryption keys, the
ReportServer, the ReportServerTempDB, as well as all configuration files
(such as RSReportServer.config), before you attempt any upgrades. The
upgrade process will also analyze your existing RS 2000 installation - if it
finds blockers for an automatic upgrade during setup, you will need to
follow manual upgrade steps.
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
[quoted text, click to view] "Bruce L-C [MVP]" <bruce_lcNOSPAM@hotmail.com> wrote in message
news:OU657lozFHA.2064@TK2MSFTNGP09.phx.gbl...
> Just to be clear (because I am not quite sure what you mean by 2005
> databases). RS 2005 can use a SQL Server DB as its object/metadata store.
> So, you can upgrade RS 2000 only and leave the database engine as SQL
> Server 2000.
>
> And no, you cannot deploy a 2005 report to RS 2000 (Remember, you do not
> deploy to a database you deploy to RS). So, you have to upgrade RS 2000 to
> RS 2005 but don't upgrade the database engine, just RS 2000. Whether this
> is possible in the Sept CTP I don't know. I do know that when it is
> released it will support this configuration.
>
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Stephen" <switter@enpathmed.com> wrote in message
> news:1129044147.248625.54230@g44g2000cwa.googlegroups.com...
>> Thanks for the info. We are licensed with software assurance. Your
>> right, we only want to upgrade RS. So are you saying the data store
>> for both version is the same (2000/2005), or can a person install the
>> 2005 databases in a 2000 instance? Maybe I will have to play with it.
>> We have the 2005 beta installed on a test server, along side a 2000
>> instance, but I was unsucessful deploying a 2005 report to the 2000
>> database, but I could be missing something.
>>
>> Bruce L-C [MVP] wrote:
>>> Two things here. There is what is physically possible and what happens
>>> as
>>> far as licensing. RS 2005 requires a SQL Server 2005 license. Physically
>>> you
>>> can install/upgrade RS 2000 to RS 2005 and RS 2005 can use SQL Server
>>> 2000
>>> as its data store. So, you do not even need to install the 2005 database
>>> if
>>> you don't want to. I am pretty sure side by side of SQL Server 2000 and
>>> 2005
>>> is not a problem. But, if RS 2005 is what you want then I would not
>>> bother
>>> with SQL 2005, just upgrade RS only. Again, you need to be licensed for
>>> SQL
>>> Server 2005.
>>>
>>>
>>> --
>>> Bruce Loehle-Conger
>>> MVP SQL Server Reporting Services
>>>
>>> "switter" <switter@discussions.microsoft.com> wrote in message
>>> news:915D7ECA-5E98-4F8B-AF6B-53C86F58E02E@microsoft.com...
>>> > we currently have rs and sql server 2000 installed on a 2003 server.
>>> > We
>>> > have
>>> > software assurance with processor licensing. My question is can we
>>> > install
>>> > an instance of rs & sql server 2005 on this same server for rs 2005
>>> > alone?
>>> > We want to upgrade to RS 2005, but because our erp system is in 2000,
>>> > we
>>> > can't upgrade our existing sql server instance for obvious reasons.
>>> > basically we want to take advantage of the new features in rs 2005
>>> > without
>>> > having to purchase more licensing (like I said, we are fully qualified
>>> > to
>>> > install 2005). If our current erp supported 2005 we would just
>>> > upgrade
>>> > the
>>> > whole thing but that won't be the case for some time to come.
>>
>
>