[AccessD] Performance Access FE and SQL server BE [help!]

HI Jeanine 

I don't know the network situation at your site, but looking at the
information you give me I would check some basic network issues (name
resolution / default gateways).

Espicaly name resolution.
What kind of name resolution do you use in your network.
WINS, DNS or none (Browser)?

It's sound to me that your app has dificulties finding the route to the
database server.

You could try for test on one machine to replace the name of the server
with the IP address. This does not always help because some apps replace
the ip address by the name.
But in case it does help, your are certain you have a naming resolution
problem.

Erwin

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
(AccessD)
Sent: Wednesday, December 17, 2003 2:28 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Performance Access FE and SQL server BE [help!]

Hi Jeanine:

You wouldn't have a time-limited version of MSSQL would you?

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of
Jeanine.Scott at wellsfargo.com
Sent: Tuesday, December 16, 2003 8:06 AM
To: accessd at databaseadvisors.com
Subject: [AccessD] Performance Access FE and SQL server BE [help!]


Performance Access FE and SQL server BE [help!] New SQL database.
Existing Access97 app connects to the SQL db via a dsnless connection
using NT authentication. Application resides on client.

There are approx 15 users in the app. The backend data is about a gig.
The application is code heavy. Almost all the processes are ADO direct
calls.
The command and connection timeout are both set at 5000.

Great performance for the first 4 days. Last Tuesday the performance
started to slow and from then to now we are alternating between
acceptable although not great preformance to a crawl speed (7-10
minutes!). I have done the
following:

1.) reinstalled MDAC
2.) reinstalled Access
3.) compacted and repaired the front end app
4.) rebuilt the indexes on SQL
5.) had a trace put on to see if there are any locking issues (there are
not)
6.) had a network sniffer put on to determine bandwidth utilization. 25%
utilization no packets being dropped.
7.) checked utilization on the server (10% utilization most of the time)
8.) ruled out any type of SMS issue (one of the errors pointed me in
this
direction)

Some of the errors we have received have been:

* login failed for user [null]: not a trusted sql connection. (this is
after they have logged in and recordsets/data has been returned from the
server.)

* DBNETLIB connection read. recv(). General network error check your
network documentation.

* timeout expired and then under that is the following "general network
error: check your network documentation"

Can anyone help? If you have any ideas on anything to do with the SQL
server or network please let me know what I should say to the DBA and
the network contact.

Thank you!!!!

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com