Changing the OBDC for a lot of reports

[mark_wilson5]

Hi

One of the databases that has 180 reports pointing at it - is moving server.

There database is keeping the same name but there is no DNS alias on the existing server

The odbc driver will need to be updated to SQL server native client 11 and the Application Intent set to read only and Multi subnet fail over set to true

My problem is I will have to go into all 180 reports individually and set Datasource Location to the new server once set up. Then probably need to reschedule the reports that scheduled to pick up the new odbc

Is there any quicker way of doing this?

[former_member665074 · Accepted solution]

Had the same issue.

I developed a simple utility that loops through a user defined folder and updates the logon properties for all reports.

If you're visual studio savvy, I'm sure you can figure it out.

Out of curiosity, are you doing this for TLS 1.2 compliance?

See my response on this thread:

https://answers.sap.com/questions/12837980/crystal-reports-are-nor-running-when-tls-12-is-ena.html?c...

[DellSC]

One of the ways I've handled this in the past is to create a new ODBC connection with the same name as the old one. This will have the updated client and other settings. Since the reports look for the ODBC connection by name, you don't have to do anything to them to get them to run unless you're using a really old version of the ODBC driver now (like the one that comes installed on Windows).

-Dell