After switching to a new MSSQL database for data offload, this error was observed while offloading to the 'alarm_property' table only. Other offloads are ok.
- Does offloading require a certain collation ?
- How can this error be resolved ?
NonQuery 'BULK INSERT alarm_property_temp FROM
'\\SERVERNAME\Offload\alarm_property\current2021_02_17_19_53_42_7556_35642.dat' WITH (DATAFILETYPE='widechar', FIELDTERMINATOR = '\t');MERGE alarm_property AS TargetTable
USING alarm_property_temp AS SourceTable
ON(TargetTable.[AlarmId] = SourceTable.[AlarmId] AND TargetTable.[DmaId] = SourceTable.[DmaId] AND TargetTable.[Name] = SourceTable.[Name] AND TargetTable.[Type] = SourceTable.[Type] AND TargetTable.[OwnerId] = SourceTable.[OwnerId])
WHEN NOT MATCHED BY TARGETTHEN INSERT ([AlarmId],[DmaId],[Name],[Type],[OwnerId],[Value],[Sequence])
VALUES(SourceTable.[AlarmId],SourceTable.[DmaId],SourceTable.[Name],SourceTable.[Type],SourceTable.[OwnerId],SourceTable.[Value],SourceTable.[Sequence])
WHEN MATCHED
THEN UPDATE SET
TargetTable.[Value] = SourceTable.[Value],TargetTable.[Sequence] = SourceTable.[Sequence];
DROP TABLE alarm_property_temp;
' failed. (code = 468, message = Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.)
Hi,
By default we use collation "Latin1_General_CP1_CI_AS" in the MSSQL central Database.
You can either recreate the central database with that collation, or you can configure dataminer to use another one (see DataMiner Help ).
Correction, SQL_Latin1_General_CP1_CI_AS is the default.