Hi Manu,

Yes this is "normal". In 11.2, size of Associated Labels fields have been increased to 255.
On start-up the HDS detects the db is in older format therefore it tries to update it. But if it too big it doesn't do it because it's too long.
So, you must do it manually before starting PcVue by running a sql script.
Scripts are:
BinUpgradeLogTable.sql for each log table
BinUpgradeTrendTable.sql for each trend table

I advise you backup your DB before (in case....)

Nico

And here is an extract of the Release Notes 11.2:

HDS Databases update (SPR #62324)
As documented, from now on, when upgrading a project to version 11.2, if a HDS database is
larger than 10 Gb, the HDS loading is aborted and an error message is traced.
As part of the migration process, databases' schema has to be updated using the T-SQL scripts
provided in the files binUpgradeLogTable.sql and binUpgradeTrendTable.sql before starting
PcVue and the HDS.
It was a known issue since version 11.2.05001 - The T-SQL scripts were not up to date for
upgrading to 11.2.

[Fixed] Upgrade of HDS table schema
With version 11.2, length of associated labels and event titles can be up to 255 characters long
(was 40).
This change affects the schema of HDS trend tables (column AssocLabel), and HDS log tables
(columns AssocLabel and EvtTitle).
The change in table schema is done automatically at startup if the size of the database is less
than 10 Gb.
If the size is higher, the traces ask you to run the migration script.
The issue is that the migration script, as supplied with the installation package, was not
updated to reflect this change in column size. In addition, this script may no longer be required
in a future update.
If you have an urgent need for migrating your project from an earlier version, to successfully
start the HDS shipped with version 11.2, you will need to:
• Alter the AssocLabel column of Log an Trend tables to type it nvarchar(255) (was
nvarchar(40)),
• Alter the EvtTitle column of Log tables to type it nvarchar(255) (was nvarchar(40)),
• Change the value of DBVersion and set it to 3 (was 2 for versions earlier than 11.2).
[Edit: Fixed in 11.2.06010]

By the way, you can directly update the version to the 11.2.06010 😉

You can also check in the RN11.2 if there are "Ugrades" that concern your project (just look for the keyword Upgrade)

Thanks Florent & Nico,
so i sent to the customer last night the version 11.2.0627. If I understand your comments, it means that they don't have to run any sql script to run HDS with this update?

If the database is lower than 10Go, yes, otherwise, he will have to run the scripts or alter the tables by himself:
• Alter the AssocLabel column of Log an Trend tables to type it nvarchar(255) (was
nvarchar(40)),
• Alter the EvtTitle column of Log tables to type it nvarchar(255) (was nvarchar(40)),
• Change the value of DBVersion and set it to 3 (was 2 for versions earlier than 11.2).

Hello,

Be careful, in the script in the 11.2 version there's an error in the "UpgradeLogTable.sql" script.

DECLARE @NeedsIndexRebuild BOOLEAN;
Or boolean does not exist in SQL.
New need to write this :
DECLARE @NeedsIndexRebuild BIT;

After replace IF @NeedsIndexRebuild = TRUE by IF @NeedsIndexRebuild = 1

Stephan, I assume you are talking about the 11.2.5002 but not the last one?

I still have find the error in the Version 11.2.6024.18773 - Update - 2016/09/29.

Florent,
Where can I find the last release note 11.2?

@Stephan: did you report it ?

@Manu: in the KB, section "Version Information"
https://support.pcvuesolutions.com/index.php?option=com_k2&view=item&id=827:112-releases-information&Itemid=543

Yes : SPR 62695

I did a document explaining how to use these scripts

Hello,
please find in attached file UpgradelogTable.sql(corrected as stephan recommendations) & UpgradeTrendTable.sql

Here the new UpgradeLogTable.zip
in the previous a SET was missing at the line 46

Mine didn't works?