Re: Miagrating Data from SE to ONline Engine

> > I am miagrating Data From SE to Online Engine. I am going to use > DBEXPORT and DBIMPORT to do this eventually. Right now, I am using > Unload and Load statement to load tables into Online. Some of these > tables are very large and I got a message "Long Transactions". The > databases uses unbuffered logging and there are 50 logs defined with > size of 300 Kbytes. I was able to solve by changing the database to NO > LOGGING and it worked fine. Right now, I have no problem having NO > Logging to load large tables. But, Once my database in production with > UNBUFFERED Transactions then how would I handle this so I can insert > large tables without running into "Long Transacations"? Is there any > command that allows me to turn from UNBUFFERED logging to No Logging > for that one process? > > > How should I setup my database Logging when I use DBIMPORT to miagrate > the data to ONLINE? Personally, i'd use dbload to load the new rows. dbload counts rows between commits, and can be run with logging on. We wrote a similar set of programs to dbexport/dbimport, called dbsave/dbrestore that unloads an entire database or part of one, and reloads the data using dbload. > When this database in production with UNBUFFERED LOGGING then How can I > prevent user from not doing long transactions? If you are referring to stopping it through isql, you can't. Only educating the users will help. In your programs, you must educate the programmers to keep transactions small. When we have a large change to make to a large table, we turn off logging, and exclusively lock the table (during small scheduled outages). Its the only safe way. -- Naomi Walker (aka N7FSA) | naomi@anasazi.com | Phoenix, Arizona ---------------------------------------------------------------------- It's almost impossible to overestimate the unimportance of most things.