How do I add tables that already exist to a database?

Keith,

<< How do I add tables that already exist to a database? >>

Tables cannot exist in ElevateDB without a database.  Are you saying that
you don't have an EDBDatabase.EDBCat catalog file that corresponds to the
tables ?  If not, then the table files themselves are useless without it.

--
Tim Young
Elevate Software
www.elevatesoft.com

In trying to figure things out I believe I dropped the database from the
catalog.  Now the tables still exist (along with their indexs and blobs).  I
want them back.  The EDBcat.Old apparently got overwritten more than once
before I realized what I had done.

Keith,

<< In trying to figure things out I believe I dropped the database from the
catalog.  Now the tables still exist (along with their indexs and blobs).  I
want them back.  The EDBcat.Old apparently got overwritten more than once
before I realized what I had done.  >>

The database isn't stored in the catalog, it is stored in the configuration
file.  Did you try to simply create the database again using the CREATE
DATABASE statement or the EDB Manager ?  Just use the same path, and EDB
will simply use the existing catalog file and tables that are there.

--
Tim Young
Elevate Software
www.elevatesoft.com

1)  These database was migrated from dbisam3 and I have no create statement
saved.

2)  Let me see if I understand this:
       a)  The config file stores Users, Roles, Jobs, and Database Name and
Paths
       b)  The catalog stores the table metadata (table names, columns,
indexes, constraints, etc)
       c)  The edbtbl, edbidx, and edbblb files are nothing but pure data.
   If this is correct and I dropped the database, why isn't there a
function to add a database (catalog) back into the config?   I'm using EDB
Manager for everything at this point.

3)  In DBISAM terms, a database was a directory.  End users could move
directories to any computer and change the path, and all the program had to
do was point to the file directory where the tables were and everything was
fine.  It didn't matter how workstations referenced the server computer and
the directory where the tables were.  One could call it s:\my_data and
another could refer to it as z:\c-drive\my_data.  Is that not possible
anymore?  Can the config file not store relative path information.  If the
directory where all the tables and config files reside gets moved does that
break the system?

thanks


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:32B36606-02C2-4ACE-B163-377FADEEF9DB@news.elevatesoft.com...
> Keith,
>
> << In trying to figure things out I believe I dropped the database from
> the catalog.  Now the tables still exist (along with their indexs and
> blobs).  I want them back.  The EDBcat.Old apparently got overwritten more
> than once before I realized what I had done.  >>
>
> The database isn't stored in the catalog, it is stored in the
> configuration file.  Did you try to simply create the database again using
> the CREATE DATABASE statement or the EDB Manager ?  Just use the same
> path, and EDB will simply use the existing catalog file and tables that
> are there.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Keith,

probably it's simpler than you think.

If you migrated the table(s) from DBISAM, there should be a catalog-file in
the same directory as your tables. So the only thing you have to do is to
create a new database with a path that points to your tables.

Conclusion: You can drop a database at any time without losing your tables,
but the catalog is a part of the tables.

Just recreate the database, assign the table's path and you are done.

Regards Uli

Now i'm completely confused.  I restored a backup copy of the directory that
stored all these files.  Everything in this directory was perfectly fine.
Now I cannot get edb manager to add the database in.  If i say create new
database and point the folder to this directory I still get zero tables.

I'm completely lost.


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:32B36606-02C2-4ACE-B163-377FADEEF9DB@news.elevatesoft.com...
> Keith,
>
> << In trying to figure things out I believe I dropped the database from
> the catalog.  Now the tables still exist (along with their indexs and
> blobs).  I want them back.  The EDBcat.Old apparently got overwritten more
> than once before I realized what I had done.  >>
>
> The database isn't stored in the catalog, it is stored in the
> configuration file.  Did you try to simply create the database again using
> the CREATE DATABASE statement or the EDB Manager ?  Just use the same
> path, and EDB will simply use the existing catalog file and tables that
> are there.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Tried and tried.  Not working (using edb manager).  I'll try again tomorrow
after I sleep on it I guess. As of now it looks like I'll have to remigrate
the data and make all the adjustments all over again.


"Uli Becker" <test@test.com> wrote in message
news:3A98A5F7-05D6-4516-9680-D9E0079835CD@news.elevatesoft.com...
> Keith,
>
> probably it's simpler than you think.
>
> If you migrated the table(s) from DBISAM, there should be a catalog-file
> in the same directory as your tables. So the only thing you have to do is
> to create a new database with a path that points to your tables.
>
> Conclusion: You can drop a database at any time without losing your
> tables, but the catalog is a part of the tables.
>
> Just recreate the database, assign the table's path and you are done.
>
> Regards Uli

keith


Can you find a file with the extension EdbCfg or EdbCfg.Old (assuming you didn't change the ElevateDB defaults) if not then you have no catalog and about all you can do is re-migrate the data.

If you've changed things in the tables since the migration then migrate to a different folder and copy your current tables over the ones created.

I'd also suggest that you do a reverse engineer and store the sql somewhere safe just in case.

Roy Lambert [Team Elevate]

Keith,

<<  a)  The config file stores Users, Roles, Jobs, and Database Name and
Paths >>

Correct.

<< b)  The catalog stores the table metadata (table names, columns, indexes,
constraints, etc) >>

Correct (among other things such as functions, procedures, views, etc).

<< c)  The edbtbl, edbidx, and edbblb files are nothing but pure data. >>

Correct.  Think of them like tablespaces in other databases.

<< If this is correct and I dropped the database, why isn't there a function
to add a database (catalog) back into the config?   I'm using EDB Manager
for everything at this point. >>

There is such a function - just create a new database and point it to the
directory where the database catalog resides.  That will bring the database
back into the configuration.

<< 3)  In DBISAM terms, a database was a directory.  End users could move
directories to any computer and change the path, and all the program had to
do was point to the file directory where the tables were and everything was
fine.  It didn't matter how workstations referenced the server computer and
the directory where the tables were.  One could call it s:\my_data and
another could refer to it as z:\c-drive\my_data.  Is that not possible
anymore? >>

No.  If multiple users are accessing the same configuration file, then you
should use UNC paths to ensure that all users are referencing the same
database paths, irregardless of drive mappings, etc.

<< Can the config file not store relative path information. >>

No, it can store any path that you want.  However, using relative path
information is not a particularly robust mechanism and can break any time
the current working directory is changed for any reason.   And this can
happen through something as simple as using a file open dialog.

<< If the directory where all the tables and config files reside gets moved
does that break the system?

It broke the "system" in DBISAM also.  The only difference is that in
ElevateDB, you re-configure the path in the configuration file instead of in
the application's .INI file or a registry setting:

http://www.elevatesoft.com/edb_faqt_2.htm

--
Tim Young
Elevate Software
www.elevatesoft.com