Just ran the first Live to Test refresh since converting to v11. Do I have to re-run TIM against Test also? I’m getting those nasty services errors logging in to Tessitura which I believe are TIM related.
David,
The Moving a Database documentation has been updated for v11 and includes all the steps you need to take for a Live to Test copy.
If you are still having an issue please feel free to open a support ticket.
Best,
Anna
Hi Anna,
A question about the services user... I noticed in the Moving a Database document you posted, a lot of code is included to rebuild that user from scratch. However, the Resolving Orphan Users section on p.18 mentions the same sp_change_users_login procedure I mentioned in my previous post for resolving orphaned users.
We actually use the sp_change_users_login approach for our services user as well, and haven't experienced any problems (at least not yet). Do you know why it is advised to drop/recreate the services user from scratch rather than using sp_change_users_login to reassociate the login with the database user?
Thanks,David
Anna,
Is there a document for V11 Live to V12 Test?
Thanks
John
John,
After moving your live v11 database to a test v12 environment you will need to run the v12 TIM Upgrade and Migration processes. There is a note in the v12 Upgrade Instructions on refreshing a v12 TEST instance with a copy of a v11 LIVE instance. I pasted it below:
NOTE: If you plan to refresh your v12 Test instance with a copy of a v11 Live instance using the detach/attach method, in order to go through the migration process again, you will first need to delete the Documents folder from the Database Documents Path or the FILESTREAM portion of the upgrade will fail. If you are using the backup and restore method, this will not be an issue. The Moving a Database v12 document details moving the Tessitura database from one server to another such as when copying from Live to Test.
--Chris