Skip to main content
Version: v2.5

Release 2.5.14

Issues fixed​

Accept @value attribute on count file for file based staging load (ticket: 4613)
Fixed an issue where a previously valid format of the adjacent count file for a staging load file failed. Specifically, the runtime now again accepts the row count inside a @value attribute.

Valid formats are:

  • Simple number:
    • 123
  • Root format (RowCount/Count as root element):
    • <RowCount>123</RowCount>
    • <Count>123</Count>
    • <RowCount value="123" />
    • <Count value="123" />
  • Nested format (root element name is not significant):
    • <Root><RowCount>123</RowCount></Root>
    • <Root><Count>123</Count></Root>
    • <Root><RowCount value="123" /></Root>
    • <Root><Count value="123" /></Root>

Improved diagnostics on attempted creation of an invalid index (ticket: 4611)
Setup of the Source Engine or optimize of View queries intermittently attempts to create an invalid index (with no index columns). The behavior is linked to the indexes already in place on the targeted table and this makes it difficult for Hopp to identify the core issue.

The reported error in the job log is now improved in order to provide diagnostics information to assist a long term resolution.

The job log also provides a workaround to the user in the form of dropping all non-clustered IX_Mig_* indexes on the target table and restart the job.