Reporting Services 2003 and 2005 on same server?

Can I install Reporting Serer 2005 and 2003 on the same server, each 1
accessing a seperate SQL2000 database?
Are there any white papers on this regard?
ThanksCan you clarify the versions;
I assume you mean RS2000 (there isn't a 2003).
Also what do you mean by 'accessing a SQL2000 database'.
The RS2000 needs to reside in a SQL2000 db, but it can access any OLE
DB compliant datasource.
Likewise, RS2005 needs to reside in a SQL2005 db, but again it can
access any OLE DB compliant datasource (including SQL2000).
RS2005 will not work installed on a SQL2000 only server.
I don't know whether RS2000 will work from within 2005 and I don't know
why you would try?
SQL2005 is still beta, if you are trying to run it alongside a live
RS2000 implementation on the same server I would advise you strongly
not to!
If you are testing both of these, then maybe consider Virtual PC or
Virtual Server, this is a safe way of testing different things on one
machine.
Go here for white papers and all things SQL2005 from Microsoft;
http://www.microsoft.com/sql/2005/
Regards
Chris
Hennie wrote:
> Can I install Reporting Serer 2005 and 2003 on the same server, each
> 1 accessing a seperate SQL2000 database?
> Are there any white papers on this regard?
> Thanks|||Just a quick comment. At release RS 2005 is supposed to be able to install
using a SQL Server 2000 database. You still have to have a 2005 license
though.I don't know if the beta will do this or not.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Chris McGuigan" <chris.mcguigan@.zycko.com> wrote in message
news:%233DX0$YnFHA.3628@.TK2MSFTNGP10.phx.gbl...
> Can you clarify the versions;
> I assume you mean RS2000 (there isn't a 2003).
> Also what do you mean by 'accessing a SQL2000 database'.
> The RS2000 needs to reside in a SQL2000 db, but it can access any OLE
> DB compliant datasource.
> Likewise, RS2005 needs to reside in a SQL2005 db, but again it can
> access any OLE DB compliant datasource (including SQL2000).
> RS2005 will not work installed on a SQL2000 only server.
> I don't know whether RS2000 will work from within 2005 and I don't know
> why you would try?
> SQL2005 is still beta, if you are trying to run it alongside a live
> RS2000 implementation on the same server I would advise you strongly
> not to!
> If you are testing both of these, then maybe consider Virtual PC or
> Virtual Server, this is a safe way of testing different things on one
> machine.
> Go here for white papers and all things SQL2005 from Microsoft;
> http://www.microsoft.com/sql/2005/
> Regards
> Chris
> Hennie wrote:
>> Can I install Reporting Serer 2005 and 2003 on the same server, each
>> 1 accessing a seperate SQL2000 database?
>> Are there any white papers on this regard?
>> Thanks
>

Reporting Services

Does anyone have any advise regarding implementing SQL Server Reporting Services on a seperate server from the SQL Server database?

1. Can this be done?

2. If it can be done what are the pros and cons?

Thank you.(1) yes it can be done.you would need to be able to establish a connection to the sql server though.

(2) am not xactly sure about the pros and cons..its just another way you can do it..maybe someone else here can give you more details about that..

hth

Reporting Server - 2nd SQL Server

Hi,
I have a SQL server running in our production environment. I would like to
create a test/reporting environment running on a seperate server. I will
take my DB backups from the production server and then restore it onto my
2nd server. What is the best way to get the 2nd system updated? I do not
want a live replication all day long. I simply need a method to update the
2nd server once a day at a scheduled time.
Ideas?
Thank you.You can use the log shipping model. This means that you can restore the logs
from your production server on the reporting server.
Here are some details you can actually see how it could be implemented:
http://www.sql-server-performance.c...og_shipping.asp
Let me know if it helps..
"Dragon" wrote:

> Hi,
> I have a SQL server running in our production environment. I would like to
> create a test/reporting environment running on a seperate server. I will
> take my DB backups from the production server and then restore it onto my
> 2nd server. What is the best way to get the 2nd system updated? I do not
> want a live replication all day long. I simply need a method to update the
> 2nd server once a day at a scheduled time.
> Ideas?
> Thank you.
>
>|||The log shipping model will leave your second server in a read only
state, rendering it useless for testing.|||The link I posted states pros and cons of this model. It all depends of what
type of testing.
"mryan" wrote:

> The log shipping model will leave your second server in a read only
> state, rendering it useless for testing.
>|||Thank you all for your replies.
Unfortunately I will need a totally indipendent system for my testing.
Having read only will not work as we will not be able to test applications
against it. Any other ideas? What about incremental backups and restores?
"Edgardo Valdez, MCSD, MCDBA"
<EdgardoValdezMCSDMCDBA@.discussions.microsoft.com> wrote in message
news:5B49860B-A765-49CE-9719-EE982B37ED00@.microsoft.com...[vbcol=seagreen]
> The link I posted states pros and cons of this model. It all depends of
> what
> type of testing.
> "mryan" wrote:
>

Reporting Server - 2nd SQL Server

Hi,
I have a SQL server running in our production environment. I would like to
create a test/reporting environment running on a seperate server. I will
take my DB backups from the production server and then restore it onto my
2nd server. What is the best way to get the 2nd system updated? I do not
want a live replication all day long. I simply need a method to update the
2nd server once a day at a scheduled time.
Ideas?
Thank you.You can use the log shipping model. This means that you can restore the logs
from your production server on the reporting server.
Here are some details you can actually see how it could be implemented:
http://www.sql-server-performance.com/sql_server_log_shipping.asp
Let me know if it helps..
"Dragon" wrote:
> Hi,
> I have a SQL server running in our production environment. I would like to
> create a test/reporting environment running on a seperate server. I will
> take my DB backups from the production server and then restore it onto my
> 2nd server. What is the best way to get the 2nd system updated? I do not
> want a live replication all day long. I simply need a method to update the
> 2nd server once a day at a scheduled time.
> Ideas?
> Thank you.
>
>|||The log shipping model will leave your second server in a read only
state, rendering it useless for testing.|||The link I posted states pros and cons of this model. It all depends of what
type of testing.
"mryan" wrote:
> The log shipping model will leave your second server in a read only
> state, rendering it useless for testing.
>|||Thank you all for your replies.
Unfortunately I will need a totally indipendent system for my testing.
Having read only will not work as we will not be able to test applications
against it. Any other ideas? What about incremental backups and restores?
"Edgardo Valdez, MCSD, MCDBA"
<EdgardoValdezMCSDMCDBA@.discussions.microsoft.com> wrote in message
news:5B49860B-A765-49CE-9719-EE982B37ED00@.microsoft.com...
> The link I posted states pros and cons of this model. It all depends of
> what
> type of testing.
> "mryan" wrote:
>> The log shipping model will leave your second server in a read only
>> state, rendering it useless for testing.
>>

Reporting Server - 2nd SQL Server

Hi,
I have a SQL server running in our production environment. I would like to
create a test/reporting environment running on a seperate server. I will
take my DB backups from the production server and then restore it onto my
2nd server. What is the best way to get the 2nd system updated? I do not
want a live replication all day long. I simply need a method to update the
2nd server once a day at a scheduled time.
Ideas?
Thank you.
You can use the log shipping model. This means that you can restore the logs
from your production server on the reporting server.
Here are some details you can actually see how it could be implemented:
http://www.sql-server-performance.co...g_shipping.asp
Let me know if it helps..
"Dragon" wrote:

> Hi,
> I have a SQL server running in our production environment. I would like to
> create a test/reporting environment running on a seperate server. I will
> take my DB backups from the production server and then restore it onto my
> 2nd server. What is the best way to get the 2nd system updated? I do not
> want a live replication all day long. I simply need a method to update the
> 2nd server once a day at a scheduled time.
> Ideas?
> Thank you.
>
>
|||The log shipping model will leave your second server in a read only
state, rendering it useless for testing.
|||The link I posted states pros and cons of this model. It all depends of what
type of testing.
"mryan" wrote:

> The log shipping model will leave your second server in a read only
> state, rendering it useless for testing.
>
|||Thank you all for your replies.
Unfortunately I will need a totally indipendent system for my testing.
Having read only will not work as we will not be able to test applications
against it. Any other ideas? What about incremental backups and restores?
"Edgardo Valdez, MCSD, MCDBA"
<EdgardoValdezMCSDMCDBA@.discussions.microsoft.com> wrote in message
news:5B49860B-A765-49CE-9719-EE982B37ED00@.microsoft.com...[vbcol=seagreen]
> The link I posted states pros and cons of this model. It all depends of
> what
> type of testing.
> "mryan" wrote: