#DateForumTypeThreadPost
1502 May 2008 @ 02:39 PDTAnalyticsReplyFacing 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.
1402 May 2008 @ 02:37 PDTAnalyticsReplyEXcel to TeradataIf 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...
1325 Jul 2006 @ 07:52 PDTUDAReplyHow to run a stored procedure please?call nameofprocedure()
1206 Jul 2006 @ 02:03 PDTDatabaseReplyProblem with installation Teradata V2R6I guess you have administrative privileges on that machine. Is it a brand new installation or upgrading to newer version?
1129 Jun 2006 @ 03:13 PDTConnectivityReplyTrying to set up ODBC connectionWhat 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.
1029 Jun 2006 @ 03:08 PDTAnalyticsReplydbql rule helpAs 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...
929 Jun 2006 @ 01:52 PDTDatabaseReplyJoinsThe 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...
819 Jun 2006 @ 09:35 PDTDatabaseReplyMigrating to V2R6My 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.
719 Jun 2006 @ 09:33 PDTDatabaseReplyCOLLECT STATISTICSI 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...
619 Jun 2006 @ 09:30 PDTDatabaseReplyPPI explainIn 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.
519 Jun 2006 @ 09:24 PDTDatabaseReply10065 WSA E HostUnreachCould 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.
419 Jun 2006 @ 09:15 PDTAnalyticsReplyPERFORMANCE ISSUESThe 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...
316 Jun 2006 @ 03:30 PDTDatabaseReplyCollecting Statistics on multiple ColumnsI 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.
216 Jun 2006 @ 03:27 PDTDatabaseReplywhy 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.
125 Jan 2006 @ 01:13 PSTThird Party SoftwareReplyTeradata and Ascential Data StageMy 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...