Vantage Editor is a lightweight SQL editor intended for doing common business tasks, ad hoc data discovery/analysis that is fully supported by Teradata.

• Query Editor (built on the open-source Monaco Editor), with SQL syntax highlight and error handling 

• Database Explorer Tree to view and browse Database 

• Result Set for viewing and managing query results 

• Basic data load and export   

• Connection Manager for managing Vantage connections  

• Query History of submitted SQL statements  

Vantage Editor will NOT provide feature parity with SQL assistant/Studio. Based on customer feedback and user research, it will provide the most critical functionalities that are required for providing an optimal SQL editor.   

For users that require more advanced IDEs (integrated development environments) for SQL development to complement their Vantage Editor experience, they can explore incremental integrations from open ecosystem tools and products from 3rd party partners such as the listed below:  

• Teradata integrations open ecosystem tools: Vantage Modules for Jupyter, VS Code SQL Tools Extensions, Visual Studio Tools  

• 3rd Party Teradata Partners: VSCode, DBeaver, Toad, Razor  

As part of our move-forward strategy and being competitive in the market, Teradata will continue to expand partnerships to provide modern tools for increased flexibility.

Other open ecosystem and 3rd party tools exist in the marketplace that have been proven to work with Vantage and used by users but are neither provided nor supported by Teradata.

Customers have multiple options for accessing Vantage Editor  

• Browser: Deployed and managed by the Teradata through Vantage Console. Available for VantageCloud Enterprise and VantageCloud Lake 

• Desktop: A downloadable install that will be available from Teradata Downloads once the product is GA. Available for VantageCore, VantageCloud Enterprise and VantageCloud Lake customers.  Please reach out if you want access to the current beta version. 

• Customers can deploy the desktop editor on any environment of their choice. As of now, we are not aware of any limitations that would prevent running on VMs or Citrix. 

As many of our customers transition to the cloud, we know they will live in a Hybrid environment and want to provide a unified customer experience across all our platforms (VantageCloud and VantageCore).   

Some of the reasons why customers / users may prefer or require a desktop Vantage Editor:  

• Need to connect to a Teradata on-premises Vantage Core system.  

• Prefer to connect directly from their computer to Vantage, meaning they prefer dedicated desktop apps in general — Navigating browser tabs gets messy real fast. Nobody needs yet another tab that’s somehow impossible to find when you need it.  

• As of today, Teradata still has thousands of customers connecting to their systems through SQL Assistant, which is a desktop application. This tells us that this is still a trend among our users. 

No. At this moment the Web versions of Vantage Editor will only be accessible through Vantage Console from VantageCloud.

Vantage Editor is one product that can be accessed through different channels (Web, Desktop). Our goal is to provide the same unified experience. This means that the key major capabilities of the SQL Editor product will be available, with only small differences that are applicable to the specific access method.  

Note: In the initial releases of desktop Vantage Editor there may differences in the product, but we will converge these as part of our product roadmap.

No. Customers that require connectivity to other sources can explore the following options:  

• Integration with external data sources through core Vantage capabilities such as QueryGrid, NOS.  

• 3rd party tools that provide universal access such as DBeaver.  

No. Vantage Editor will only support 17.10 and forward Vantage SQL Engine versions. Previous versions may work but will not be officially supported.

No. Desktop Vantage Editor is built on the very popular cross-platform Electron framework for creating native applications from web technologies. The other frameworks are Monaco (editor), Covalent and Angular JS. The installer will bundle all required components.  

Desktop Vantage Editor will be available for major Windows and Mac (Intel & ARM) distributions.   

The VantageCloud Lake editor uses the Query Service (REST API) and the Desktop Editor uses the Teradata node.js driver.

No, desktop Vantage Editor will only be available as a separate install.

No, desktop Vantage Editor is a product with an ongoing evolving product roadmap that will be focused on improving the core capabilities of a modern light SQL editor.

Due to architectural differences, some variance in performance depends on the use case. Given performance is a crucial factor for SQL editors, we will continue to monitor and improve as part of our product roadmap.  

Dependent on the use case, other tools may be better suited for maximizing performance/throughput. For example, for automating bulk loading leverage TPT.  

Teradata Studio is currently supported with no new feature development. As part of the General Availability of Vantage Editor in 2024, Teradata Studio is targeted to be end of life in 2024. An official communication and timelines (9-12months notice) for Teradata Studio end of life will be formally announced.

Customers and users are encouraged to start to plan transition to Vantage Editor, or a 3rd party tool offering. 

Teradata will be providing EDM support 16.20 SQL assistant for special cases only. This is planned until 6 months past the Desktop Vantage Editor GA. Extended SQL assistant support with SQLE 17.10 will continue to be as is for EDM:  

• SQL Assistant 16.20 will work with DB 17.10, though it will not be able to take advantage of any new DB features introduced after 16.20. For example:  

• Cannot configure Federated Authorization  

• Syntax highlighting of keywords/restricted words since (note there is only one in 17.10)  

• Cannot configure TLS or JWT with .NET data provider  

• EDM support will be for only for P1 incidents, i.e. those causing production stoppage and have no workaround.  

• SQL Assistant 16.20 will work with DB 17.20 by installing both TTU 16.20 & 17.10 without erasing previous versions. Although this setup will only be supported for P1 cases, on business hours and as best effort. 

If you are a SQL Assistant user, we recommend that you don’t migrate to Teradata Studio. Instead, we request you to wait on the Desktop Vantage Editor GA release and migrate directly to Desktop Vantage Editor. To make direct transition from SQL Assistant to Desktop Vantage Editor possible, we have extended support for SQL Assistant until 6 months past the Desktop Vantage Editor GA release. Alternatively, you can also consider 3rd party IDEs that we have partnered with - Razor, Dbeaver / Cloudbeaver, and Toad.

If you’re already in the process of migrating from SQL Assistant to Teradata Studio, we’d like to remind you that Teradata Studio will be nearing end of life by Dec 31, 2024 and you will be required to migrate again to Desktop Vantage Editor in 2024.

Currently, LDAP and TD2 are supported mechanisms on Vantage Editor. TD2 is the default Teradata Logon mechanism. Federated SSO will be part of future release.

The in-DB function explorer, is available in the Web editor to provide easy discovery and execution of the in-DB functions. It is currently not part of the desktop editor for GA - < is this being considered>. However, users can still execute the in-DB functions in the desktop editor by creating their queries with these functions manually. Users need to find such syntax in places such as Teradata docs.

We are looking at these, and interview-based research is underway to include them in the future release.