Advanced ETL Processor 6.5.3.0 is now available. This release improves SQL Server connectivity, speeds up ODBC and SQL Server data transformation and import work, and fixes memory leaks. Connection handling and memory management are not glamorous, but neither is a failed overnight job at 2:13 a.m. That one really does not go according to schema.
What is new in Advanced ETL Processor 6.5.3.0
- Improved: SQL Server connectivity, particularly Windows Authentication, SQL Server Authentication, Microsoft Entra Service Principal, Microsoft Entra Managed Identity, Microsoft Entra Default, and Microsoft Entra Password.
- Improved: Minor data transformation and import performance improvement for ODBC and SQL Server.
- Fixed: Memory leaks.
SQL Server authentication support is broader
Version 6.5.3.0 improves SQL Server connectivity for both traditional and Microsoft Entra authentication methods. That includes Windows Authentication and SQL Server Authentication, plus Service Principal, Managed Identity, Default, and Password options for environments managed through Microsoft identity services.
This matters when ETL workflows connect to newer SQL Server, Azure SQL, or identity-managed database environments. If the connection layer behaves correctly, the rest of the workflow has a much better chance of staying boring. Boring is good in production.
ODBC and SQL Server imports get a small performance improvement
This release also includes minor data transformation and import performance improvements for ODBC and SQL Server. Small performance gains are useful because ETL jobs often run repeatedly: every hour, every night, or whenever someone exports yet another file called final_final_really_final.xlsx.
Do not expect this update to turn a badly designed query into a rocket ship. If the source SQL is slow or the network is struggling, fix that first. But for normal ODBC and SQL Server workflows, the update should make the processing path a little cleaner.
Memory leaks have been fixed
The release fixes memory leaks found during recent testing and support work. That is especially relevant for longer-running ETL processes, scheduled jobs, and repeated imports where small leaks can become large problems over time.
If your current setup runs SQL Server or ODBC jobs for long periods, this is a sensible update. If your installation is small, stable, and not using these connection types, there is no need to treat the update like a fire drill.
Upgrade when you use SQL Server, ODBC, or Microsoft Entra authentication
Upgrade to Advanced ETL Processor 6.5.3.0 if your workflows use SQL Server, ODBC, or Microsoft Entra authentication. It is also worth installing if you run scheduled jobs for long periods and want the latest memory-leak fixes.
See the Advanced ETL Processor Enterprise product page, review the Enterprise version history, or download the fully functional 30-day trial.