Database

Re: Microsoft ODBC Driver for Oracle [urgent] Please Help

2-Oct-07 1:24

Please don't cross post and please don't put Urgent in the title.

Deja View - the feeling that you've seen this post before.

Programm3r2-Oct-07 4:58

Programm3r

2-Oct-07 4:58

Will do Pete Smile | :)

The only programmers that are better that C programmers are those who code in 1's and 0's Green Alien | [Alien]

Programm3r
My Blog: ^_^

Re: Microsoft ODBC Driver for Oracle [urgent] Please Help

Pete O'Hanlon2-Oct-07 9:55

Re: Microsoft ODBC Driver for Oracle [urgent] Please Help

2-Oct-07 9:55

Cheers.;)

Deja View - the feeling that you've seen this post before.

ChandraRam2-Oct-07 21:05

Duplicate with the Same Identity Number

2-Oct-07 21:05

You say "dont" he says "will do" and you say "cheers"?? Fun language this... Smile | :)

Vimalsoft(Pty) Ltd1-Oct-07 21:54

1-Oct-07 21:54

I have a table, that has an Identity Column as a Primary key.Suddenly there are some Dublicate that have same idenitity Column ID, and they look identical. i cant remove the Duplicates because they have the same ID. please help me to remove the Duplicate.

thanks

Vuyiswa Maseko,

Sorrow is Better than Laughter, it may Sudden your Face, but It sharpens your Understanding

VB.NET/SQL7/2000/2005
http://vuyiswamb.007ihost.com
http://Ecadre.007ihost.com
vuyiswam@tshwane.gov.za

Pete O'Hanlon1-Oct-07 22:19

1-Oct-07 22:19

Hmmm. Did you remove the unique constraint from your primary key field by any chance (the identity column is a primary key, isn't it)? This constraint is there to ensure that you can't have duplicate fields.

Anyway, there are a number of ways that you could do this, but the implementation really depends on factors such as do you have foreign keys linked to your table? If so, then you really need to be careful about deleting.

A quick thought has occurred to me - how did you select these records? Are they part of a multi-table select? If so, it is likely that what you are seeing is the result of a one-to-many relationship. Try selecting the data out of the table on its own.

If a single table select still produces duplicate data and it's not a part of a foreign key then you can do the following:

Open up your table in the designer and drop the identity column. Save it to the database. Then add the identity column back into the table and save it again. The stages here drop the identity column and then force the database to apply a new identity column - which will have the effect of giving a new Id to each record. Voila - you now have unique rows.

Deja View - the feeling that you've seen this post before.

Vimalsoft(Pty) Ltd1-Oct-07 22:50

1-Oct-07 22:50

Hi

Thanks for your reply

i did not remove the primary key Constraint. And there is a Foreign key linked to this table.

Pete O'Hanlon1-Oct-07 22:53

1-Oct-07 22:53

I fail to see how you've got this problem then because the unique constraint prevents duplicate data from being posted. The identity column is the primary key isn't it?

BTW - just a quick confidence test. You are using SQL Server aren't you?

Deja View - the feeling that you've seen this post before.

Vimalsoft(Pty) Ltd1-Oct-07 23:08

1-Oct-07 23:08

yes, it is the Primary key, i have not used the Unique Constraint, sorry about that. i thought if i make a Column Primary key and its identity. it will enforce the Uniqueness. my Field is a Primary key, and i have not defined the unique constraint.

Thanks

ChandraRam2-Oct-07 20:59

2-Oct-07 20:59

Vuyiswamb wrote:
yes, it is the Primary key, i have not used the Unique Constraint, sorry about that. i thought if i make a Column Primary key and its identity. it will enforce the Uniqueness. my Field is a Primary key, and i have not defined the unique constraint.

Surely if the field is the primary key, the database would not have allowed you to fill duplicate values in the first place?

And I also noticed that you said something like "looked identical" in your first post... how did you determine that you had duplicates in your table?

Vimalsoft(Pty) Ltd2-Oct-07 21:18

2-Oct-07 21:18

i have used a Query to Determine that.

SELECT *
FROM sde.Property p1
WHERE (FUNC_KEY = 'PV000000') AND EXISTS
        (SELECT 1
      FROM sde.Property p2
      WHERE p2.lis_key = p1.lis_key
      HAVING COUNT(p2.Property_ID) = 2)
      order by Property_ID Asc

Thanks

ChandraRam2-Oct-07 21:22

2-Oct-07 21:22

What happens if you just say

SELECT * FROM sde.Property WHERE (FUNC_KEY = 'PV000000')

how many records do you see?

Vimalsoft(Pty) Ltd2-Oct-07 22:04

2-Oct-07 22:04

i see Records with Dublicates in Property_ID.

ChandraRam2-Oct-07 22:32

2-Oct-07 22:32

Vuyiswamb wrote:

i see Records with Dublicates in Property_ID.

Then it looks like Property_ID is not the primary key of this table.

John-ph1-Oct-07 22:52

John-ph

1-Oct-07 22:52

Either you must be referring to a Foreign Key Column for which Unique-Key Constraint is not set or You must be doing a Multi-Table Select. There is no chance of Identiy Primary key Column to generate Duplicate value.

Regards
J O H N

"Even eagles need a push." David McNally