3.1.5.44 proc_GetVersion
The proc_GetVersion stored procedure is invoked to get the component version number string associated with the specified version identifier GUID (using the format major.minor.phase.build; for example, 3.0.106.0).
-
PROCEDURE proc_GetVersion( @VersionId uniqueidentifier, @Version nvarchar(64) OUTPUT );
@VersionId: The version identifier of the component version number to retrieve.
@Version: An output parameter containing the component version number string matching the specified version identifier. This value MUST be unchanged from the input value if the specified @VersionId value does not have a matching component version number.
Return Values: The proc_GetVersion stored procedure returns an integer return code which MUST be listed in the following table.
Value |
Description |
---|---|
0 |
Successful execution. |
The front-end web server can define one or more version numbers. Each of the version numbers is identified by a Version ID. When a database is created by the front-end web server on the back-end database server, the front-end web server stores the version numbers with different version identifiers in the Versions table (section 2.2.7.11). When the front-end web server connects to a back-end database server, the front-end web server SHOULD retrieve the Version IDs using stored procedure proc_GetVersion<15> and make sure the versions are within an acceptable range defined by the front-end web server; otherwise, the front-end web server MUST refuse to connect to the back-end database server.
The version identifiers and the acceptable version numbers for this protocol used when communicating with a content database are listed in the following table.
Version Id GUID |
Acceptable version range |
---|---|
"00000000-0000-0000-0000-000000000000" |
14.0.4006.1010 - 14.0.4006.9999 |
"6333368D-85F0-4EF5-8241-5252B12B2E50" |
4.0.116.0 - 4.0.116.0 |
"1A707EF5-45B2-4235-9327-021E5F9B8BB0" |
4.0.6.0 - 4.0.6.0 |
"25EB5CEE-15BD-4954-BD4E-2624D5878D8C" |
14.0.4006.1010 - 14.0.4006.9999 |
When the protocol is used to communicate with a configuration database, the list of version ids used are the following.
Version Id GUID |
Acceptable version range |
---|---|
"00000000-0000-0000-0000-000000000000" |
14.0.4006.1010 - 14.0.4006.9999 |
"F4D348C4-A6E9-4ED5-BDB2-2358B74EF902" |
4.0.116.0 - 4.0.116.0 |
"60B1F2BE-5130-45AB-AF1D-EDD34E626B5D" |
4.0.6.0 - 4.0.6.0 |
The acceptable version numbers specified in the preceding tables can change when the front-end web server is updated. As a result, the updated front-end web server might not be able to communicate with the back-end database server. In order to re-enable front-end web server to back-end database server communication, the front-end web server MUST use an upgrade process to modify any data structure on the back end database server to accommodate any changes which might have occurred to this protocol, and to update the version numbers to match the new acceptable version numbers. Upgrade logic is implementation specific.
The proc_GetVersion stored procedure MUST NOT return any result sets.