DWHPRO TITHONIZER: UTF-8 source correction, 24 October 2026

This is the historical procedure with seven hexadecimal newline expressions
replaced by CHR(10). It is UTF-8 text. This change fixes the compilation issue
observed in the documented test setup; it is not a new optimization algorithm.

Follow the original installation document, including G00_SP_LOG_TEMP,
prerequisite volatile tables, procedure compilation permissions, source SELECT
permissions and the documented cleanup before CALL:
https://www.dwhpro.com/wp-content/uploads/2015/05/SP_DWHPRO_TIHONIZER_DOCU.pdf

Compile in a dedicated test environment before adapting to your databases.
Do not execute it in an arbitrary current database. Review the procedure and
its generated SQL, object names and privileges before use.

Verification scope: Teradata Database 20.00.28.81, UTF-8 BTEQ session.
The corrected procedure compiled. A CALL against 10,000 synthetic rows
returned compression candidates for two columns. The test did not establish
globally optimal compression, production safety, or historical performance
and storage savings. This tool uses a greedy candidate-selection heuristic.
