Is it normal ?

Database
Enthusiast

Is it normal ?

INCREDIBLE ...
the context :

the batch jobs insert/update datas with transaction:

begin transaction
lock table tutu for write ;
insert ..
update ...
...
end transaction

We have view with lock row for access so anyone can see data even if they are updating or inserting.

During transaction (as by default we are in teradata mode (not ANSI)) all datas can be read by end users throught reporting.

I was sure it was working like in ANSI mode (nobody can see the changes until commit). Unbelievable for a datawarehouse (data intergrity, where are you ?)

I'm wondering if it's not better not to have view with row lock for access, so all end users will be locked, and wait data will be safe...

Worst

done the same thing in bteq, but begining by
.SET SESSION TRANSACTION ANSI ;

same result, anyone can see my updates, insert ...

This is ABSOLUTLY NOT ANSI standard.
2 REPLIES
Enthusiast

Re: Is it normal ?

Sorry, but I don't quite get it.

If I want "read commited" in teradata, should I set the transaction mode to ANSI, as you pointed in previous post that teradata also support ANSI (Do i mis-read?)

Many thanks.
Junior Contributor

Re: Is it normal ?

- There are two session modes within Teradata RDBMS: ANSI session and Teradata session
- There are lots of minor differences between those session modes (e.g. autocommit/case sensitivity,...)
- But regardless of session mode the Teradata RDBMS only supports
Read Uncommited & Serializable

Dieter