Hi Tim,
I have problems on manage the new architecture of config files and catalogs
with EDB server and local.
I have a lot of databases that must be collected and managed by users and
it's very dangerous to work with catalogs and config files, respect of
DBISAM.
Why you don't prepare the enterprise release with 1 file for database that
manage all within?
So my question is: Using DBISAM4 C/S what penalty I have to pay in
performance and number of connected users or session, in a large internet
installation (+-300 users) respect EDB  (my last post) ?
I have need (my customers need) often to change folders, substitute files
tables and other thing  that I cannot provide with EDB catalogs and
configs...
I will use EDB for another kind of application (under my control...
Thank you for the excellent support...
Stefano Monterisi

Stefano,

<< I have problems on manage the new architecture of config files and
catalogs with EDB server and local. >>

Why would you have an issue with configuration files and the ElevateDB
Server ?  The DBISAM Database Server has a configuration file, just like the
ElevateDB Server

<< I have a lot of databases that must be collected and managed by users and
it's very dangerous to work with catalogs and config files, respect of
DBISAM. >>

I'm not sure that you understand ElevateDB's architecture very well.
Configuration files do not need to be included with copies of databases,
only the catalog file and the table files need to be included.  That means
that you need exactly one more file than one you needed with DBISAM to
ensure that you have a complete copy of the database.  If you simply copy
everything that is in a database directory, you'll have everything that you
need.

<< Why you don't prepare the enterprise release with 1 file for database
that manage all within? >>

That is what the enterprise version of ElevateDB will have, but it won't be
usable in multi-user, file-sharing configurations.

<< So my question is: Using DBISAM4 C/S what penalty I have to pay in
performance and number of connected users or session, in a large internet
installation (+-300 users) respect EDB  (my last post) ? >>

I really can't answer that without knowing the specifics about the
application.  In general, I can tell you that EDB will have better
performance than DBISAM with that many users.

<< I have need (my customers need) often to change folders, substitute files
tables and other thing  that I cannot provide with EDB catalogs and
configs... >>

You can substitute table files with ElevateDB, provided that they have the
same structure as the table files that are being replaced.  The only problem
occurs when you try to copy table files with a different structure.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,


<I'm not sure that you understand ElevateDB's architecture very well.
Configuration files do not need to be included with copies of databases,
only the catalog file and the table files need to be included.  That means
that you need exactly one more file than one you needed with DBISAM to
ensure that you have a complete copy of the database.  If you simply copy
everything that is in a database directory, you'll have everything that you
need.>

Ok, this mean that I can receive only one table from customer, modify it (without alter structure) and send back without problem? Catalog file don't contain refers to data content? Only structure, relations, etc..?
(one problem already exists, but is marginal: 2 databases in the same folder...)


<< Why you don't prepare the enterprise release with 1 file for database
that manage all within? >>

<That is what the enterprise version of ElevateDB will have, but it won't be
usable in multi-user, file-sharing configurations.>
Ok! Only C/S edition!!


The true problem I have is when customers send databases for repair, modify, share, etc....
I don't speek on server edition, but LOCAL management...
With DBISAM I have to restore the files and  only set the directory for manage database. So the same database is used for all purpose...
With EDB I cannot set PATH and use it; I have to populate the config file...and this is problem; In DBISAM I collect  300 databases that have the same name (teorical), the same structure, with different directory. I must change this logic with EDB....

I don't Known well EDB, but It seem less elastic in this scenario that DBISAM....
I try to study and test better...

Thanks,
Stefano Monterisi

Stefano


>The true problem I have is when customers send databases for repair, modify, share, etc....
>I don't speek on server edition, but LOCAL management...
>With DBISAM I have to restore the files and only set the directory for manage database. So the same database is used for all purpose...
>With EDB I cannot set PATH and use it; I have to populate the config file...and this is problem; In DBISAM I collect 300 databases that have the same name (teorical), the same structure, with different directory. I must change this logic with EDB....

It sounds like you're getting very confused. If the users do not change the table structure, and all of your databases are the same structure then they should be able to simply send you the table files, and if you're willing to do a repair you probably don't even need the index file. Where the structure is different they'll need to send the appropriate table files and the catalog.

Assuming you alteady have a session set up you'll need this

CREATE DATABASE "alf"
PATH 'D:\Domestic MyM\Info'
UNENCRYPTED CATALOG

If you also have a database set up you'll use the ALTER DATABASE command.

One of the biggest differences I've found between DBISAM and ElevateDB is that you have to use SQL a lot (and I mean have to). All of the table management commands are now SQL. I was helped tremendously by the SQL history in EDBManager (one I had it pointed out to me by Tim) and will often do things through its menu to get the right syntax.

>
>I don't Known well EDB, but It seem less elastic in this scenario that DBISAM....
>I try to study and test better...

Because DBISAM carried all the information in the table itself it is certainly easier to copy stuff around and have databases spread around but ElevateDB gives a lot of benefits by switching to a catalog model. It takes time, but its worth it.

[Team Elevate]

Ok, Roy...
I am testing now and it seems all ok. There is only a little effort on
manage configs on local side....but it seems there is an advantage on switch
faster to remote...
I continue to porting the application; If I have troubles, I ask you...
Another question:
If I use the application in a local network, all work ok, because the
transport is very fast. But If I use the application over Internet, I need
to optimize better data access. In a particular situation, I need to load
several tables (kbmmemtable as child tables)  from blobs when I scroll the
table. I have noted that this is slow because the blobs are read remotely
one at time, on demand. This is an advantage when I need to access large
blobs only when I need , ma in this scenario  I need to load "all at once".
There is a way for prefetch a record with its blob in a single remote
operation?

Thanks in advance!
Stefano Monterisi

Tim,
all ok for now....
Please see my request to Roy.
Many thanks for support...

Stefano Monterisi.

Stefano


The only way I can think of to sort of do what you seem to be asking is to use a thread and to populate a local table in the background.Alternatively, if there isn't to much data involved you could use ElevateDB's streaming methods to stream the table from the remote machine to the local one. You'll have to search the ngs for this because its not anything I've ever done.

Roy Lambert [Team Elevate]

Stefano,

<< Ok, this mean that I can receive only one table from customer, modify it
(without alter structure) and send back without problem? >>

Yes, provided (as Roy said) that the database catalog that you're using on
your system matches the structure used with the table files.  If it doesn't,
then EDB will tell you, so if it works, then no problem.

<< Catalog file don't contain refers to data content? Only structure,
relations, etc..? >>

Correct.

<< (one problem already exists, but is marginal: 2 databases in the same
folder...) >>

You can't do that with DBISAM, at least not with the same table names.

<< Ok! Only C/S edition!! >>

Actually, it will do single-user and C/S, multi-user, just not multi-user
file-sharing.

<< The true problem I have is when customers send databases for repair,
modify, share, etc....
I don't speek on server edition, but LOCAL management...
With DBISAM I have to restore the files and  only set the directory for
manage database. So the same database is used for all purpose...
With EDB I cannot set PATH and use it; I have to populate the config
file...and this is problem; In DBISAM I collect  300 databases that have the
same name (teorical), the same structure, with different directory. I must
change this logic with EDB.... >>

This really depends upon whether you need to keep around copies of the
tables that customers send you.  If you don't, then just define one database
using CREATE DATABASE, make sure that the current database catalog is copied
into the database directory, and then copy the table files from customers
into the database directory as they arrive, overwriting whatever table files
currently exist there.  This is all exactly the same as with DBISAM.  The
only difference is the initial CREATE DATABASE to make sure that the
database name/path is defined in your local configuration that you use for
the customer database(s).

--
Tim Young
Elevate Software
www.elevatesoft.com

Stefano,

<< There is a way for prefetch a record with its blob in a single remote
operation? >>

Not currently, no.  However, once a BLOB is opened, it is cached on the
client side until the row is discarded due to navigation, etc.

--
Tim Young
Elevate Software
www.elevatesoft.com

All ok, Tim.
Don't worry, I am in progress with EDB....
Thanks...

Stefano Monterisi


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> ha scritto nel
messaggio news:91AD2676-FD88-4549-A5E8-CE019F8EDFEC@news.elevatesoft.com...
> Stefano,
>
> << Ok, this mean that I can receive only one table from customer, modify
> it (without alter structure) and send back without problem? >>
>
> Yes, provided (as Roy said) that the database catalog that you're using on
> your system matches the structure used with the table files.  If it
> doesn't, then EDB will tell you, so if it works, then no problem.
>
> << Catalog file don't contain refers to data content? Only structure,
> relations, etc..? >>
>
> Correct.
>
> << (one problem already exists, but is marginal: 2 databases in the same
> folder...) >>
>
> You can't do that with DBISAM, at least not with the same table names.
>
> << Ok! Only C/S edition!! >>
>
> Actually, it will do single-user and C/S, multi-user, just not multi-user
> file-sharing.
>
> << The true problem I have is when customers send databases for repair,
> modify, share, etc....
> I don't speek on server edition, but LOCAL management...
> With DBISAM I have to restore the files and  only set the directory for
> manage database. So the same database is used for all purpose...
> With EDB I cannot set PATH and use it; I have to populate the config
> file...and this is problem; In DBISAM I collect  300 databases that have
> the same name (teorical), the same structure, with different directory. I
> must change this logic with EDB.... >>
>
> This really depends upon whether you need to keep around copies of the
> tables that customers send you.  If you don't, then just define one
> database using CREATE DATABASE, make sure that the current database
> catalog is copied into the database directory, and then copy the table
> files from customers into the database directory as they arrive,
> overwriting whatever table files currently exist there.  This is all
> exactly the same as with DBISAM.  The only difference is the initial
> CREATE DATABASE to make sure that the database name/path is defined in
> your local configuration that you use for the customer database(s).
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>