CMC - server change impacts on recurring reports

[careymw]

Does anyone have any suggestions on how to quickly modify existing recurring report instances when a database is moved to another server. Not only do each of the reports have to be opened - pointed to the new server - save - then refreshed... the recurrings also have to be set up from the ground up. You can't use replace because it won't allow you to modify what appears in the database window.

I've seen the Use Custom Database logon would we use this? Any suggestions are appreciated.

 

[hilfy]

A lot of this depends on what type of database you're using and how the connection is set up.

If you're using Oracle, you could just update the TNSNames file on the report server so that it points to the new server.

If you're using an ODBC connection, regardless of the database type, just point the ODBC connection to the new server.

In either of these situations, you shouldn't have to update any of the reports or the recurring schedules.

-Dell

A computer only does what you actually told it to do - not what you thought you told it to do.

 

[careymw]

The reports impacted are SQL reports. Doesn't Crystal store the server information in the reports for SQL?

 

[hilfy]

It stores the connection information based on the database type. If you're connecting to SQL Server through an ODBC connection (as opposed to an OLE DB connection) then the actual connection info is stored in the ODBC connection definition, not in the report itself. The report stores the info about which ODBC connection to use. As long as the database name is the same, updating the ODBC connection on the server should take care of everything.

-Dell

A computer only does what you actually told it to do - not what you thought you told it to do.