I have my Central Repository, Local Repositoty and Data Cleanse directories installed on a SQL Server that has been scheduled to be out of our environment becuase of the aging hardware.
I have a new SQL Server location that is ready to receive the repositores, however I have not found any documentation on how I should go about prefroming this migration.
Moving the actual SQL Server databases is something that I am very familar with, so I think I should be OK there. However, I’m unclear on how I make the Data Services system point to the new SQL Server instead of the old.
Okay yes there would be some glitches in the DI. To make everything clean, you would have to un-register the repositories from the job server. Otherwise DI Server Manager is not allowing to remove them. Why because whenever we change the Repo information, it usually asks for the Database Password. So if one doesn’t exist then how would I remove it? We cannot force remove anything also. This happened for me when I changed the DB name. So I had to leave that orphan repo info just like that which I don’t like from a Standards perspective
Also, if you have the batch files you would have to mass replace the DB name.
If it is Production, then yes you would have to freeze the PROD and only do this.
I have been successful in moving the reposities to the new server.
However, I have two real-time jobs that are no longer working. It appears that they are not getting pointed to the new servers. If I bring the old repository SQL Server databases back online then the real time jobs are able to run.
I have looked everywhere that I know to look but I can’t see wherer these jobs are getting there server information from.
The only errors are in the admin console where I can see that the jobs are trying to connect to the wrong database server. Nothing very meaningful to see there - I know that’s is the problem
What I don’t see are any editable references to the wrong database that can be changed. In fact I see no references to the old database anywhere - I have updated everything that I know.
– a) Create the central and developer repositories on the new server.
– b) Export the Project (full) from Old repository to an .atl file.
– c) Import the .atl file in the new server developer repository.
– d) Attach the repositories to Job Server
– e) Add repository, user in DS Console.
– f) Change the Data Store connections to point to New Server.
– g) Create Job Schedule’s and you are good to go!!!
This method does seem to work in the sense that my jobs, dataflows, data stores, etc have been sucessfully moved and appear to work. However, this method does not appear to move over other important items, such as the NCOALink Certification log files. These appear to be stored in the CSLSTATS and PAFBALASTATS database tables.
Without this type of information this really was not a repository move or migration. Instead it was a copy of job informaiton to a new repository. I would still be required to keep the old repository around in order to get access to these cerification logs (which mush be kept for a minimum of 5 years).
Is there anything that can be done to move this data, short of mannually figuring out each table and doing an export and import directly in SQL?
You never mentioned about the Certificates in your earlier post
Can you try this first on a DEV environment and check whether you are able to export the certificates including the logs to a new location on the new server. ?
Make sure you use the correct repository where the Certificate and Logs data is stored. This should be done only once otherwise you will see duplicate information. If the data is huge then it will take some time… also make sure the user id that you are using has enough privileges…from server to server.
Select Management > CertificationLogs, and select the repository that contains the certification log that you want to export.
Click the NCOALink tab.
Select the date range that contains the data that you want to export.
Select the NCOALink licensee ID for the logs that you want to export, or select All NCOA Licensee IDs.
Specify the location where the certification logs will be exported.
The defaultlocation is LINK_DIR\DataQuality\certifications\CertificationLogs\repository.
To reset the export location to the default,click the Reset button.
If you want to overwrite an existing log file, click the Overwrite option.
Click the Search button. The page displays the available log files with the specified criteria. You can sort the log files using the column headers. The “Data Available” column has a Yes status when there is data for atleast one of the log types (PAF, Bala, or CSL). A No status indicates that no data is available and will result in an empty log file for each type.
Select the log file(s) that you want to export or select the checkbox next to “Select All”.
Click the Export button. After the log file is exported, a confirmation message is displayed at the top of the page.
Thanks BO_Chief. SOrry I did not mention the Certificates earlier. I was approaching this with the mind set of being able to migrate the entire repository, which would naturally include the NCOALink Certification Logs. However it appears that this will need to be more recreation and partial repopulation rather than a true migration.
I can certainly export the monthly reports from the current repository and save these files on my file system. I was hoping that I would be able to retain this history in the repository to simplify keeping up with which certification logs are where.
Exporting these logs and placing them on the new server do not really do anything within the Management Console, as it is only looking at the database itself and not any text files on the local filesystem.
Therefore it would appear that there is not really a method available for a true repository migration?
Hello Experts.
I am facing a similar issue with the SQL server db move. Development repositories I was able to get moved, but central repository doesn’t work. It still gives me error that it is trying to connect to the old repository db. Here are the steps I did
For local/developer repository- Successful
1.DBA moved db from old server to new server with the user permissions granted
2.Took atl backup of repository
3.Deleted repo connection from Job scheduler
4.Deleted repo connection from CMC
5.created the same repository via repository manager
6.Added repo connection in jobschedular and CMC with the new server details
7.Connected to the repository and imported the atl backup file
For central repository- Failure
1.Deleted central repo connection from CMC
2.Created same central repo from repository manager on the new server
3.DBA restored DB from the old server to new server
4.Created central repo connection in CMC with the new SQL db
5.Connected to local/developer repo and tried to connect to the newly added central repo
–Here the connection fails with error that it is trying to connect to the old DB server. I am not sure which metadata table or place it has the old connection stored? Can you please help me here.
I also checked DSConfig file and I do not see any connection pointing to old db.
Query the repository object from the CMC and ensure the value for SI_DB_RESERVED1 is correct. If not you will need to update it with the correct database server name.
Also check the AL_MACHINE info table and update any rows that contain the old database name to the new one. If you had to update any rows, its possible that unregistering and re-registering the central repo in the CMC will work, meaning you will not have to update SI_DB_RESERVED1.
(BOB member since 2011-04-30)
(BOB member since 2008-07-17)
(BOB member since 2006-02-02)
(BOB member since 2012-04-25)