Upgrade the Database Structure

There are several methods for upgrading your database depending on your existing installation. You must verify your existing database version and follow the appropriate method.

To verify your database version:

1. Open SQL Server Management Studio.

2. Connect to the AVEVA NET Gatekeeper or AVEVA Change Manager database.

3. Locate the table named dbo.TIM_VERSION. The database version is in the first row of the TIM_VERSION_NO column.

Follow the appropriate method:

Upgrading Database Version 3.4.4

When upgrading from TIM to AVEVA NET Gatekeeper or AVEVA Change Manager, you must first upgrade the database from version to 3.4.4.

Note: Before upgrading, make a backup of the existing database.

To upgrade the database:

4. Navigate to the sub-directory Database\ApplicationDB\Update\From 4.9 to 5.0.1.

   Note: The sub-directory mentioned above should be available in the timInstallPath directory , typically C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application, as it is installed along with AVEVA NET Gatekeeper and AVEVA Change Manager Common files by means of the installer.

5. In each of the following files, replace any instances of the username tim_user with a valid username for the existing database. Alternatively, if the database owner is used to connect to the database from the application, remove the lines that have a format similar to "GRANT EXECUTE… TO tim_user…":

   • bug_2669.sql

   • bug_2775.sql

   • bug_3609.sql

   • bug_3877.sql

   • sp_TIM_CreateClassLibraryTableBackups.sql

   • sp_TIM_RemoveClassLibraryTableBackups.sql

   • task_2277.sql

6. Navigate to the Database\ApplicationDB\Update\From 4.9 to 5.0.1 sub-directory, and open the sub-directory Running Scripts.

7. Open AVEVAScripts.cmd in Notepad, and update the following values:

   • @SET "SQLCMD_ARGS=-U DB_OWNER_NAME -P DB_OWNER_PASSWORD -S DB_SERVER_NAME -d DB_NAME"

   • @SET "SQL_SCRIPT_ROOT=enter_base_path_where_SQL_scripts_listed_below_are_located"

     For example, @SET "SQL_SCRIPT_ROOT= C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 4.9 to 5.0.1"

   • @SET "AREA_ATTRIBUTE_GEICL_ID=enter_area_attribute_GEICL_id"

     For example, @SET "AREA_ATTRIBUTE_GEICL_ID=3125"

   Note: If you are updating from TIM 4.9 or older version to Technical Information Manager (TIM) 5.0 or newer version, enter the Generic Engineering Information Class Library (GEICL) ID of the AREA attribute specified in the Class Library used by the old version of the application. It is needed for correct migration of the data related to AREA codes into the newer version. If you are updating from the TIM 5.0 or above, leave this parameter as it is ("enter_area_attribute_GEICL_id") to avoid running the redundant migration operation.

8. Save the updates, and exit from the script.

9. Create a Results folder in the folder where the upgrade scripts are located. For example, C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 4.9 to 5.0.1\Results.

10. To run the upgrade script, double-click the AVEVAScripts.cmd file.

11. Verify the Results folder for any errors.

Upgrading Database Version 3.4.5

Before upgrading AVEVA NET Gatekeeper or AVEVA Change Manager, you must first upgrade the structure of the existing database version to 3.4.5.

Note: Before upgrading, make a backup of the existing database.

To upgrade database structure:

12. Navigate to the sub-directory Database\ApplicationDB\Update\From 5.0.1 to 5.0.2.

    Note: The sub-directory mentioned above should be available in the directory timInstallPath, typically C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application, as it is installed along with AVEVA NET Gatekeeper and AVEVA Change Manager Common files by means of the installer.

13. In each of the following files, replace any instances of the username tim_user with a valid username for the existing database. Alternatively, if the database owner is used to connect to the database from the application, remove the lines that have a format similar to "GRANT EXECUTE… TO tim_user":

    1. task_4498.sql

    2. bug_4567.sql

    3. bug_4982_5050.sql

    4. Feature_3455.sql

    5. Feature_4272.sql

    6. Feature_4349.sql

14. Navigate to the Database\ApplicationDB\Update\From 5.0.1 to 5.0.2 sub-directory, and open the sub-directory Running Scripts.

15. Open AVEVAScripts.cmd in Notepad, and update the following values:

    • @SET "SQLCMD_ARGS=-U DB_OWNER_NAME -P DB_OWNER_PASSWORD -S DB_SERVER_NAME -d DB_NAME"

    • @SET "SQL_SCRIPT_ROOT=enter_base_path_where_SQL_scripts_listed_below_are_located"

    For example, @SET "SQL_SCRIPT_ROOT= C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.1 to 5.0.2"

16. Save the updates, and exit from the script.

17. Create a Results folder in the folder where the upgrade scripts are located. For example, C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.1 to 5.0.2\Results.

18. To run the upgrade script, double-click the AVEVAScripts.cmd file.

19. Verify the Results folder for any errors.

Upgrading Database Version 3.5.0

Before upgrading AVEVA NET Gatekeeper or AVEVA Change Manager, you must first upgrade the structure of the existing database version to 3.5.0.

Notes:

20. Before upgrading, make a backup of the existing database.

21. If Naming-and-Numbering (N&N) tables are used as either a part of the AVEVA Change Manager database or as a separate N&N database, apply the Database\NandN\004-Alter-v1.0.1-to-v.1.0.2.sql script.

To upgrade database structure:

22. Navigate to the sub-directory Database\ApplicationDB\Update\From 5.0.2 to 5.0.3.

    Note: The sub-directory mentioned above should be available in the directory timInstallPath, typically C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application, as it is installed along with AVEVA NET Gatekeeper and AVEVA Change Manager Common files by means of the installer.

23. In each of the following files, replace any instances of the username tim_user with a valid username for the existing database. Alternatively, if the database owner is used to connect to the database from the application, remove the lines that have a format similar to "GRANT EXECUTE… TO tim_user":

    7. bug-4098.sql

    8. bug-4963.sql

    9. bug-5261.sql

    10. Feature-4474.sql

    11. improvement-4986.sql

24. Navigate to the Database\ApplicationDB\Update\From 5.0.2 to 5.0.3 sub-directory, and open the sub-directory Running Scripts.

25. Open AVEVAScripts.cmd in Notepad, and update the following values:

    • @SET "SQLCMD_ARGS=-U DB_OWNER_NAME -P DB_OWNER_PASSWORD -S DB_SERVER_NAME -d DB_NAME"

    • @SET "SQL_SCRIPT_ROOT=enter_base_path_where_SQL_scripts_listed_below_are_located"

    For example, @SET "SQL_SCRIPT_ROOT= C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.2 to 5.0.3"

26. Save the updates, and exit from the script.

27. Create a Results folder in the folder where the upgrade scripts are located. For example, C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.2 to 5.0.3\Results.

28. To run the upgrade script, double-click the AVEVAScripts.cmd file.

29. Verify the Results folder for any errors.

Upgrading Database Version 3.5.1

Before upgrading AVEVA NET Gatekeeper or AVEVA Change Manager, you must first upgrade the structure of the existing database version to 3.5.1.

Note: Before upgrading, make a backup of the existing database.

To upgrade database structure:

30. Navigate to the sub-directory Database\ApplicationDB\Update\From 5.0.3 to 5.0.4.

    Note: The sub-directory mentioned above should be available in the directory timInstallPath, typically C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application, as it is installed along with AVEVA NET Gatekeeper and AVEVA Change Manager Common files by means of the installer.

31. In each of the following files, replace any instances of the username tim_user with a valid username for the existing database. Alternatively, if the database owner is used to connect to the database from the application, remove the lines that have a format similar to "GRANT EXECUTE… TO tim_user":

    12. bug-841.sql

    13. bug-2620.sql

    14. bug-5606.sql

    15. bug-5688.sql

    16. bug-5719.sql

    17. Improvement-2929.sql

    18. Improvement-5727.sql

    19. Improvement-4800.sql

    20. Improvement-5795.sql

32. Navigate to the Database\ApplicationDB\Update\From 5.0.3 to 5.0.4 sub-directory, and open the sub-directory Running Scripts.

33. Open AVEVAScripts.cmd in Notepad, and update the following values:

    • @SET "SQLCMD_ARGS=-U DB_OWNER_NAME -P DB_OWNER_PASSWORD -S DB_SERVER_NAME -d DB_NAME"

    • @SET "SQL_SCRIPT_ROOT=enter_base_path_where_SQL_scripts_listed_below_are_located"

    For example, @SET "SQL_SCRIPT_ROOT= C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.3 to 5.0.4"

34. Save the updates, and exit from the script.

35. Create a Results folder in the folder where the upgrade scripts are located. For example, C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.3 to 5.0.4\Results.

36. To run the upgrade script, double-click the AVEVAScripts.cmd file.

37. Verify the Results folder for any errors.

Upgrading Database Version 3.5.2

Before upgrading AVEVA NET Gatekeeper or AVEVA Change Manager, you must first upgrade the structure of the existing database version 3.5.2.

Note: Before upgrading, make a backup of the existing database.

To upgrade database structure:

38. Navigate to the sub-directory Database\ApplicationDB\Update\From 5.0.4 to 5.0.5.

    Note: The sub-directory mentioned above should be available in the directory timInstallPath, typically C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application, as it is installed along with AVEVA NET Gatekeeper and AVEVA Change Manager by means of the installer.

39. In each of the following files, replace any instances of the username tim_user with a valid username for the existing database. Alternatively, if the database owner is used to connect to the database from the application, remove the lines that have a format similar to "GRANT EXECUTE… TO tim_user":

    21. bug-6427.sql

    22. feature-6199.sql

    23. feature-6277.sql

    24. feature-6278.sql

    25. feature-6322sql

    26. feature-6323.sql

40. Navigate to the Database\ApplicationDB\Update\From 5.0.4 to 5.0.5 sub-directory, and open the sub-directory Running Scripts.

41. Open AVEVAScripts.cmd in Notepad, and update the following values:

    • @SET "SQLCMD_ARGS=-U DB_OWNER_NAME -P DB_OWNER_PASSWORD -S DB_SERVER_NAME -d DB_NAME"

    • @SET "SQL_SCRIPT_ROOT=enter_base_path_where_SQL_scripts_listed_below_are_located"

    For example, @SET "SQL_SCRIPT_ROOT= C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.4 to 5.0.5"

42. Save the updates, and exit from the script.

43. Create a Results folder in the folder where the upgrade scripts are located. For example, C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.4 to 5.0.5\Results.

44. To run the upgrade script, double-click the AVEVAScripts.cmd file.

45. Verify the Results folder for any errors.

Upgrading Database Version 3.5.3

Before upgrading AVEVA NET Gatekeeper or AVEVA Change Manager, you must first upgrade the structure of the existing database version 3.5.3.

Note: Before upgrading, make a backup of the existing database.

To upgrade database structure:

46. Navigate to the sub-directory Database\ApplicationDB\Update\From 5.0.5 to 5.0.6.

    Note: The sub-directory mentioned above should be available in the directory timInstallPath, typically C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application, as it is installed along with AVEVA NET Gatekeeper and AVEVA Change Manager by means of the installer.

47. In each of the following files, replace any instances of the username tim_user with a valid username for the existing database. Alternatively, if the database owner is used to connect to the database from the application, remove the lines that have a format similar to "GRANT EXECUTE… TO tim_user":

    27. bug-6498.sql

    28. feature-6439.sql

    29. feature-6443.sql

    30. feature-6447.sql

    31. feature-6448.sql

    32. feature-6460sql

48. Navigate to the Database\ApplicationDB\Update\From 5.0.5 to 5.0.6 sub-directory, and open the sub-directory Running Scripts.

49. Open AVEVAScripts.cmd in Notepad, and update the following values:

    • @SET "SQLCMD_ARGS=-U DB_OWNER_NAME -P DB_OWNER_PASSWORD -S DB_SERVER_NAME -d DB_NAME"

    • @SET "SQL_SCRIPT_ROOT=enter_base_path_where_SQL_scripts_listed_below_are_located"

    For example, @SET "SQL_SCRIPT_ROOT= C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.5 to 5.0.6"

50. Save the updates, and exit from the script.

51. Create a Results folder in the folder where the upgrade scripts are located. For example, C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.5 to 5.0.6\Results.

52. To run the upgrade script, double-click the AVEVAScripts.cmd file.

53. Verify the Results folder for any errors.

Upgrading Database Version 3.5.4

Before upgrading AVEVA NET Gatekeeper or AVEVA Change Manager, you must first upgrade the structure of the existing database version 3.5.4.

Note: Before upgrading, make a backup of the existing database.

To upgrade database structure:

54. Navigate to the sub-directory Database\ApplicationDB\Update\From 5.0.6 to 5.0.7.

    Note: The sub-directory mentioned above should be available in the directory timInstallPath, typically C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application, as it is installed along with AVEVA NET Gatekeeper and AVEVA Change Manager Common files by means of the installer.

55. In each of the following files, replace any instances of the username tim_user with a valid username for the existing database. Alternatively, if the database owner is used to connect to the database from the application, remove the lines that have a format similar to "GRANT EXECUTE… TO tim_user":

    33. feature-6594.sql

    34. feature-6563.sql

    35. feature-6562.sql

    36. feature-6351.sql

    37. bug-6540.sql

    38. bug-6497.sql

56. Navigate to the Database\ApplicationDB\Update\From 5.0.6 to 5.0.7 sub-directory, and open the sub-directory Running Scripts.

57. Open AVEVAScripts.cmd in Notepad, and update the following values:

    • @SET "SQLCMD_ARGS=-U DB_OWNER_NAME -P DB_OWNER_PASSWORD -S DB_SERVER_NAME -d DB_NAME"

    • @SET "SQL_SCRIPT_ROOT=enter_base_path_where_SQL_scripts_listed_below_are_located"

    For example, @SET "SQL_SCRIPT_ROOT= C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.6 to 5.0.7"

58. Save the updates, and exit from the script.

59. Create a Results folder in the folder where the upgrade scripts are located. For example, C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.6 to 5.0.7\Results.

60. To run the upgrade script, double-click the AVEVAScripts.cmd file.

61. Verify the Results folder for any errors.

Upgrading Database Version 3.5.5 for Application Version 5.0.8

Before upgrading AVEVA NET Gatekeeper or AVEVA Change Manager from 5.0.7 to 5.0.8, you must first upgrade the structure of the existing database version 3.5.5.

Note: Before upgrading, make a backup of the existing database.

To upgrade database structure:

62. Navigate to the sub-directory Database\ApplicationDB\Update\From 5.0.7 to 5.0.8.

    Note: The sub-directory mentioned above should be available in the directory timInstallPath, typically C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application, as it is installed along with AVEVA NET Gatekeeper and AVEVA Change Manager Common files by means of the installer.

63. Navigate to the Database\ApplicationDB\Update\From 5.0.7 to 5.0.8 sub-directory, and open the sub-directory Running Scripts.

64. Open AVEVAScripts.cmd in Notepad, and update the following values:

    • @SET "SQLCMD_ARGS=-U DB_OWNER_NAME -P DB_OWNER_PASSWORD -S DB_SERVER_NAME -d DB_NAME"

    • @SET "SQL_SCRIPT_ROOT=enter_base_path_where_SQL_scripts_listed_below_are_located"

    For example, @SET "SQL_SCRIPT_ROOT= C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.7 to 5.0.8"

65. Save the updates, and exit from the script.

66. Create a Results folder in the folder where the upgrade scripts are located. For example, C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.7 to 5.0.8\Results.

67. To run the upgrade script, double-click the AVEVAScripts.cmd file.

68. Verify the Results folder for any errors.

Upgrading Database Version 3.5.5

Before upgrading AVEVA NET Gatekeeper or AVEVA Change Manager from 5.0.8 to 5.0.9, you must first upgrade the structure of the existing database version 3.5.5.

Note: Before upgrading, make a backup of the existing database.

To upgrade database structure:

69. Navigate to the sub-directory Database\ApplicationDB\Update\From 5.0.8 to 5.0.9.

    Note: The sub-directory mentioned above should be available in the directory timInstallPath, typically C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application, as it is installed along with AVEVA NET Gatekeeper and AVEVA Change Manager Common files by means of the installer.

70. In each of the following files, replace any instances of the username tim_user with a valid username for the existing database. Alternatively, if the database owner is used to connect to the database from the application, remove the lines that have a format similar to "GRANT EXECUTE… TO tim_user":

    39. feature-6674.sql

    40. feature-6703.sql

    41. feature-6704.sql

71. Navigate to the Database\ApplicationDB\Update\From 5.0.8 to 5.0.9 sub-directory, and open the sub-directory Running Scripts.

72. Open AVEVAScripts.cmd in Notepad, and update the following values:

    • @SET "SQLCMD_ARGS=-U DB_OWNER_NAME -P DB_OWNER_PASSWORD -S DB_SERVER_NAME -d DB_NAME"

    • @SET "SQL_SCRIPT_ROOT=enter_base_path_where_SQL_scripts_listed_below_are_located"

    For example, @SET "SQL_SCRIPT_ROOT= C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.8 to 5.0.9"

73. Save the updates, and exit from the script.

74. Create a Results folder in the folder where the upgrade scripts are located. For example, C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.8 to 5.0.9\Results.

75. To run the upgrade script, double-click the AVEVAScripts.cmd file.

76. Verify the Results folder for any errors.

Upgrading Database Version 3.5.6

Before upgrading AVEVA NET Gatekeeper or AVEVA Change Manager from 5.0.9 to 5.0.10, you must first upgrade the structure of the existing database version 3.5.6.

Note: Before upgrading, make a backup of the existing database.

To upgrade database structure:

77. Navigate to the sub-directory Database\ApplicationDB\Update\From 5.0.9 to 5.0.10.

    Note: The sub-directory mentioned above should be available in the directory timInstallPath, typically C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application, as it is installed along with AVEVA NET Gatekeeper and AVEVA Change Manager Common files by means of the installer.

78. In each of the following files, replace any instances of the username tim_user with a valid username for the existing database. Alternatively, if the database owner is used to connect to the database from the application, remove the lines that have a format similar to "GRANT EXECUTE… TO tim_user":

    42. feature-5797.sql

    43. feature-6321.sql

    44. feature-6884.sql

    45. feature-6956.sql

    46. feature-7004.sql

    47. feature-7025.sql

79. Navigate to the Database\ApplicationDB\Update\From 5.0.9 to 5.0.10 sub-directory, and open the sub-directory Running Scripts.

80. Open AVEVAScripts.cmd in Notepad, and update the following values:

    • @SET "SQLCMD_ARGS=-U DB_OWNER_NAME -P DB_OWNER_PASSWORD -S DB_SERVER_NAME -d DB_NAME"

    • @SET "SQL_SCRIPT_ROOT=enter_base_path_where_SQL_scripts_listed_below_are_located"

    For example, @SET "SQL_SCRIPT_ROOT= C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.9 to 5.0.10"

81. Save the updates, and exit from the script.

82. Create a Results folder in the folder where the upgrade scripts are located. For example, C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.9 to 5.0.10\Results.

83. To run the upgrade script, double-click the AVEVAScripts.cmd file.

84. Verify the Results folder for any errors.

Note: To start supporting the user role Allocator in AVEVA NET Gatekeeper, update the respective database using the following SQL script:

IF NOT EXISTS(SELECT * FROM [dbo].[GEN_ROLE] WHERE [dbo].[GEN_ROLE].[GEN_ROLE_NAME] = 'TIMALLOCATORS')
BEGIN
SET IDENTITY_INSERT [dbo].[GEN_ROLE] ON
INSERT [dbo].[GEN_ROLE] ([GEN_ROLE_ID], [GEN_ROLE_GUID], [GEN_ROLE_NAME], [GEN_ROLE_DESC], [GEN_ROLE_ACTIVE], [GEN_ROLE_CREATEDBYID], [GEN_ROLE_CREATEDDATE], [GEN_ROLE_UPDATEDBYID], [GEN_ROLE_UPDATEDDATE], [GEN_ROLE_CODE])
VALUES (5, N'024e8e9e-cb49-4677-8a95-058edecbe2b8', N'TIMALLOCATORS', N'Members of this Role are the only users that are allowed to allocate and check in Tag or Document Numbers in AVEVA NET Gatekeeper', 1, 1, GETDATE(), 1, GETDATE(), N'Allocator')
SET IDENTITY_INSERT [dbo].[GEN_ROLE] OFF
END
GO

Upgrading Database Version 3.5.7

Before upgrading AVEVA NET Gatekeeper or AVEVA Change Manager from 5.0.10 to 5.0.11, you must first upgrade the structure of the existing database version 3.5.7.

Note: Before upgrading, make a backup of the existing database.

To upgrade database structure:

85. Navigate to the sub-directory Database\ApplicationDB\Update\From 5.0.10 to 5.0.11.

    Note: The sub-directory mentioned above should be available in the directory timInstallPath, typically C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application, as it is installed along with AVEVA NET Gatekeeper and AVEVA Change Manager Common files by means of the installer.

86. In each of the following files, replace any instances of the username tim_user with a valid username for the existing database. Alternatively, if the database owner is used to connect to the database from the application, remove the lines that have a format similar to "GRANT EXECUTE… TO tim_user":

    48. feature-6922.sql

    49. bug-7180.sql

87. Navigate to the Database\ApplicationDB\Update\From 5.0.10 to 5.0.11 sub-directory, and open the sub-directory Running Scripts.

88. Open AVEVAScripts.cmd in Notepad, and update the following values:

    • @SET "SQLCMD_ARGS=-U DB_OWNER_NAME -P DB_OWNER_PASSWORD -S DB_SERVER_NAME -d DB_NAME"

    • @SET "SQL_SCRIPT_ROOT=enter_base_path_where_SQL_scripts_listed_below_are_located"

    For example, @SET "SQL_SCRIPT_ROOT= C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.10 to 5.0.11"

89. Save the updates, and exit from the script.

90. Create a Results folder in the folder where the upgrade scripts are located. For example, C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.10 to 5.0.11\Results.

91. To run the upgrade script, double-click the AVEVAScripts.cmd file.

92. Verify the Results folder for any errors.

Upgrading Database Version 3.5.8

Before upgrading AVEVA NET Gatekeeper or AVEVA Change Manager from 5.0.11 to 5.0.12, you must first upgrade the structure of the existing database version 3.5.8.

Note: Before upgrading, make a backup of the existing database.

To upgrade database structure:

93. Navigate to the sub-directory Database\ApplicationDB\Update\From 5.0.11 to 5.0.12.

    Note: The sub-directory mentioned above should be available in the directory timInstallPath, typically C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application, as it is installed along with AVEVA NET Gatekeeper and AVEVA Change Manager Common files by means of the installer.

94. In each of the following files, replace any instances of the username tim_user with a valid username for the existing database. Alternatively, if the database owner is used to connect to the database from the application, remove the lines that have a format similar to "GRANT EXECUTE… TO tim_user":

    50. bug-7247.sql

    51. bug-7326.sql

    52. archiving-old-data.sql

    53. validation-status-implementation.sql

95. Navigate to the Database\ApplicationDB\Update\From 5.0.11 to 5.0.12 sub-directory, and open the sub-directory Running Scripts.

96. Open AVEVAScripts.cmd in Notepad, and update the following values:

    • @SET "SQLCMD_ARGS=-U DB_OWNER_NAME -P DB_OWNER_PASSWORD -S DB_SERVER_NAME -d DB_NAME"

    • @SET "SQL_SCRIPT_ROOT=enter_base_path_where_SQL_scripts_listed_below_are_located"

    For example, @SET "SQL_SCRIPT_ROOT= C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.11 to 5.0.12"

97. Save the updates, and exit from the script.

98. Create a Results folder in the folder where the upgrade scripts are located. For example, C:\Program Files\AVEVA\WDA.Applications\TechInfo Manager\Application\Database\ApplicationDB\Update\From 5.0.11 to 5.0.12\Results.

99. To run the upgrade script, double-click the AVEVAScripts.cmd file.

100. Verify the Results folder for any errors.

Important Notes:

54. The SQL script archiving-old-data.sql contains two parts: database structure upgrade and data migration. The SQL script is to create new tables in the AVEVA NET Gatekeeper or AVEVA Change Manager database to store historical data of the completed Working Sets and move the data from the actively used tables such as TIM_TAG, TIM_DOC, TIM_DATASET_ATTRIBUTES, etc., to the similar tables with the names starting with the prefix "TIM_HISTORICAL_" specially designed for keeping historical data. So execution of the script may take more time than usual depending on how many Tags\Documents have been already processed by AVEVA NET Gatekeeper or AVEVA Change Manager, e.g. 40 minutes or more.

55. When the AVEVA NET Gatekeeper or AVEVA Change Manager database has been successfully upgraded, the empty table TIM_PROJECTOWNED_TAG should be available. The table is intended to store data of the Tags that have ever been processed by AVEVA NET Gatekeeper to use these data further for Parent Tag or Tar Reference validation in order to improve performance of AVEVA NET Gatekeeper (for AVEVA Change Manager, the table is always empty and not used). So, please, run the SQL script parent-tag-validation-data-update.sql against the AVEVA NET Gatekeeper database if you want to populate the table based on the data that already persists in other database tables.

56. Please, run all the database update scripts in the same order as mentioned in the file AVEVAScripts.cmd. Ensure that the SQL script validation-status-implementation.sql is running after the SQL script archiving-old-data.sql has successfully completed. Be aware that the SQL script validation-status-implementation.sql sets the validation status property of each Tag or Document existing in the database of AVEVA NET Gatekeeper or AVEVA Change Manager so, based on amount of data persisting in the database, this process may take several hours.