Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 5 of 5 total |
Just got started ... |
Tue, Sep 9 2008 11:42 AM | Permanent Link |
adam | Just got started with EDB, so far sooo good. I am bound to be asking a few questions in
the next few days though! First tiny request. When migrating from DBISAM -> EDB it would be great if there was a choice over which tables to migrate, i.e. pull up a pick list to tick off which tables you want. I realise most people just want all of them, but I have some multi-gig databases & only want to transfer some parts, as other parts are historical. Adam |
Tue, Sep 9 2008 12:15 PM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | adam
Nice idea - as a temporary workround rename the table extensions to something the migrator doesn't recognise - that should stop it. Just remember to rename them afterwards Roy Lambert [Team Elevate] |
Tue, Sep 9 2008 2:33 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Adam,
<< When migrating from DBISAM -> EDB it would be great if there was a choice over which tables to migrate, i.e. pull up a pick list to tick off which tables you want. I realise most people just want all of them, but I have some multi-gig databases & only want to transfer some parts, as other parts are historical. >> I'll see about getting table selection added. I've got to change around some of the migration code anyways. -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Sep 10 2008 4:20 AM | Permanent Link |
adam | That's a great workaround. Thanks.
Having transferred several DBs yesterday I encountered 1 more niggle of my own making. 1 older DB I transferred had a corrupted table in it, the migration process simply stopped at the corrupt table, fair enough really but better behaviour would have been either to just skip a corrupt table and hold a message in a log about it or (perhaps) attempt to repair the table & then migrate it? Adam |
Wed, Sep 10 2008 4:50 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | adam
>That's a great workaround. Thanks. Old family motto - If at first you don't succeed CHEAT! >Having transferred several DBs yesterday I encountered 1 more niggle of my own making. > >1 older DB I transferred had a corrupted table in it, the migration process simply stopped >at the corrupt table, fair enough really but better behaviour would have been either to >just skip a corrupt table and hold a message in a log about it or (perhaps) attempt to >repair the table & then migrate it? The second option makes sense but not the first with the new concept of database rather than a collection of tables. I keep coming up against some of these concepts and having to send my brain through another rinse cycle to try and get them straight. Roy Lambert [Team Elevate] |
This web page was last updated on Tuesday, April 30, 2024 at 03:55 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |