Planning Analytics

Expand all | Collapse all

SQL Server 2017 Compatibility Levels supported in Planning Analytics 2.07

  • 1.  SQL Server 2017 Compatibility Levels supported in Planning Analytics 2.07

    Posted Wed June 12, 2019 11:01 AM
    Hi All,

    Can you please tell what are SQL Server 2017 Compatibility Levels supported in Planning Analytics 2.07?
    As of now we have PA 2.02 and 2014 SQL Server with compatibility level 120.

    For Ex :  SQL Server 2017 ( Database Version 14.x)
    Available Compatibility Level Values in SQL Server : 140, 130, 120, 110, 100

    Lets Say you have a Database called Operational in SQL Server 2014 or 2016 or 2017.
    When you right click on the Operational Database , you will get the properties window , there you can check  "options ". In Options we do set the compatibility level. 
    As of now IBM PA supported 120 only but there are some performance issues because of this low level in SQL server 2017 Databse issues.

    If we set compatibility level 140  , Database has good performance but Planning Analytics has limitations .
    as of now we have PA 2.04.

    If we upgrade to PA 2.07 , can we set  Compatibility Level 140?

    It would be great  if we have quick response.


    Please find the attached image for how we set for any Database Compatibility level.

    6fQEqeOURLgtNV43Az6k_Does-SQL-Server-Database-Compatibility-Level-Matter-Compatibility-Level.jpg


    Thanks,
    Srinivas




    ------------------------------
    Srinivas
    Sr. BI & Planning Analyst / ETL Architect
    ------------------------------


  • 2.  RE: SQL Server 2017 Compatibility Levels supported in Planning Analytics 2.07

    Posted Thu June 13, 2019 02:20 AM
    There is nothing that I am aware of in PA Local that restricts what version of sql server you are using. As long as you have the correct ODBC drivers all should work okay. 

    If you're accessing the database via secure gateway you have to work with IBM to make the drivers available on the cloud.

    ------------------------------
    Ryan Clapp
    ------------------------------



  • 3.  RE: SQL Server 2017 Compatibility Levels supported in Planning Analytics 2.07

    Posted Thu June 13, 2019 05:59 AM
    Hi Srinivas,

    Following are requirements which you would need to have in place and follow.

    This is our Supported Environment for Planning Analytics.
    https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/prereqsForProduct?deliverableId=1413345793248

    The other notification which was recently released was this following one which discusses the incompatibility with a windows patch that enforces TLS 1.2 for all odbc connections.
    https://www-01.ibm.com/support/docview.wss?uid=ibm10742287 

    Kind Regards,

    ------------------------------
    Robert VAUTOUR
    ------------------------------



  • 4.  RE: SQL Server 2017 Compatibility Levels supported in Planning Analytics 2.07

    Posted Fri June 14, 2019 12:36 PM
    Thank you Ryan , Robert and Stuart for your great suggestions. we will consider and follow all these suggestions while we upgrading PA to 2.07 version .
    At present we have SQL 2017 and PA 2.0.4 .We tried these all suggested options but PA throwing an error by saying "Database Compatibility ( 140 )  Does not support "  , so we switched to 120 and then its connected without an error.

    Hi Stuart ,
    one request , since you have SQL Server 2017 ,If possible and appropriate  could you please check with SQL Server team ,what compatibility level they set on SQL Server DB which PA   is connecting to get the Data.

    Once again  thank you for response.

    Thank you ,
    Srinivas

    ------------------------------
    Sree K
    Sr. BI & Planning Analyst / ETL Architect
    ------------------------------



  • 5.  RE: SQL Server 2017 Compatibility Levels supported in Planning Analytics 2.07

    Posted Thu June 13, 2019 06:41 AM
    Hi Srinivas,

    We recently updated the supported environments page for Planning Analytics 2.0.7 to list support for Microsoft SQL Server 2016, Microsoft SQL Server 2017, and all versions of Oracle 12.  To see the report go here https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html and search for Planning Analytics Local.

    The supported environments page reflects what our QC and engineering teams test.   Although we only tested 2.0.7 with SQL Server 2017, I would not expect problems using it with lower versions of Planning Analytics.

    I recommend looking at version 2.0.7 or the upcoming 2.0.8 release as a potential upgrade.  There has been lots of quality improvements and important features added since 2.0.2.

    ------------------------------
    Stuart King
    IBM Planning Analytics Offering Manager
    ------------------------------



  • 6.  RE: SQL Server 2017 Compatibility Levels supported in Planning Analytics 2.07

    Posted Fri June 14, 2019 12:34 PM
    Hello Srinivas,

    Could you mention how you communicate with the SQL server database ?
    I don't think there is any limitations in PA with SQL comparability level

    Do you have any errors when you change the comparability? Which driver you are using to connect to the SqL server instance?

    ------------------------------
    Muhammad Eissa
    ------------------------------



  • 7.  RE: SQL Server 2017 Compatibility Levels supported in Planning Analytics 2.07

    Posted Fri June 14, 2019 12:40 PM
    Hi Muhammad ,
    We are connecting through ODBC ( 64 Bit) using SQL Server Native Client 11.0 driver.

    Thank you ,
    Srinivas


    ------------------------------
    Sree K
    Sr. BI & Planning Analyst / ETL Architect
    ------------------------------



  • 8.  RE: SQL Server 2017 Compatibility Levels supported in Planning Analytics 2.07

    Posted Sat June 15, 2019 02:47 PM
    Hi Srinivas,

    Please try to use SQL ODBC driver version 17, you can find it here:
    https://www.microsoft.com/en-us/download/details.aspx?id=56567

    I think the issue between the driver and the SQL server itself.
    If the error still exists it will be more helpful if you send the error detailed message from the log file with the error number.

    Regards,

    ------------------------------
    Muhammad Eissa
    ------------------------------