Le fasature di import falliscono con un errore di Cannot resolve the collation conflict between "SQL Latin1 General CP850 CI AS" and "Latin1 General CI AS" in the equal to operation.: Difference between revisions

From RVM Wiki
Jump to navigation Jump to search
Created page with "Se in Import una fasatura non aggiorna i dati, e nel log si trova un errore tipo: <pre> 20201104 13:26:22 - Errori durante fasatura ARRICCHIMENTO CEDOLINI EMAIL 20201104 13:2..."
 
mNo edit summary
 
Line 39: Line 39:
GO
GO
</pre>
</pre>
* Oppure usare
COLLATE DATABASE_DEFAULT

Latest revision as of 12:07, 15 March 2021

Se in Import una fasatura non aggiorna i dati, e nel log si trova un errore tipo:

20201104 13:26:22 - Errori durante fasatura ARRICCHIMENTO CEDOLINI EMAIL
20201104 13:26:22 ----------------------------------------------------------------------------
20201104 13:27:28 - Fasatura [C] ARRICCHIMENTO CEDOLINI EMAIL
20201104 13:27:28 - UPDATE A1010 SET F1016=L1.Email FROM ANAGRAFICA_CEDOLINI_CU L1 ,TDOC  WHERE A1010.F1008=L1.CF AND
TDOC.FIDD=A1010.FIDD AND FENA=-1 AND FLAF=1 
20201104 13:27:28 - Cannot resolve the collation conflict between "SQL_Latin1_General_CP850_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.
20201104 13:27:28 - Errori durante fasatura ARRICCHIMENTO CEDOLINI EMAIL
20201104 13:27:28 -
----------------------------------------------------------------------------------------------

Bisogna forzare la collation sui campi indice della vista usata dalla fasatura, ad esempio:

ALTER view [dbo].[ANAGRAFICA_CEDOLINI_CU] AS

select distinct
   cardname AS Nome_Cognome
 , e_mail as Email
 , AddID collate Latin1_General_CI_AS as CF
 
from [10.48.149.4].[SBOFPM].[dbo].[ocrd]
where 
	AddID is not null

union all

select distinct 
   concat(firstName,' ', lastName) As Nome_Cognome
 , email as Email
 , govID collate Latin1_General_CI_AS as CF

from [10.48.149.4].[SBOFPM].[dbo].[ohem]
where
	govID is not null
GO


  • Oppure usare
COLLATE DATABASE_DEFAULT