15 | 02 May 2008 @ 02:39 PDT | Analytics | Reply | Facing error- '{' ('7B'X) is not a valid Teradata SQL token. | Some times comments might contain special characters like ' or " TD Syntaxer acts little funny some times. Same sql works fine in BTEQ. |
14 | 02 May 2008 @ 02:37 PDT | Analytics | Reply | EXcel to Teradata | If you have access to oleload tool, you can use that. You can import from access directly. To import from Excel, you need to modify the connection properties of Microsoft Jet 4.0 OLE DB Provider to... |
13 | 25 Jul 2006 @ 07:52 PDT | UDA | Reply | How to run a stored procedure please? | call nameofprocedure() |
12 | 06 Jul 2006 @ 02:03 PDT | Database | Reply | Problem with installation Teradata V2R6 | I guess you have administrative privileges on that machine. Is it a brand new installation or upgrading to newer version? |
11 | 29 Jun 2006 @ 03:13 PDT | Connectivity | Reply | Trying to set up ODBC connection | What TTU are you using? Before installing the ODBC driver, there are other dependencies such as TDICU and TeraGSS packages. These need to be installed first before installing ODBC driver. |
10 | 29 Jun 2006 @ 03:08 PDT | Analytics | Reply | dbql rule help | As mentioned in the error message, if you select Summary, you can not add a rule with other options. The best way to see these dependecies is to use Teradata Administrator. If you select Query Logg... |
9 | 29 Jun 2006 @ 01:52 PDT | Database | Reply | Joins | The joins are picked up based on the costing. The whole plan is built by costing different paths. If you have enough stats for a NUSI-UPI join you may expect Nested Join. Similarly, if the demograp... |
8 | 19 Jun 2006 @ 09:35 PDT | Database | Reply | Migrating to V2R6 | My suggestion is to check with other applications used in your environment are compatible with TTU 8.0 before migrating. Compatability in terms of getting support from the respective vendors. |
7 | 19 Jun 2006 @ 09:33 PDT | Database | Reply | COLLECT STATISTICS | I recommend collecting stats on at least on Primary Index column. In the absence of stats, we may encounter soome bad plans. At times, a larg table may be assumed smaller to a small table. This lea... |
6 | 19 Jun 2006 @ 09:30 PDT | Database | Reply | PPI explain | In the second query, we have conditions on exactly primary index and partition columns. With additional ANDed conditions in the first query it picked up a different plan. |
5 | 19 Jun 2006 @ 09:24 PDT | Database | Reply | 10065 WSA E HostUnreach | Could you check the pdestate with option a like pdestate -aIf you see something like logons are disabled, you need to enable the logons. Otherwise, you can not login. |
4 | 19 Jun 2006 @ 09:15 PDT | Analytics | Reply | PERFORMANCE ISSUES | The statements SEL * FROM TABLENAME and SEL * FROM TABLENAME WHERE 1=1 have all rows scan access path. The performance difference is none. If you consider the following scenario,INS Target SEL * FR... |
3 | 16 Jun 2006 @ 03:30 PDT | Database | Reply | Collecting Statistics on multiple Columns | I do not think it makes any difference. When different column combinations are analyzed, the combined stats are analyzed. Based on this analysis, optimizer estimates the combined cost. |
2 | 16 Jun 2006 @ 03:27 PDT | Database | Reply | why this error was raised? help me! | According to ANSI semantics, we can not update the same target row by multiple source rows. This error is to prevent that. |
1 | 25 Jan 2006 @ 01:13 PST | Third Party Software | Reply | Teradata and Ascential Data Stage | My suggestion is to check the query submitted to the database. We may not see the exact query that is submitted via BTEQ. Some times these tools generate data mismatch conditions. Due to this optim... |