Yes. See my previous posting. The only difference I can now see is that the db caches work if the database tables are on the same box as Sambar. In the ODBC administrator panel, you have the option of specifying another directory where the tables may reside. When Sambar was running in the sys tray (i.e. not as a service) I could pick any directory on any volume that I could connect to across our LAN. So Sambar ran as an app in the sys tray on one PC, and the database tables were on a Novell server. Worked great until Sambar dbms performance started taking a hit even for tables with only 300 rows. Now dbms is lighting fast with Sambar running as a service, but only if database tables are stored on the Sambar box.
>>> [EMAIL PROTECTED] 07/18/02 11:37PM >>> Is sambar running as a system user? Should be. On 18/Jul/2002 15:31:36, Michael Cook wrote: > Further to my previous posts on my difficulties with poor dbms performance on W2K, I >decided to run Sambar as a service bewfore doing a re-install of the OS and Sambar. >To my amazement, dbms performance is now lighting fast! However, this is only true >when using the ISQL utility in Sambar. When I run an STM script I cannot connect to >the database table. I have all my dbms caches configured as SYSTEM DSNs in the ODBC >administrator interface. So what am I missing? > ------------------------------------------------------- > To unsubscribe please go to <A TARGET="_blank" >HREF="http://www.sambar.ch/list/";>http://www.sambar.ch/list/</A> > > > > > ------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/ ------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/
