Hi,
I noticed that elevateddb creates a number of files for each table in the database.
Is there a setting so only one or a few files are created in total no matter the number of tables?

If not it would be a nice change in the future.

The reason is that when making the distribution of my software I would like as few files as possible

Regards Torben

Torben Laursen wrote:

> Hi,
> I noticed that elevateddb creates a number of files for each table in
> the database.  Is there a setting so only one or a few files are
> created in total no matter the number of tables?
>
> If not it would be a nice change in the future.
>
> The reason is that when making the distribution of my software I
> would like as few files as possible
>
> Regards Torben

Yes.  From the website..

"ElevateDB automatically creates all necessary files when they are
needed. For example, you can distribute a single database catalog file
with your application, and ElevateDB will automatically create the the
table files as they are opened by sessions. In addition, ElevateDB
provides reverse-engineering facilities that allow you to easily create
creation and upgrade SQL scripts that can be run during installation to
transparently create any necessary system or database objects."

Malcolm

The database is filled with content so the files are allready present.
It is not a major problem, I just want to keep track on as few files as possible.

Torben

Torben,

<<
I noticed that elevateddb creates a number of files for each table in the database.
Is there a setting so only one or a few files are created in total no matter the number of tables?
>>

In general there are 3 files created (table data, index and blob) per table so that's what you should be including for each table together with the catalog files if you want the table data to be present. The other option is to create the tables and data on the 1st run or from installer using a sql script. This would potentially make updates easier as well.   Another option would be to include EDB backup of your database with your installer  (this would be single file) and then on 1st run do a restore.  

Tim has mentioned a single-file database model for EDB but not before EDB v3 (next version) and even then at some point he called it Enterprise version so not sure what the final product will be like. He is well aware of the need but ETA is unknown at this time and if I took a wild guess i'd say we're still a year out.

Raul