SQL 2000 Timeout Issues Since Converting from BDE to ADO

From: brag (ggroshner_at_fnis.com)
Date: 11/05/03 

Date: Tue, 4 Nov 2003 20:29:39 -0500

We have a large, multi-user (500+) application which runs against either SQL
2000 or Oracle which we recently converted to ADO from BDE. BDE ran fine and
provided very good performance, up to 3000 users. We converted the
application to use ADO basically by converting the BDE components to ADO
components. The application runs fine with smaller numbers of users, but as
users increase (even as small as 50 concurrent) we run into severe
performance degradation and finally timeout issues. It seems like there are
some blocking issues going on between users at the SQL 2000 level. A very
odd thing is that these issues do NOT occur when connected to Oracle, only
when connected to SQL 2000 (the application will run against either database
without recompile - we just change ADO connection parameters). Taking a
flyer, we converted our SELECT statements to use the (NOLOCK) hint on SQL
Server and that seems to resolve the issue. It doesn't seem like we should
have to do that. We use disconnected dataset components exclusively, which
on BDE did not appear to create any locks on the SQL 2000 side. ADO seems
like it does. Any ideas? Any suggestions would be appreciated. Thanks in
advance.

Relevant Pages

  • Re: What Database model should I use?
    ... If you want to upgrade to a serious DBMS you did not list SQL Server. ... Porting Access/JET databases can be done with the upsizing wizard as ... I would also read about coding ADO a bit more. ... > But I am having a problem converting the MS Access JET databases. ...
    (microsoft.public.vb.database)
  • Re: SQL 2000 Timeout Issues Since Converting from BDE to ADO
    ... > 2000 or Oracle which we recently converted to ADO from BDE. ... > application to use ADO basically by converting the BDE components to ADO ...
    (borland.public.delphi.database.ado)
  • Re: ADODataset.CreateDataset
    ... Especcially because if using SQL, a lot of data is entered twice, as the table has persistance columns. ... >>But how to get this memory table into a physical database, using ADO? ... with BDE it worked directly to the mdb file. ... ADO does not have a capability to create ...
    (borland.public.delphi.database.ado)
  • ADO Newbie Question
    ... MS SQL Server 2005 and ADO. ... I am working on some research to convert an application from BDE to ADO. ...
    (borland.public.delphi.database.ado)
  • Re: BDE vs ADO
    ... ok, thanks, i had a tool having db connectivity in bde and i need to evaluate ... the performance of the tool by converting it to ado. ... > Easy - don't start ANY applications using the BDE. ...
    (borland.public.delphi.database.ado)