60 | 08 Feb 2011 @ 09:41 PST | Tools | SQL Assistant Java Edition 13.10 available | @strattok,
Thank you for clearing this up. |
59 | 08 Feb 2011 @ 09:39 PST | Tools | SQL Assistant Java Edition 13.10 available | @kerpal,
Can you be more specific? Are you in the SQL Editor view? |
58 | 28 Jan 2011 @ 09:09 PST | Tools | SQL Assistant Java Edition 13.0 available | First make sure you are running our latest version of SQLA JE, version 13.10. Refer to the Download link for SQL Assistant Java Edition 13.10. This version contains an enhanced Result Set Viewer th... |
57 | 12 Jan 2011 @ 08:35 PST | Tools | SQL Assistant Java Edition | We are currently planning our next release for Spring. |
56 | 11 Jan 2011 @ 10:44 PST | Tools | SQL Assistant Java Edition | The ACCOUNT property should have been in the list of JDBC Properties for the connection profile. It will get fixed and available in our next release. Sorry for the inconvenience.
|
55 | 28 Dec 2010 @ 07:45 PST | Tools | SQL Assistant Java Edition 13.10 for Windows 32-bit | It is currently limited to 4. We will resolve this in the next release. |
54 | 23 Dec 2010 @ 10:52 PST | Tools | SQL Assistant Java Edition 13.10 available | Yes, this is something we will look in to.
Thanks for bringing it to our attention. |
53 | 22 Dec 2010 @ 02:15 PST | Tools | SQL Assistant Java Edition 13.10 for Windows 32-bit | Bill,
Currently, SQLA JE and the Teradata Plug-in provides the list of JDBC properties for the user to choose from. CLIENT_CHARSET is not listed in the JDBC User's Guide, thus it is not in our lis... |
52 | 16 Dec 2010 @ 03:55 PST | Tools | SQL Assistant Java Edition 13.10 for Windows 64-bit | The SQL Results view is not longer used and instead SQL result data is displayed in the Result Set tabs of the Teradata View. When a group execution is run, the result sets are displayed as a group... |
51 | 16 Dec 2010 @ 03:44 PST | Tools | SQL Assistant Java Edition 13.10 for Windows 32-bit | The following is from the Teradata JDBC documentation, "Although the CLIENT_CHARSET connection parameter can be used to override the Teradata JDBC Driver fixed mapping of Teradata session character... |
50 | 15 Dec 2010 @ 01:53 PST | Tools | SQL Assistant Java Edition 13.0 available | My understanding is that the VMWare image running on your desktop is in its own private network within your desktop. You can access it from applications running on your desktop (and outside the VMW... |
49 | 19 Nov 2010 @ 05:06 PST | Tools | SQL Assistant Java Edition 13.01 for Windows 32-bit | The intent of the "New Editor" is to clone the current editor, with the same input as the current editor. Often this is used for editing a large SQL file where you want to view the file at differen... |
48 | 29 Oct 2010 @ 11:52 PDT | Tools | SQL Assistant Java Edition | Martin, I have not seen the problem of the case sensitivity, so I am puzzled as to why you are having this problem. I do not use exact case and the queries are successful. SQLA JE simply passes the... |
47 | 20 Oct 2010 @ 04:57 PDT | Tools | SQL Assistant Java Edition | We access the DBC views for the Teradata meta data to populate the Data Source Explorer. We will look into adding an option on the dialog such as 'Don't display this message again...' for exception... |
46 | 30 Sep 2010 @ 11:38 PDT | Tools | SQL Assistant Java Edition 13.01 for Windows 32-bit | I will try to address some of your issues.
The connection profiles, filters, and SQL history is stored in metadata in your workspace directory. The workspace directory is created in C:\Documents
... |
45 | 28 Sep 2010 @ 10:08 PDT | Tools | SQL Assistant Java Edition 13.01 available | There isn't currently a way to specify pre-load statements, but we have something similar on our list of enhancements that are being worked on.
Also, there is another option you can try to speed... |
44 | 27 Sep 2010 @ 02:35 PDT | Tools | SQL Assistant Java Edition 13.01 available | There is information that SQL JE is gathering from the Database about the database objects when loading them in the Data Source Explorer, as well as during syntax checking. The product will access ... |
43 | 24 Sep 2010 @ 10:07 PDT | Tools | SQL Assistant Java Edition 13.01 available | You can access multiple databases (or schemas) within a single database connection by providing the fully qualified name for the table access in your query. If you don't provide the database name, ... |
42 | 21 Sep 2010 @ 11:26 PDT | Tools | SQL Assistant Java Edition 13.01 available | The files that contains the connection profile information are driverStorage.xml and ServerProfiles.dat and located in the worksapce/.metadata/.plugins/org.eclipse.datatools.connectivity/ directory... |
41 | 20 Sep 2010 @ 08:55 PDT | Tools | SQL Assistant Java Edition 13.01 available | No, they should not go away. The connection profile information is stored in a metadata file in the workspace directory. If that is being deleted for some reason, then the connection profiles are d... |
40 | 16 Sep 2010 @ 03:00 PDT | Tools | SQL Assistant Java Edition | Thank you for your comments. We will look into your request for additional filtering options. |
39 | 14 Sep 2010 @ 08:55 PDT | Tools | SQL Assistant Java Edition | This should help if you are trying to display a large result set. You can also modify the number of rows to display in the SQL Results preferences. Otherwise there may be adjustments needed on the ... |
38 | 06 Sep 2010 @ 05:30 PDT | Tools | SQL Assistant Java Edition | The 'unexpected token' means that in parsing the fastload input file, it has come across an unexpected value. This could be that the number of values for a row in the input file does not match the ... |
37 | 14 Jul 2010 @ 03:58 PDT | Tools | SQL Assistant Java Edition 13.0 available | No. you should be able to run the CREATE PROCEDURE command with SQL. Check to make sure your SQL is correct. Fully qualify any table references if needed. If you can, test the SQL outside the proce... |
36 | 14 Jul 2010 @ 09:26 PDT | Tools | SQL Assistant Java Edition | Thank you for your feedback. In response to your concerns:
#1. There is a way to filter on the schemas list and select only specific schemas to show in the data source explorer: Right click on the... |