Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Redesigned databases

Status
Not open for further replies.

ducksoup

Programmer
Aug 17, 2001
35
US
Hey all --

I have remapped a database in SQL7.0 so that I could eliminate some tables and create some primary keys and indexing. The database has about 500,000 records, and was transferred like this:

for each (patron in old database) do
insert patron in new database
get patron_identity
for each patron_record (in old database) do
insert patron_record with patron_identity
get patron_record_identity
end
end /* it's worse than this, but that's the gist */

checking the rowcounts in each database, though, there's about 160 rows extra in the NEW database. i checked to see if they happened be null values, and i've checked to see if the externally-generated id's (this data is imported weekly from a university library) were different -- but there are no externally-generated id's that exist in one but not in the other.

AND because i'm using a new identity, the pk's don't match anymore so I can't validate those directly, only aggregates.

is there any way to try and match these two up, or check for duplicates in the new one (maybe i'm looping over some if-statement near the bottom once too many times...)???

everything looks ok, but i don't trust it yet. Help! __________________________________
"This is our Stretchy-Relativistic-Ruler -- it allows us to read a moving measurement from a fixed point accurately during space contraction... How fast can you run down the hall?" -- Overheard Physics Professor at the University of Oregon
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top