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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Need to combine 5 databases

Status
Not open for further replies.

Fadius

IS-IT--Management
Joined
Jul 25, 2001
Messages
139
Location
US
I have a site that instead of using a networked version of this application, decided to install 5 stand alone version of the app. Now they want to move it to the networked version so they can share all the data. WHat would be the easiest approach to combining the data in thes e 5 databases?

The Table structure is exactly the same in all 5 databases.


Thank you in advance.
 
COPY THE DATA FROM EACH TABLE.
THEN USE THE PASTE APPEND FUNCTION

I love deadlines. I especially like the wooshing sound they make as they fly by.
-Douglas Adams
 
There are going to be a ridiculous number of "synchronization errors". I can't even begin to help you because it depends on: a) if you have lots of related tables, including parent/child relationships, b) if there are lots of duplicate records, and how to pick which row of the duplicates to 'use', c) the value of your data, meaning how useful is it for everyone to see all the old data.


Depending on c), you can either throw together all the data and just drop everything that conflicts, or you'll have to go through a tedious "data scrubbing" routine that involves...well, I've done that twice recently, and it involves a lot of work if you're going to do it right.

Good luck.


Pete
 
you should be able to do a make table query using a UNION. I believe that will even give you only distinct records. Do you need to flag which database the record came from?
 
besides the data issue(s) already mentioned, it is possible / probable that the versions also differ in some other manner, such as some user(s) having generated their own queries, forms, reports, etc. If these exist -and need to be retained -you have even more of a chore.

It is even possible (probable?) that some of the objects were modified in one or more copies of the db. I would advise you to discuss the pitfalls with the users (ALL of them) and then with the management. Failure to do so could easily result in a great deal of dis-satisfaction, and depending on the source of that dis-satisfaction, it could be "a carrear altering event".




MichaelRed
m.red@att.net

Searching for employment in all the wrong places
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top