Hi All,

One of our client has serious problems with their DBIsam based software
running on a Windwos 2003 Small Business Server Premium.

the server is quite powerful, Dual Xeon 3.2 GHz with 15k Rpm Scsi Drives for
4 users!!! at the same time it takes 15 seconds to open the application.
After some testing we came to conclusion that there is a conflict with a
number of services, but we don't know why.

What I need to establish first if this is an inherent problem with SBS and
DBISam or it is just a one off unfortunate mistery?

If anyone has this setup running fine, please let me know.

!!!! I am only interested in SBS 2003 Premium !

TIA,

Tom

Hi Tom,

My customer is running a DBISAM server on SBS2003 Premium Edition. Initially, we were using Routing & Remote Access for the firewall/NAT but later installed ISA server. During this
period the initial server has been replaced with a more modern one. Apart from the issues I reported in another thread (strange crashes apparently linked to trigger code in the server) we
have had no problems with performance over a LAN. However, we are running a client/server model with the DBISAM server running on the SBS2K3 box and 5 client applications running on
workstations over the LAN and 20 client applications running over the Internet. The Internet clients are a bit slow because the server only has a 128kb/s outgoing link.

It's not clear to me exactly what your set up is. It sounds like you have the database and the application on the same SBS2K3 box but you don't say if it is a shared file or client/server
implementation. My customer does have a client application on the server itself but this is only used for testing and maintenance not for production. However the performance of that
application is also OK. So I'd have to say that there are no inherent SBS2K3 problems that I am aware of.

It may well be something the application itself is doing (especially on startup) that conflicts with SBS2K3 and may not have anything to do with DBISAM at all.

I think somebody else might have suggested that you download DBSYS from this site and run it (on your server) to perform queries on your database. If it performs well then it may indicate
a problem with your application itself.

Hi Tony,

Sorry for not making all clear. the application is client/server, the server
runs the DB and the client machines run the App.

The app was only installed on the server to see if we can narrow down the
cause, take out the network from the equation.

Since I haven't done any work with DBIsam, I am not really up to the level
to do queries, in other words it is outside of my boundaries but I try
to gather soe info to work out what is the best solution.

My primary aim with this thread is to establish that the type of server, out
of the box has no problems with the DBIsam server. This is something that I
beleive, but want to hear from others too.

The setup of the server is pretty standard, it is kind of out of the box,
standard install.  The logic sais, if others running the same default setup
with no problem, than we must have a problem with the istalled image,
something is corrupted, or who knows...so it is worth trying to reinstall as
it likely to fix the problem.

Anyway, many thanks for your help

Regards,

Tom






"Tony Pomfrett" <tonyp@aline.com.au> wrote in message
news:681658D1-A466-40DD-9E1F-EDDC6A62F9E7@news.elevatesoft.com...
> Hi Tom,
>
> My customer is running a DBISAM server on SBS2003 Premium Edition.
> Initially, we were using Routing & Remote Access for the firewall/NAT but
> later installed ISA server. During this
> period the initial server has been replaced with a more modern one. Apart
> from the issues I reported in another thread (strange crashes apparently
> linked to trigger code in the server) we
> have had no problems with performance over a LAN. However, we are running
> a client/server model with the DBISAM server running on the SBS2K3 box and
> 5 client applications running on
> workstations over the LAN and 20 client applications running over the
> Internet. The Internet clients are a bit slow because the server only has
> a 128kb/s outgoing link.
>
> It's not clear to me exactly what your set up is. It sounds like you have
> the database and the application on the same SBS2K3 box but you don't say
> if it is a shared file or client/server
> implementation. My customer does have a client application on the server
> itself but this is only used for testing and maintenance not for
> production. However the performance of that
> application is also OK. So I'd have to say that there are no inherent
> SBS2K3 problems that I am aware of.
>
> It may well be something the application itself is doing (especially on
> startup) that conflicts with SBS2K3 and may not have anything to do with
> DBISAM at all.
>