I haven't noticed any bugs in the functionality provided with this so far. I would like to have the ability to see what database I'm connected on on each tab. I'd also like to be able to format any sql snippets I copy and paste into the edit window. I really like the auto complete function and look forward to the next version of this extension.
I assume you are referring to View columns in the Teradata Explorer.
Unfortunately Teradata does not store the column information for views.
Applications like SQL Assistant have to add that information through use of Help Column commands which are extremely slow when updating large numbers of objects.
This tool is designed to provide a very fast implementation of the Teradata Explorer and as a result it can not add this information.
There will be an alternate way to obtain the information starting in Teradata 16.0 but I suspect it would still probably increase the data retrieval time by a factor of 10, so we may still not be able to display the column types for views.
Column types are of course displayed for tables.
I think the 2013 Community edition is equivalent to the old 2010 'Express' editions.
I have not tried this but you may be able to get the current version to work by slightly modifying a file.
Download the install file (*.vsix)
This is really just a zip file so open it in your favorite ZIP app and extract the file "extension.manifest".
Finally put the file back into the zip container, close it, and execute it.
(It will probably complain that the digital signature is invalid since you changed something but I think it should still run.)
I'm not certain that the comunity version has all the required support libraries but since the Integrated shell version does I would think it will.
Another possible issue is if it expects 'Community' or 'Community_All' or some such string rather than 'Express_All' when added to the 2012 or 2013 nodes. (I don't think so though since they completely changed the format of this file for 2012 and the onld one still works.)
Let me know if it works...
The way VS works is that each editor extension registers a file type (or types) that it handles.
Microsoft has already grabbed 'sql' so I had to register 'tdsql'.
If you never use SQL Server and you want to use sql rather than tdsql you can play with the registry a bit.
In the following key, change the string value 'tdsql' to 'sql, leaving everything else the same:
(or you could just add an 'sql' string value that copies the 'tdsql' value)
Either remove the following keys completely, or change the 'sql' string value in their Extensions key to 'mssql' or something similar:
All the above keys are for Visual studio 2010.
If you use VS2012 change '10.0_Config' to '11.0_Config', etc.
NOTE - I have NOT tested this ... but I think it will work.
Getting the following error...
Microsoft Visual Studio
The 'Teradata.Client.VS.Query.TdQueryEditorPackage, Teradata.Client.Query, Version=188.8.131.52, Culture=neutral, PublicKeyToken=76b417ee2e04956c' package did not load correctly.
The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by running the application together with the /log parameter on the command line, and then examining the file 'C:\Users\sbedwel\AppData\Roaming\Microsoft\VisualStudio\10.0\ActivityLog.xml'.
In the log, it says "Could not load file or assembly 'ActiproSoftware.Shared.WinForms, Version=13.1.310.0, Culture=neutral, PublicKeyToken=c27e062d3c1a4763' or one of its dependencies. The system cannot find the file specified."
Any ideas to get past this?
The vsix file (really just a zip file) should contain the following files:
It sounds like at least one of them was either corrupted or not extracted when VS installed the extension.
Hopefully you can manually extract these files and place them into the directory where the extension is installed.
Alternatively you could try uninstalling the extension, then re-installing the vsix file. (assuming you have the file on your system)
If you installed it directly though VS gallery and don't have the actual vsix file on your system you would have to uninstall and then reinstall from the gallery.
In 15.0 you will be able to collapse entire statements - including the separate parts of a Union/Intersect - as well as the derived tables, case statements, Begin/end blocks, procedural blocks and multiline comments that you can currently collapse.
The idea of user defined regions does not fit well with SQL since the parts that need to be collapsed often dont start/end at the beginning or end of a line. (and starting/ending regions in the middle of a line would be a parsing nighmare)