Re: Transfering tables

M Auger wrote: > > >M Auger wrote: > >> > >> We need to transfer some tables between 2 databases on a regular basis. Most > >> tables have referential constraints, there are hundred of tables we have to > >> look for. Is there an easy way to list the tables in order they should be > >> inserted first? > >I would create the second tables without constraints, load data and > >create > >constraints. In case it is done only once (or is it not ?) it seems to > >me > >quicker then anything else. Loading data into tables without > >constraint/indexes > >is also quicker - there are no integrity controls during load. > > >Michal Hajek > >-- > >-------------------------------------------------------------- > >Michal Hajek mailto:hajek@nspuh.cz > >Sprava NIS http://www.nspuh.cz > >NsP Uherske Hradiste phone : voice +420 0632 529 204 > >Purkynova 365 fax +420 0632 551 014 > >686 68 Uherske Hradiste Czech Republic > >-------------------------------------------------------------- > > My exact situation is : we will be running 2 databases in parallel for at > least one month, and a transfer between databases can be triggered by the user > at any moment which could be every 10 minutes or 30 minutes. That's why we > need to determine the order at which the tables should be inserted first. We > started doing this manually, someone is also trying to find a script > solution, but I thought I could a quicker solution on the Net. The > No constraints solution would not be practical in our situation. > Thanks for your comment. > > Michel Ideally, the tables should be inserted in tabid order. That way, the master tables should be inserted first, then the child tables inserted and constraints created. John Carlson