We are pleased to announce general availability of the Teradata Developer Tools for Visual Studio 15.01.
This product may be integrated with Visual Studio 2010, 2012 or 2013 and can be downloaded from the following locations:

    English version
    Japanese version

Alternatively, you can use the Extensions and Updates item on the Tools menu in Visual Studio to download it directly from within Visual Studio.

If you are not familiar with this tool you may wish to read New Teradata Developer Tools for Visual Studio before continuing with this article.


This release of the Teradata Developer Tools for Visual Studio adds a Teradata Explorer window that allows you to explore the objects in your data source, and to perform various actions on them. It also includes an Edit Table function that allows you to directly modify the data in a table, and provides full integration with the Visual Studio Properties window.

The Teradata Explorer tool window

The Teradata Explorer displays each Data Source that you connect to. You can expand a data source to display the Databases, and optionally the Users, within that data source.
You may then drill down to see the Tables, Views, Columns, Indexes, etc. within a database.

The information in this tree structure will be saved to a local file when the application closes, and re-loaded the next time you open the tool. This makes the information available even when you are not connected to the data source. It also reduces the impact on the data source itself.
Since this tree structure acts as a cache for the Intellisense functionality you do not need to be connected to the data source in order to get Intellisense help.
It does however mean that you must manually refresh the contents of the tree after structural changes are made on the data source. This is done using the Refresh context menu on any node that may have children.

The following actions may be performed using the Teradata Explorer:

  • Display detailed information about the selected object in the Properties window.
  • Display the DDL that defines the selected object in a new Query window.
  • Rename the selected object on the data source.
  • Delete [Drop] the selected object from the data source.
  • Insert the DDL, or a Select or Insert template, into the current code window.
    The text will automatically be formatted for the language used by that code window.
  • Open a new Table Edit window to directly edit the contents of a Table. See below.
  • Re-Load [Refresh] the children of the current object.

The Edit Table window

These editor windows are created using the Edit Table context menu for any table in the Teradata Explorer.

These windows provide the following functionality:

  • Display the data in a Teradata table.
  • Add new rows to an existing table.
  • Modify the data values in existing rows.
  • Delete existing rows from a table.
  • Paste a 'table' of rows into a table. The source may be a Word Table, Excel data, or any application that provides tab delimited data in the clipboard.
  • In all cases the data entered will be validated within the application to ensure it is of the correct data type for the target column.
  • Rows that have been changed but not yet committed to the data source will display a different background color.
  • If you edit a large Text or Byte cell a multi-line textbox will be displayed in a separate dialog in order to make the text easier to read.
  • If errors occur when applying updates the error messages can be displayed by clicking on the indicated rows.

Other new features

  • An Execute as Batch command allows you to submit the entire query [or selected portion] as a single request. This causes Teradata to execute the statements in parallel. The query will fail if it contains any DDL or DCL statements.
  • Print and Print Preview commands have been added for Queries and Explain or Show output.
  • You may now toggle between a result set and a view of the SQL that created it.
  • Additional Visual Studio shortcuts are now recognized.

Fixes to earlier releases

  • Visual Studio will no longer prompt you to save changes to a Teradata Query when you start to debug your project.
  • The SPL text is now saved to the dictionary when a stored procedure is created.
  • Various improvemants have been made to the syntax highlighting and outlining functionality.
  • Call statements preceded by comments will now run correctly.
  • Invalid image data in a BLOB column no longer causes the result set to lock up.


This tool will allow you to develop the SQL required for your applications without leaving the Visual Studio environment. However it should be noted that the tool is not a replacement for SQL Assistant or Teradata Studio. These other tools still have more functionality than the Teradata Developer Tools.