locked
Azure Data Factory - Azure SSISDB - Collation Error RRS feed

  • Question

  • We have SQL Managed Instance: Collation is set to Latin1_General_CI_AS

    When Azure SSIS is creating SSIDB it takes default collation: SQL_Latin1_General_CP1_CI_AS

    So when we try to deploy to SSIDB it gives collation conflict error.

    Has anybody else faced this problem?


    VJ

    Thursday, March 14, 2019 1:05 PM

Answers

All replies

  • Hello Vishal,

    After the SSISDB is created, can you please try to change the collation

    USE master;  
    GO  
    ALTER DATABASE SSISDB
    COLLATE Latin1_General_CI_AS ;  
    GO  
    
    -- Check if the Changes are successful
    SELECT name, collation_name  
    FROM sys.databases  
    WHERE name = N'SSISDB';  
    GO  

    Also, is there a specific reason your MI is created with Latin1_General_CI_AS as the collation?

    Friday, March 22, 2019 10:57 AM
  • Hi,

    I had tried this and the collation for ssisdb does change.

    However, still the collation error did not go when i tried creating a folder.

    I got the same collation error.

    Also, as per microsoft forums even if ssidb collation is different between ssis db and sql server it should not be problem.

    Thanks!

    Vishal


    VJ

    Friday, March 22, 2019 11:50 AM
  • Could you please post the complete error to help us troubleshoot better.
    Sunday, March 24, 2019 8:19 AM
  • Steps for reproducing error:

    1. Create a new SQL managed instance – Collation Latin1_General_CI_AS 
    2. Create Data Factory.
    3. Create Azure SSIS with SSIDB deployed on the SQL Server created in step 1.
    4. Right Click Azure SSIS Catalog and try to create folder.
    5. Error Displayed: "Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.


    VJ

    Wednesday, March 27, 2019 12:12 PM
  • Hi,

    I am talking to microsoft and they confirm this is a bug and will be fixed in 2 weeks time!

    Regards,

    Vishal


    VJ

    Thursday, March 28, 2019 1:06 PM
  • Hi VJ,

    Thanks for the update, which might be beneficial to other community members reading this thread. 

    Tuesday, April 23, 2019 6:47 AM