Hi Team,
A couple of curiosity questions if I may..
1.  How much usage is made of the directory in the 'TempTablesPath'?  If the Apps & main Database are installed on a Server and the User calls the Apps via a shortcut, is there a performance benefit to having the 'TemTablesPath' on the Users PC?  i.e. 'C:\TemTables'.  Is there any down side to this?

2.  ConfigPath & ConfigMemory.  I can see how ConfigPath gets filled, how does ConfigMemory get filled?  Is it on the Server or Users PC?  How does it get refilled after a restart?  Pros & Cons of each mode?

Regards & TIA,
Ian

Ian,

<< 1.  How much usage is made of the directory in the 'TempTablesPath'?  If the Apps & main Database are installed on a Server and the User calls the Apps via a shortcut, is there a performance benefit to having
the 'TemTablesPath' on the Users PC?  i.e. 'C:\TemTables'.  Is there any down side to this? >>

The TempTablesPath property will default to the current user account's local temporary tables path, so in most cases you don't need to do anything with it.  This is one of the reasons why I made it public instead of published recently.

<< 2.  ConfigPath & ConfigMemory.  I can see how ConfigPath gets filled, how does ConfigMemory get filled?  Is it on the Server or Users PC?  How does it get refilled after a restart?  Pros & Cons of each mode? >>

I don't know what you mean by "filled" ?  Just like any other property setting, it is controlled by either a) your application, for local sessions, or by the EDB Server settings, for remote sessions.

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

Ian,

<< 1.  How much usage is made of the directory in the 'TempTablesPath'?  If the Apps & main Database are installed on a Server and the User calls the Apps via a shortcut, is there a performance benefit to having
the 'TemTablesPath' on the Users PC?  i.e. 'C:\TemTables'.  Is there any down side to this? >>

<<<  The TempTablesPath property will default to the current user account's local temporary tables path, so in most cases you don't need to do anything with it.  This is one of the reasons why I made it public instead of published recently.  >>>

IB - Sorry Tim, reflecting my lack of understanding.."current user account's local temporary tables path" - Is that their PC/wkstn Temp pah or the EDB User account Temp Path?

<< 2.  ConfigPath & ConfigMemory.  I can see how ConfigPath gets filled, how does ConfigMemory get filled?  Is it on the Server or Users PC?  How does it get refilled after a restart?  Pros & Cons of each mode? >>

<<<  I don't know what you mean by "filled" ?  Just like any other property setting, it is controlled by either a) your application, for local sessions, or by the EDB Server settings, for remote sessions.  >>>

IB - Sorry, my poor wording -  Let's start with ConfigPath - As I understand att - ConfigPath points to EDBConfig.EDBCfg and is a physical file and gets config info put into it.  When is that config info put into it?


Tim Young
Elevate Software
www.elevatesoft.com

Ian

>>IB - Sorry, my poor wording -  Let's start with ConfigPath - As I understand att - ConfigPath points to >>EDBConfig.EDBCfg and is a physical file and gets config info put into it.  When is that config info put into it?


As far as I understand it the The EDB Config file holds all the database meta data, such as details of JOBs, STOREs, Databases. I think this file changes whenever you ALTER or CREATE one of these objects.

The EDB Config file may also contain some data about the actual data-tables, I'm not sure.