The material provided is for informational purposes only, and should not be relied on in making any purchasing or investment decision. The information is not a commitment, promise or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion. © 2026 Cloud Software Group, Inc. All rights reserved
Sorry about that, Fred. I corrected the link.
Jason – I cannot log into that site. It says, no such email address exists.
Fred
Hi Kelsey and Fred,
Thanks for your feedback. We're looking at ways to improve the capabilities for supported data sources on an on-going basis. Additionally, you can see this idea to auto / self tune the capabilities rather than have the user edit the XML capabilities files:
https://ideas.tibco.com/ideas/TDV-I-6
Regards,
Jason
Kelsey - i agree. We're facing this right now as more and more, and larger, queries are added to our system and we hit the magic showplan button. Lo and behold, basic fundamental functions like TO_CHAR and MAX aren't being pushed down to Oracle or SQL Server. A few hours spend manually editing the clumsy XML capabilities files has improved performance immensely. The help I received from Anil in support was timely, professional, and clear. But I'd still like #1) much improved capabilities files for the most commercially used databases worldwide, and #2) maybe an interface thru Studio for maintaining and enhancing capabilities files.
It is super annoying to later find that the function you used wasn't supported in the source and is therefore causing the query to execute in TDV (slower) and not in the source. You realize this only after looking through the plan, which most users don't dig through.