To enable Authorized Data Truncation (ADT) for the client session:
Since OpenEdge 11.5.1, the Authorized Data Truncation (ADT)
feature can be enabled or disabled for a specific client session via ODBC or JDBC in the connection URL with truncateTooLarge
1. For ODBC:
- The parameter is connection specific and is remembered by SQL only during the connection session.
- truncateTooLarge=off (data will not be truncated and an error is returned)
- truncateTooLarge=on (truncates data exceeding the column size)
- truncateTooLarge=output (truncates only the data returned to the user when its size exceeds the column size)
ODBC Data Source Administrator tool : DNS
> Advanced > Extended Options: " truncateTooLarge=on " (This is case sensitive)
2. For JDBC
On Unix, under the respective ODBC DSN in the odbc.ini file:
Add the truncateTooLarge
parameter to the connection string:
sqlexp -url "jdbc:datadirect:openedge://<IPAddress>:<port>;databasename=<dbname>;truncateTooLarge=output;"
ADT truncateTooLarge Parameter in Connection URL and Autonomous Schema Update (ASU)
In OpenEdge 11.6, the Autonomous Schema Update (ASU) feature can only be enabled by specifying the -SQLWidthUpdate database startup parameter when the Login Broker starts for client connections to the related SQL Server, not for client sessions specifically. For further information refer to Article:
- When the ASU -SQLWidthUpdate startup parameter is turned ON, ADT (-SQLTruncateTooLarge) is also enabled.
- The truncateTooLarge parameter in connection URL overrides the ADT server startup parameter (-SQLTruncateTooLarge).
- For example, If the value of the -SQLWidthUpdate parameter is set to ON when the Database Login Broker was started, when a user connects with truncateTooLarge=off in connection URL, then ADT will be turned off for this connection. While ASU will be enabled on the SQL Server, ASU is indirectly turned off for this particular connection because there will be no data truncation event (ADT) for the schema update feature to use.