Precision, Performance, Confidence. ™

Moving a MET/TEAM database to a different server

Three major operations need to be performed to execute a successful database move:

1) Relocate the database on the new SQL instance.

2) Point the MET/TEAM website to the new database.

3) Re-register the application (because moving the database requires re-licensing to the new DB server).

Notes you need to be aware of prior to starting the process.

Note 1: MET/TEAM's licenses are tied to the computer and environment where MET/TEAM is installed so any changes will most likely invalidate the registration. Because of this, follow the steps in this article to capture your current state because these same code(s) will be needed by you to re-register. :
How to capture MET\TEAM licensing \ registration data

Note 2: If you are moving your database from a full SQL Server instance to a local instance and intend on using the files provided with the MET/TEAM installer, you need to be aware of the following...  The MET/TEAM install includes SQL Server 2008R2 and or 2012 express which has a limit of a 10G database size. If your current database is larger than 10G in size, a full version of a supported SQL Server version will need to be installed on the new computer.  If a full version needs to be purchased, this is accomplished thru Microsoft, not Fluke Calibration.  The current requirements for MET/TEAM can be found on our website:  MET/TEAM requirements

I Relocate the database to a new server

1) To prevent modification of the data during this process, first stop the MET/TEAM website in IIS.  Please see this article: How to Stop, Start or Restart the MET/TEAM website in IIS

How to Stop, Start or Restart the MET/TEAM website in IIS

2) Back up the database on the old SQL Instance. Please see this article: How to manually back up a MET/TEAM database

How to back up a MET/TEAM database


3) Restore the database on the new SQL Instance. Please see this article: How to manually restore a MET/TEAM database

How to restore a MET/TEAM database


II Point MET/TEAM website to the new database 


1) On the web server, open IIS. 
2) On the left panel, expand the connections until you get to the MET/TEAM site. Select that site. 
3) In the middle panel, there is an icon for Connection Strings. It looks like a yellow cylinder. Double-click it. 
4) In Connection Strings, double-click on the entry titled "MetTrack_Dev" and edit the connection string's server setting to point to the newly installed SQL Instance. 


5) Repeat steps 2-4 for the Customer Portal Site, if necessary. 
6) Open the Registry Editor. 
7) Go to the following key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EmailAlerts 


8) Double click on the ImagePath key value, and edit the string's SQL Instance so that it points to the new instance.


III Re-register the application 


1)  Before starting this process it is important to ensure the MET/TEAM website and Application pool are stopped described in this article...
How to Stop, Start or Restart the MET/TEAM website in IIS

2) Run the following SQL command against the database:

DELETE FROM dbo.Licenses 
UPDATE dbo.Servers SET mNotes = NULL

If instructions are needed, please see this article: 
How to run SQL scripts for MET/TEAM


3) Start the website in IIS. (For instructions, use the same article mentioned above in step  1 above.

3) Attempt to log into MET/TEAM and register it in the normal manner.

If instructions are needed, please see this article: 

How to request and apply License(s) for MET/TEAM


If you see a database logon failure when you enter the website, it is most likely because the user account that is running the website has insufficient privileges to access the new database. If you go into IIS and enter the Application Pools screen, you can see the user account running the MET/TEAM application pool (under the Identity column). This account needs to, at the very least, be a db_owner of the new server's MET/TEAM database.

NOTE: Depending on the reasons for moving your database, you should review the following "System Default" records to be sure their 'values' are accurate within the new environment:

Also review any "Alerting Schedules" that are configured to ensure they are still valid.

Have more questions? Submit a request

Comments

Please sign in to leave a comment.