ODBC Lockup Problem?

ODBC Lockup Problem?

Post by Darlen » Sat, 12 Jan 2002 23:26:30



Hi,

I have an application program that used native drivers to
connect to MSSQL 6.5 database.  We are switching the
program to ODBC because we want to upgrade to MSSQL7.0 and
the connection performance awful and we haven't found a
fix.  

In switching to ODBC I have an application program that
uses cursors.  When I run that program that displays a
report from my workstation, it seems to lockup all other
users request until I exit the application.  Their
requests seem wait even if the information they are going
after is in another database on the server.  

Does anyone have any ideas on what might be wrong?

Any suggestion appreciated.. Thanks in advance.

 
 
 

ODBC Lockup Problem?

Post by Darlen » Sat, 12 Jan 2002 23:26:37


Hi,

I have an application program that used native drivers to
connect to MSSQL 6.5 database.  We are switching the
program to ODBC because we want to upgrade to MSSQL7.0 and
the connection performance awful and we haven't found a
fix.  

In switching to ODBC I have an application program that
uses cursors.  When I run that program that displays a
report from my workstation, it seems to lockup all other
users request until I exit the application.  Their
requests seem wait even if the information they are going
after is in another database on the server.  

Does anyone have any ideas on what might be wrong?

Any suggestion appreciated.. Thanks in advance.

 
 
 

1. ODBC lockup problems and SQL 6.5

We use an Access 97-based database product with SQL Server 6.5.  The problem
is there's times when something happens where our SQL Server will freeze up.
Not the whole server - just the SQL Server component of it.  If I go into
SQL Enterprise manager, some things I can do while it's locked up (change
users, etc.), but I can't do some things such as "Current Activity" (or
refresh "Current Activity" if that window is already open).

I can run select statements in ISQL and through SQL Trace, I found client
computers can still do SELECT-type statements just fine while it's locked
up.  The only thing anyone can't do is ODBC-related functions (as well as me
not being able to get Current Activity).   ODBC apparently locks up.

We tried reinstalling that entire server from scratch.  We even made it a
member server vs. a PDC, which it was before.   We took all extra functions
and applications off of it except it's a backup DNS server.  Still ODBC will
freeze up.

We use MDACRDST on the clients, dated 1-15-98.

Please help!!!

Thanks you.

 - can't even find out what the current activity is since the current
activity refresh feature locks up.  Can't do anything on the SQL Server
except ISQL.

2. PD DA 6.1.01 problem (SQLAny55): Problem with foreign key column modification

3. Lockup on connection to ODBC database

4. standby database with RAC cluster?

5. How to avoid lockups when using ODBC.

6. Table Information - SOS

7. Thread lockup inside ODBC when SQLCancel is used

8. Launch a a SQL SERVER DTS for VB .NET

9. Oracle ODBC Lockups

10. Urgent : ODBC Lockups

11. ODBC - D3 - SCO Lockup...Please help

12. Ver 5 Lockup Problem

13. Lockup problems...hlep....help.