Migrating an instance of a Time Matters(c) database can be somewhat of a daunting task to many IT professionals and Consultants. Many that I know would not even attempt this without having tech support on the line to hold their hand. Often times you will run in to a situation where you have to move a database from one SQL Server to another due to hardware upgrades, upgrading from an express edition of SQL to SQL server standard, or even having to reinstall SQL. All things aside, it can be a straightforward process if you follow these steps. However you must be aware that instance specific data is stored regarding the running SQL server and there is a possibility of running into licensing issues.
1. Try to make the move when you know that Lexis Nexis(s) support is available in case you need to have the licensing server reset (shouldn’t have to but it is a possibility).
2. Backup the Time Matters Database ***
3. Copy the files over to the proper directory for your new SQL server.
4. The secret part, run the Time Matters Orphaned User Script:
USE TIMEMATTERS10 EXEC sp_change_users_login 'Auto_Fix', 'lntmuser'
For Time Matters9:
Use TIME MATTERS9 EXEC sp_change_users_login 'Auto_Fix', 'tm9user'
This will reset the Default TM user and allow you to point the application at the new SQL server instance
If you get an error when trying to auto_fix the user, you probably have to recreate the user first. Try:
CREATE LOGIN [lntmuser] WITH PASSWORD=N'êV]K6íMiíÄ÷ùUUvé"³,çêÅÏ GO
And then rerun the orphaned auto_fix script
Launch Time Matters Click Option > Databases > Toggle to New Server. Login You’re Done
For more info see the MS tech article: http://bit.ly/9GNwzj