.NET Remoting Server Windows Service Performance Problem

[Buzz Bonner]

Hi,

We have developed a distributed system that uses multiple .NET remoting
servers hosted by Windows Services. However, the single server used for
performing all database access using ADO.NET has very poor performance when
using the 'Release' version of the assembly. When using the 'Debug' version
there seems to be no problem.

The release version seems to function reasonally well until we make a few
database calls in quick succession. At this time the CPU usage increases to
99%, and remains there until the process is destroyed.

We are using Access 2002 as our database and standard .NET database access
components.

Is this a known problem?

Regards,

Mark

[Peter Bromberg [C# MVP]]

Buzz,
Using MS Access as a multi-user production database is definitely a "known
problem".

You'd be better served, assuming you can't afford or are not ready to
license SQL Server, to use the free MSDE version which scales very nicely
and can be distributed by VS.NET Developers.
--Peter

"Buzz Bonner" <bu********@btopenworld.com> wrote in message
news:c0**********@hercules.btinternet.com...

Hi,

We have developed a distributed system that uses multiple .NET remoting
servers hosted by Windows Services. However, the single server used for
performing all database access using ADO.NET has very poor performance when using the 'Release' version of the assembly. When using the 'Debug' version there seems to be no problem.

The release version seems to function reasonally well until we make a few
database calls in quick succession. At this time the CPU usage increases to 99%, and remains there until the process is destroyed.

We are using Access 2002 as our database and standard .NET database access
components.

Is this a known problem?

Regards,

Mark