So for reasons I won't go into, we recently had to re-configure our clients Tridion 2013 SP1 CM to use a new SQL Server.
After the usual planning and content freeze, it basically went like this:
- Backup old CM db & copy to new SQL Server.
- Restore backup onto new SQL Server.
On CM server itself:
- Stop all services, shutdown COM+ and stop IIS.
- Open Tridion Configuraiton snap-in and update the database section with new details. Save & close.
- Restart services and IIS.
We had a few initial MS DTC issues that stopped us from saving schemas for example, but these were overcome. It's when we turned the old SQL Server off that things got strange.
On first load of the CM in the browser we got an SQL connection error notification. Also, copying & pasting multiple components just wouldn't work - I traced this to the same SQL connection error being thrown by the Tridion Batch Processing Service.
When we turned back on the old CM SQL Server the error went away and multiple copy/paste worked!
There are other Tridon components installed (e.g. AM or TM) and my understanding is that the only db connection string is the one managed through the snap-in.
Is there a step I've missed from the above? Perhaps the Batch Processor "kept hold" of the old reference somehow?