***You should test the upgrade before running it in the live environment***
Background
After upgrading the service desk program the MDM should be run to upgrade the database. When the MDM runs it checks the database for tables and columns that need to be changed to match the settings for the latest version.
Problem
While running the upgrade scripts a timeout error is shown and the database fails to upgrade.
Solution
1. Make sure that you have increased the command timeout for the framework.
A. This can be done by clicking the edit button next to the framework and changing the command timeout parameter to 600 or larger.
2. Check the MDM log from the link that is available on the MDM upgrade window.
3. Scroll to the end of the log and note the last table it was updating when the timeout occurred.
4. Check the table in the database for the column mdm_temp_column. And If it exists, delete it.
5. Run the following SQL select statement against the table "SELECT * FROM <TableName>" (be patient, this can take 10-30 minutes to finish)
6. Run the MDM upgrade again.
This will load the contents of the table into the memory of the SQL server. When the MDM upgrade runs the next time it won't have to read the data from disk and will be able to get through the table much faster, without timing out. If you do receive one timeout error on the upgrade then it is likely that it will happen more than once, on different tables. For each table that it times out on, delete the mdm_temp_column and run the SQL statement against the new table. (The results from the previous SQL statement(s) should still be in memory). Repeat these steps for each table until the upgrade is able to run without any more timeout errors.
Once you have completed the MDM upgrade successfully, copy down each of the SQL statements that were run. When upgrading the live server, run each of the SQL statements against the live database before running the MDM upgrade. This will cache all of the tables before you start the MDM upgrade for the first time and should prevent any timeout errors.
