MS Access connections issue with SQL server

Question

5.00/5 (3 votes)

See more:

SQL-server-2000

, +

Hello All,

We are facing an issue with MS access ADP project (SQL SERVER 2000 on backend) in production environment. Currently 20 users are using the application and they have their own copies of access application, when any user opens the application it creates three new connections with the database and keep them in sleeping status. Activity monitor shows the following processes in sleeping state,

1)

SQL

SET NO_BROWSETABLE ON

2)

SQL

select object_name(id), user_name(uid), ObjectProperty(id, N'IsScalarFunction'), ObjectProperty(id, N'IsInlineFunction'), ObjectProperty(id, N'IsMSShipped'), ObjectProperty(id, N'IsSchemaBound') from sysobjects where type = N'TF' and permissions(id) & 4096 <> 0

3)

SQL

SET LANGUAGE us_english

When all users open their application number of processes reach to 60 and sql server got struck. Is their any way to minimize the number of connections?

Posted 24-Feb-11 6:40am

khurem

Updated 24-Feb-11 6:52am

Henry Minute

v2

Add a Solution

Comments

Zamarrud 24-Feb-11 13:59pm

I am also facing the above issue.

Sunasara Imdadhusen 25-Feb-11 0:20am

You should close connection whenever your task is done
e.g.
Con.Open();
Cmd.ExecuteNonQuery("DELETE FROM EMP",Con);
Con.Close();

Thanks,

khurem 25-Feb-11 2:27am

Sunasara,

This problem occurs at application startup

Thanks,

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

sairam.bhat · Answer 1 · 2011-03-17T23:04:00

Solution 1

see this link it may help u
http://www.mssqltips.com/tip.asp?tip=1470[^]

Posted 17-Mar-11 23:04pm

sairam.bhat