Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 6 of 6 total
Thread Moving tables (database)
Thu, Jan 18 2007 9:29 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim

If I create (migrate) a database in (say) C:\trial how do I move it to E:\TfR?

Roy Lambert
Thu, Jan 18 2007 9:37 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim


Just re-read what I'd posted and realised it could easily be mistaken.

I migrated a database from a live DBISAM system to C:\Zap\Trial under ElevateDB and then thought what if I don't want it there but want to physically locate it somewhere else - is this a simple copy or what?

Roy Lambert
Thu, Jan 18 2007 4:30 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Roy,

<< If I create (migrate) a database in (say) C:\trial how do I move it to
E:\TfR? >>

It's a three-step process:

1) Move the database directory contents to e:\tfr, being sure to include the
database catalog "edbdatabase.edbcat".

2) Drop the existing database using the DROP DATABASE SQL statement.   DO
NOT do this step without doing the first step or you'll simply just delete
the entire database and have no backup copy.

3) Create the same database name with the new path using the CREATE DATABASE
SQL statement.

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Jan 19 2007 4:51 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim


A bit messier than just a straight file copy but it looks easy enough

Roy Lambert
Fri, Jan 19 2007 7:35 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Roy,

<< A bit messier than just a straight file copy but it looks easy enough >>

Yeah, but it buys not having to ever use a directory path name anywhere in
your application SQL or code, which makes the code completely portable by
only needing to change the database path definition itself via CREATE
DATABASE.  It's essentially the same as DBISAM C/S, but in local and C/S.

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Jan 19 2007 8:54 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim


>Yeah, but it buys not having to ever use a directory path name anywhere in
>your application SQL or code, which makes the code completely portable by
>only needing to change the database path definition itself via CREATE
>DATABASE. It's essentially the same as DBISAM C/S, but in local and C/S.

Nifty and I can see some advantages to it.

Roy Lambert
Image