Table of Contents

• Preface
  • Scope
  • Who Should Use This Document
• Outline of the Migration Process
• Before Installing a New Version of the Denodo Platform
• Export the Metadata of the Current Installation
• Modify the Virtual DataPort Metadata
• Import the Metadata to the New Installation
• After Importing the Metadata Into the New Installation
• Test the New Denodo Platform Installation
• Backward Compatibility
  • Changes in the Denodo Platform 6.0
    • Changes Common to All the Modules
      • Logging: Clearer Format for Dates
    • Virtual DataPort
      • Changes in VQL Syntax
      • Changes in VQL Statements
        • CREATE DATASOURCE JDBC
        • LIST FUNCTIONS CUSTOM
      • Dependencies to Develop Custom Elements (Functions, Wrappers…)
      • Importing Roles from an LDAP Server
      • JDBC Data Sources
        • Access to Teradata
        • Delegate SQL Sentence as Subquery
      • JDBC Driver
        • Location of the JDBC Driver
        • Metadata Returned by the JDBC driver
        • JDBC Driver Compiled with Java 7
      • JMX
      • Memory Usage Options
      • ODBC Driver
        • New Denodo ODBC Driver
        • Date Values with Millisecond Precision
      • REST Web Services No Longer Return the HTTP Code 204 by Default
      • Stored Procedures
      • User Privileges
      • Version Control System Integration (VCS)
      • Windows Services
      • Features Deprecated in Denodo 6.0
        • VQL Syntax
        • Internal Pool of Connections of the JDBC Driver
        • Published Web Services: “with LDAP” Authentication
        • SQLFRAGMENT clause
        • Stored Procedures API: getNumOfAffectedRows Method
        • Custom Wrappers API: deprecated methods
        • XMLA Connectors for SAP
        • JDBC Data Source Dialog: Choose Automatically
        • ODBC Interface
      • Features Removed in Denodo 6.0
        • Enumerated and Money Types
        • Generic SOAP Web Service Interface
        • Server Administration Mode
    • Scheduler
      • Counters for the Number of Documents and Errors Are Stored in a Long
    • Embedded Web Container
      • Location of the Log4j Configuration File
      • Changes in the Default Configuration of the Logging System
      • Configuration Changes
  • Changes in the Denodo Platform 5.5
    • Cache
      • Default Fetch Size
    • CAST Function
    • Reserved Words
    • Prohibit Incompatible Source Type Properties
    • Three-valued Logic
    • Features Removed in Denodo 5.5
      • OpenAjax Widgets
  • Changes in the Denodo Platform 5.0
    • Case-Sensitivity of Elements
    • Comparison of Strings
    • Dependencies Between Elements
    • Exporting to a Repository of Files
    • JMS Listeners
    • Web Services Published By Denodo
    • Stored Procedures
    • Features Deprecated in Denodo 5.0