We are pleased to announce general availability of the Teradata Developer Tools for Visual Studio.
This product may be integrated with Visual Studio 2010 or 2012 and can be downloaded from the following locations:
Alternatively, you can use the Manage Extensions item on the Tools menu in Visual Studio to download it directly from within Visual Studio.
The initial release of the Teradata Developer Tools for Visual Studio contains a Teradata Query tool. This extension allows you to open custom Editor windows that can be used to compose SQL queries for the Teradata Database and execute those queries using the .NET Data Provider for Teradata.
It also provides a History window to record, and reuse, the queries that you execute. The history data is stored in an SQLServerCE database that is stored locally on your system.
The following image shows an example of the tool within Visual Studio:
The information stored in the History file is the same as that stored by SQL Assistant.
SQL Assistant stores its history in a Microsoft Access database: SQLHistory.mdb
The Teradata Developer Tool stores its history in a SQLServerCE database: SQLHistory.sdf
If you would like to use your existing history from SQL Assistant you can download the attached HistoryConverter tool. Simply unzip the file into a directory of your choice. Note that it assumes that you have all the required pre-requisites. If you have both SQL Assistant and the Teradata Developer Tools for Visual Studio installed then you will already have those pre-requisites.
This tool will allow you to perform any of the following functions:
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 have far more functionality than the Teradata Developer Tools.
Can we anticipate any of these features in future releases of SQL Assistant? Especially the Outlining and SQLServerCE history file.
Note for using LOCK or LOCKING keyword.
These words will not be recognized as Keywords if they start at the beginning of the Query. To fix this just add whitespace or a comment before the keywords.
In addition the output messages for a LOCK statement will say '? completed' rather than 'LOCK completed'.
I will fix this in the next release but if you want to fix it before that you can do so by simply editing the teradata.lng file.
Simply move the 2 words 'LOCK LOCKING' from the section headed TokenKey="Keywords" to the section headed TokenKey="MainKeywords".
On Windows 7, with VS2010, the file will be in:
\ProgramData\Microsoft\VisualStudio\10.0\Extensions\Teradata Corporation\Teradata Developer Tools\14.11
Yes. SQL Assistant 15.0 will use the same editor that is used in this tool. As a result you will get Outlining, Quick Info tool tips, and more extensive Intellisense, amoungst other things.
It will however continue to use Microsoft Access for its History file since we need Access in order to be able to export to Access. (Not many users have SQLServerCE so exporting to that is not very useful.)