Cognos Analytics

 View Only
  • 1.  Joins with data from Azure SQL database not always working

    Posted Thu November 17, 2022 10:32 AM
    Hi
    We are migrating our databases from Netezza to Azure SQL databases. Certain reports now behave differently in joining queries. In one particular case, we are joining on blood group and the join works for negative blood groups (A-, B-, O-, AB-) but not for positive blood groups (A+, B+, O+, AB+). Does anyone know if the plus-sign could behave differently in Cognos when sourcing from these databases? Of course we can implement a work around but to avoid this in future developments, we want to know the cause.
    Thanks

    ------------------------------
    Ester D'Hoe
    ------------------------------

    #CognosAnalyticswithWatson


  • 2.  RE: Joins with data from Azure SQL database not always working

    IBM Champion
    Posted Fri November 18, 2022 04:22 AM
    Hi Ester,

    I believe you need to create a blood group key such as :
    Blood_KeyBlood_Group
    1 A-
    2 B-
    3 O-
    4 AB-
    5 A+
    6 B+
    7 O+
    8 AB+

    Then you would create the join with Blood_Key instead of Blood_Group.

    Best regards,


    ------------------------------
    Patrick Neveu
    Positive Thinking Company
    ------------------------------



  • 3.  RE: Joins with data from Azure SQL database not always working

    Posted Fri November 18, 2022 04:31 AM
    Hi Patrick

    Thank you for the fast reply! Yes, this is the work around we implemented, but do you happen to know why the original join worked with Netezza databases but not anymore with Azure SQL databases?

    Many thanks, Ester

    ------------------------------
    Ester D'Hoe
    ------------------------------



  • 4.  RE: Joins with data from Azure SQL database not always working

    Posted Fri November 18, 2022 11:16 AM
    Hi Ester,

    If you take a copy of the SQL out of Cognos and put it in a SQL tool, does it do the same thing? Cognos wouldn't know what the row data is before it sends off the query to Azure, it wouldn't modify it based on there being - or + in the rows.

    My suspicion is that the dataset returned to Cognos is where the issue resides.

    ------------------------------
    TREVOR COMEAU
    ------------------------------