I have version Toad Data Point 3.8.0.575.
My IT partners don't allow Beta versions for the line of business users like me and getting updated to version 4 is so difficult that it's just not going to happen.
John
↧
RE: How do I see the _entire_ error message
↧
Use Prompt Value in Query Results
Hello - I am new to Toad Data Point and am trying to figure our how to use a prompt value in the query results.
I know that I can set up a prompt in the query using a ":" (e.g. :SnapshotDate). However, lets say I want the :SnapshotDate to appear as a field in the query results as well.
In prior versions of TOAD...you could set up a prompt using & (e.g. &SnapshotDate)...and then call the prompt value in the query itself by listing &SnapshotDate as a field. Similar to this.... SELECT Name_, &Snapshot_Date FROM MyTable
It is not working for me in Toad Data Point using :SnapshotDate in the Select statement and as a prompt in the Where clause.
Any tips?
Thanks!
↧
↧
RE: Buggy behavior: TDP 3.8 overwriting Vertica SEARCH_PATH with "default schema"
FYI, QAT-8944 got fixed and is part of TDP 4.1 release. This is due to be released Dec 8. We added in the SQL Editor a drop down that says "I will set the schema/database myself" and this bypasses the setting of the schema that we do. You just set the search path yourself in the script.
↧
Buggy behavior: TDP 3.8 overwriting Vertica SEARCH_PATH with "default schema"
Where most other databases use CURRENT_SCHEMA, HP Vertica uses a SEARCH_PATH. SEARCH_PATH allows users to list multiple schemas for which an object should be searched during a particular session.
So if my current session's SEARCH_PATH is:
Schema1, Schema2, public
If I run SQL "SELECT * FROM FOO;" over that session, Vertica will attmpt to resolve the schema of FOO by looking for Schema1.FOO, then Schema2.FOO, and finally, public.FOO.
Toad Data Point has 3 bugs in how it handles Vertica's SEARCH_PATH feature.
Bug#1 (minor): Connecting Toad Data Point to a Vertica Database requires an ODBC connection. One of the properties of a Toad Data Point ODBC connection is "Database". For Vertica ODBC connections, this is an "invalid option" bug. For Vertica connections, the choice of database is built into ODBC source definition (the database is part of the ODBC URL). This option should either be invisible, or as a hard-coded/non-editable field that just lists echos the database portion of the Vertica connection URL.
Bug #2 (minor): In addition to being unnecessary, this "Database" field is also mislabeled. As evidenced by the dropdown list after clicking the [...] button, the field is actually referring to "the default schema that is set after connection is established". This bug (the label says Database when it means Default Schema) can be verified directly: when configuring a new Vertica ODBC connection in Toad Data Point, when I click the "..." next to "Database", the drop-down of values is actually all the schemata in the Vertica database (not the "list" of databases which, as noted in Bug 1, can only be database string in the URL).
Bug #3 (major) The real problem is how Toad handles the "default schema" for ODBC-Vertica connections. Say I choose "Schema2" for the the "Database" option of a Vertica connection. Based on this setting, when I open a new connection, Toad sends the following SQL string over ODBC: "SET SEARCH_PATH=Schema2".
What makes Bug#3 such a nasty bug is that
1) This command gets run (automatically) after all other connection settings are applied. So if my Vertica user account has default SEARCH_PATH of "Schema1, Schema2, Schema3, public", that default is overwritten by Toad Data Point to just "Schema2". Even if I make my desired SEARCH_PATH using the ODBC Connection String, this bug overwrites that value.
In other words, if I put "ConnSettings=SET SEARCH_PATH TO Shema1, Schema2, Schema3, public" in Connection String, and set that same SEARCH_PATH for my user account, after I connect to Vertica, and run SHOW SEARCH_PATH;, I will see the search-path is just "Schema2". The behavior can also be observed after connection is established. If the "default schema" (hover-text = "Select the schema/instance to associate with the statement") is changed from Schema2 to Schema3, behind the scenens the command "SET SEARCH_PATH=Schema3" is sent.
2) This behavior cannot be disabled. This is my main beef. The behavior pretty much completely prevents using SEARCH_PATH functionality in Toad Data Point; which effectively eliminates any ability to use Vertica's SEARCH_PATH feature - a sufficiently large obstacle to entice me to find an alternate IDE for Vertica analysis (and recommend the same to colleagues).
↧
How can I remove the name of the database from the Generates SQL feature?
Hi
i am using a ODBC connection to a HIVE environment. When I use the GENERAL SQL feature from one of the tables the query adds the name of the database in this case HIVE and then the schema and the table so it will be something like:
SELECT * FROM HIVE.schema_name.table_name
The problem is that it will fail and I have to remove the HIVE for the query to work so:
SELECT * FROM schema_name.table_name
When I try to pull the data in the Explorer it also gives an error.
Is there a way to change the settings so the Generate SQL or any query done does not include the database name?
Than you
↧
↧
RE: TDP Giving Up on Query Connections with No Error in Automation
Hi Debbie and TDP team. I was wondering if there were any additional updates on this issue and if there's been any developments from the other developers you were checking into on this? Thanks! Chad
↧
TDP Giving Up on Query Connections with No Error in Automation
I hope I can explain this well.
This is a problem that we've had for some time, but I was really working to ensure it wasn't an issue on my end before I submitted this to TDP. I do believe it may be on the TDP product end. Essentially we use TDP 4.0, but I've seen the problem as well on earlier versions. We have our queries that connect using an I-Series ODBC connection to an AS400 using DB2 SQL. All of our queries use this. With that being said, I've noticed quite frequently that long running queries (those that take possibly an hour or more to run) have issues specifically when running in automation that are essentially giving up the connection to the query and continuing to run on the machine. Therefore, when I come in in the morning I notice that the little toad icon is still up and the automation task is still running and I have to forcibly end the task and then attempt to rerun. (It will work usually when rerunning and this issue isn't present every time the query runs, just on and off, most notably when CPU is higher and query times are running even longer than normal) I have the ability to check the query running on the AS400 and when I do this on these queries in automation that give up and essentially keep running, I notice that the query is no longer running on the AS400. Therefore, I'm suspecting that somehow the query either times out or is killed some how on the TDP automation end, but throws no errors back. The reason I believe this, is I also have the ability to terminate connections to queries on our AS400 which means that I can stop a query on the AS400 side. If this was the case, or connections get lost, I always throw back an error on the automation that the connection has been lost, which is great and tells me that it will error for connections lost on the AS400 end. This is why I assume its something with the TDP product. I'd like to see if the wonderful TDP support folks have seen this issue before and if not, what information I may be able to provide to help this issue to be researched. Also, I'd love to hear if anyone else has experienced anything similar.
Hope to hear from you soon.
Chad
↧
RE: Deduplicate issue in Transform and Cleanse
I answered a similar post in beta forum, http://www.toadworld.com/products/toad-data-point/toad_data_point_beta_program/f/91/t/31791
Hope that helps.
↧
Deduplicate issue in Transform and Cleanse
I have a challenge trying to deduplicate in the transforn and cleanse process.
Couple of question on this:-
1. What is the order of removing duplicates in transform and cleanse.
2. Is it from top top bottom or bottom to top or arbitrarly?
My issue is that I have loan numbers with mulitple records due to activities and task performed on the same loan number over time. I will want to remove the duplicates and keep the record with the most current completed task by date. In excel I will sort by New to Old and de-dupe. This keeps the most current date and removes the duplicates below . How can I achieve same with transform and cleanse feature.
Your help will be appreciated
Chris
↧
↧
RE: Use Prompt Value in Query Results
Try Select :YourVar PromptedValue, whateverOtherFields From MyTable Where someField = :YourVar
You should get prompted for the YourVar value once and see it in the results that get filtered by the same value. I am using TDP ver 3.7.0
↧
RE: Toad Data Point on Citrix
There’s a KB on this topic for Toad for Oracle, it should apply for TDP too. Please login and follow the instructions
https://support.quest.com/toad-for-oracle/kb/12709
Hope this helps.
↧
RE: Data Point connection to PostgreSQL database instance
Hi Bob,
I'm also having this kind of problem when connecting PostgreSQL database.
When I edit the Connection String and try to connect, this error appear: "Unknown Authentication type".
Fyi, previously I'm able to connect without editing the ConnectionString, but the problem is I cannot view the data inside the tables correctly. It will show this kind of error:
Error while executing the query;
ERROR: schema "<None>" does not exist
Please help for anyone who know about this.
↧
RE: Data Point connection to PostgreSQL database instance
You are better off defining a System or User DSN. This way the driver handles the connect string. Can you try this?
↧
↧
Data Point connection to PostgreSQL database instance
I'm in need of detailed instructions to make a clean connection with Toad Data Point to POSTGRESQL database instance.
↧
RE: Use Prompt Value in Query Results
I use this technique all of the time in our Toad Reports. Works great!
↧
RE: Data Point connection to PostgreSQL database instance
I already solved the problem.
First, I install the latest ODBC driver for PostgreSQL 9.6 at this link https://www.postgresql.org/ftp/odbc/versions/msi/
Then, I add System DSN at Control Panel\Administrative Tools\Data Sources (ODBC)
But, it's quite tedious. Because one System DSN can only connect to one database, unlike Oracle or SQL Server where we can browse through all available Schema after one System DSN connected
Regards,
Azlan
↧
RE: Problem connecting to PostgreSQL
I already solved the problem.
First, I install the latest ODBC driver for PostgreSQL 9.6 at this link https://www.postgresql.org/ftp/odbc/versions/msi/
Then, I add System DSN at Control Panel\Administrative Tools\Data Sources (ODBC)
But, it's quite tedious. Because one System DSN can only connect to one database, unlike Oracle or SQL Server where we can browse through all available Schema after one System DSN connected.
Thank you for your help, Libor.
Regards,
Azlan
↧
↧
Problem connecting to PostgreSQL
Hi.
I'm trying to connect to a PostgreSQL database, but failed. During connection, there is a warning stated that "Minimum driver version requirement not met. You will still be able to connect, however some Toad features may not be available." (My version of PostgreSQL is 7.4.2)
Then, I just ignore the warning, and proceed. Connection looks successful, but i got this error message:
"Error while executing the query;ERROR: schema "<None>" does not exist"
The schema available at my PostgreSQL is only Public Schema. At Toad Data Point Navigation Manager, I can see all the tables, but because of schema is <None>, it will pop up error message "schema "<None>" does not exist" everytime I tried to view the table's content.
Thanks in advance.
↧
RE: How can I remove the name of the database from the Generates SQL feature?
I don't think there is an option for it. Did you try create a HIVE connection directly instead of using ODBC?
↧
RE: TDP Giving Up on Query Connections with No Error in Automation
We just finished TDP 4.1 so we have some more time. I have reviewed QAT-8972, which is the current open task for this issue, and have assigned to Aleksey. He will start work on this mid-next week. In the meantime I would like to capture fresh logs. We did find an error that when you open the automation script it will delete the last automation log. This is why you couldn't find the logs before So the next time you get the hang, go to app data dir, dont open the automation window and get me the following logs.
C:\Users\%userprofile%\AppData\Roaming\Quest Software\Toad Data Point 4.0\ExecutionTrace.log
C:\Users\%userprofile%\AppData\Roaming\Quest Software\Toad Data Point 4.0\Automation\automation*.log (Grab any that have hung)
C:\Users\%userprofile%\AppData\Roaming\Quest Software\Toad Data Point 4.0\ImportExport\ exportlog_TMPxxx.log
NOTE: It would also be helpful is you have verbose logging turned on
↧