Quest InTrust database movement SQL 2014 to SQL 2016.

Hi mcsebala,

Sorry to keep you waiting,

For configuration database:

1. Make sure your new SQL server is ready. Set up security of the new SQL server the same way as the old so that all accounts that were used on the old SQL work successfully on the new one
2. Stop all InTrust services (command line “net stop adcrpcs /y”)
3. Detach Config db on the old SQL server
4. Copy Config DB files to the new SQL server (you might need to give additional permissions explicitly to the DB files if the next step fail)
5. Attach Config DB on the new SQL server
6. On InTrust server machine open the registry key “HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Aelita\ADC\CfgConnection” and change the “Data Source” value from the old SQL server name to a new one
7. Start all InTrust services (command line “net start itrt_svc”)
8. Open InTrust Manager, go to “Quest InTrust Manager | Configuration | Data Stores | Databases” and in the properties of the “InTrust Configuration Database” object change the old SQL server name to a new one

For Alert and Audit databases:

• If you don’t need the previous data in these databases, you may create them anew on the new SQL server. In this case please apply only steps 1 and 8 from the above list
• If you think your Alert and Audit databases contain data you still need, then please apply steps 1, 3-5, 8 from the above list
• If you use Monitoring Console for alerts or Knowledge Portal for SSRS reports please review the administration pages of those products and make sure the configuration is consistent

Thank you sir for the reply.

Every time your are my helping hand.