Planning to move the sql server repository based databases to a diff server

[Former Member]

we are planning to move all our repository sql server databases to a different server, what is teh procedure to configure our dataservices to point to this new server.

Please kindly provide any helpful details.

we have almost 11 repository related databases.

Thanks a lot for teh helpful info.

[DayaJha]

Hi Rogers,

Regarding your query we can say that if you want to migrate Local, Profile, Secure Central reposiory from SQL Server to other RDBMS then please take following steps in consideration:

• Create a Check list of Configuration of Data-Store, Number of Jobs (Batch/Real Time Jobs), Source and Target Information.
• Take the Database backup of Local, Profile, Secure Central reposiory
• Take the ATL backup of Local reposiory
• Take the Substitution Parameter backup of Local Repository in form of ATL
• Take the System Configuration backup of Local Repository in form of ATL
• Now Using Repository manager create new blank Local Repository (RDBMS as per your requirement)
• Now  deploy ATL backup of Local reposiory in New Blank (RDBMS) Local Repository
• Now  deploy Substitution Parameter backup of Local reposiory in New Blank (RDBMS) Local Repository
• Now  deploy System Configuration backup of Local reposiory in New Blank (RDBMS) Local Repository
• After doing this activity re-check the Data-Flow Configuration,Substitution Parameter and System Configuration of Old Local repository and New Local repository
• Repeat these steps for all Local repository activity.
• And regaring Source and Target RDBMS migration please contact your DBA For this you can also use New Tools in SAP Business Objects Data Services 4.0 called "Data Services Workbench" , Pleas confirm this activity with SAP also.

For more details please refer below links.

Data Services Workbench Part 1:

Links:
http://scn.sap.com/community/data-services/blog/2013/01/24/data-services-workbench-part-1

Data Services Workbench Part 2

Links:
http://scn.sap.com/community/data-services/blog/2013/01/25/data-services-workbench-part-2

Hope this will help you as well.

Thanks,

Daya

[dv8shn]

Daya, regarding this point:

• And regaring Source and Target RDBMS migration please contact your DBA For this you can also use New Tools in SAP Business Objects Data Services 4.0 called "Data Services Workbench" , Pleas confirm this activity with SAP also.

The Data Services 4.0 Workbench is a tool to replicate database tables across systems, so it would seem a great idea to just replicate the repository tables across to a new RDBMS. I would not suggest it however, as these tables are internal to SAP and only some of them are documented. The chances of this approach working aren't high.

Bob

[dv8shn]

This is quite easily done, Guy.

1. Create the 11 new schemas in the new RDBMS.
2. Use Repository Manager to create the entities in the schema, repeat this step 11 times.
3. Use Server Manager to link the new repositories to the Job Server, repeat this step 11 times.
4. Use Central Management Console to create the 11 new repository entries.

The Designer can then be used to export the repository code.

1. Login to the first defunct local repository using Designer.
2. In the Local Object Library, click in the white space and in the context menu select Repository | Export to File, save the ATL file where you can find it.
3. In the Local Object Library, click in the white space and in the context menu select Repository | Export System Configurations, save the ATL file where you can find it.
4. In the Local Object Library, click in the white space and in the context menu select Repository | Export Substitution Parameter Configurations, save the ATL file where you can find it.
5. Close Designer.
6. Login to the replacement repository, and using the Tools menu select Import From File. Import the 3 ATL files created in the previous step.
7. Close Designer.

I hope this helps. Note that the method I've specified will cause all Job Execution statistics to be lost as well as linkages to the log files on the Job Server's local disk. In a development environment this isn't usually a problem. However, if this is production, more complicated methods must be used to move the repository and keep the statistics intact.

Bob Damm