![]() |
What are the reason(s) why a PK will be implemented as USI instead of UPI? This question was formulated based on the following statement:
28 Mar 2016
| 9 comments
,
|
![]() |
Hello All,
11 Feb 2016
| 2 comments
,
|
![]() |
I understand that a SET table has an overhead of checking for duplicate rows while data is being inserted into the table. However, if the table has a UPI/USI defined on it, only the UPI/USI columns are checked for duplicates and not duplicate row checks. Is this understanding correct ?
28 Oct 2015
| 1 comment
,
|
![]() |
Hi All,
15 Jul 2013
| 3 comments
,
|
![]() |
I have been fighting with this for weeks now. Basically I have .NET application that is using a teradata backend. I cannot for the life of me figure out why I keep getting this error, and it's random. The application itself does not specify any auto increment. I'm leaving that up to Teradata using the following create statement. Again - this has been completely random. It can be from updating a record or creating a new record. CREATE TABLE BCPM_DDBO.LTC_FBS
03 Aug 2011
| 1 comment
,
|