 |
 |
Archives of the TeradataForum
Message Posted: Thu, 18 Sep 2003 @ 19:39:43 GMT
| Subj: | | Re: COGNOS Impromptu Scheduler |
| |
| From: | | McBride, Michael |
| | "Depending on whether you're using Teradata or ANSI transaction semantics will change how you place/release locks, but the principle
remains the same." | |
This is very true, but even when you think your safe, (we have Teradata Mode as the default mode via the DBS Control record)
certain end-user tools like Impromptu appear to override the default and query via a Read Committed mode. Interestingly, the session data
indicates the session is in Teradata Mode, but apparently the query itself is bracketed in some way like a BT/ET and if you don't use the
work around I explained in a previous post, the session never gets the "ET" (End Transaction) until the session is logged off. This is an
outright bug in Impromptu that Cognos should address, but haven't had much luck as yet...
| |
