Avatar of Larry Brister
Larry Brister
Flag for United States of America asked on

SQL Open Connections and MS Access front end

I am new to our company which is using MS Access as their interface with SQL database instead of Access tables. I've been brought in to move everything to Intranet Web Application.

The company has 80 employees of which about 70% at any particular time are on the MS Access system.

When I run my code below...a standard when I was checking my intranet site(s) at my previous company...I'm getting minimun of 280 and sometimes 350+ connections to the application database. For max of 60 people using system + 4 developers + any job(s) that may be running.

Is this normal for MS Access Applications?

Generally speaking on my intranet sites as I opened and closed connections I would see a maximum of 25-40 connections in a company of 250 + people. And 6 of those were my development team.


Thanks

Getting open connections
SELECT DB_NAME(dbid) as 'DbName', COUNT(dbid) as 'Connections'
   from master.dbo.sysprocesses with (nolock)
   WHERE dbid > 0 and DB_NAME(dbid) not in ('master','msdb')
   GROUP BY dbid
   ORDER BY DB_NAME(dbid)
Microsoft SQL Server 2005Microsoft Access.NET Programming

Avatar of undefined
Last Comment
Larry Brister

8/22/2022 - Mon
Ishaan Rawat

Yes. It is normal
ASKER CERTIFIED SOLUTION
Jacques Bourgeois (James Burger)

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Armen Stein - Microsoft Access MVP since 2006

I know you're planning to move everything to a web app, and that can be a lot of work.  Just so you know, a well-designed Access + SQL Server application can easily handle 50-70 users.  But it can't just used linked tables for everything - there are specific techniques that must be used.

I've written a PowerPoint presentation on this.  It's called "Best of Both Worlds" at our free J Street Downloads Page:

http://www.JStreetTech.com/downloads

It includes some thoughts on when to use SQL Server, performance and security considerations, concurrency approaches, and techniques to help everything run smoothly.

Cheers,
Armen Stein
Jacques Bourgeois (James Burger)

If the thing is going to move to the web, I do not see why Access should stay in the equation. Access used with SQL Server is only a front end. If the front end becomes a web site, Access becomes just a useless bridge that will eventually just be a handicap. The proper route would be to go straight from ASP to SQL Server.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
Armen Stein - Microsoft Access MVP since 2006

Hi James,

I don't think lrbrister is saying that Access will still be part of the new system.  They're going to replace it with a web app.  The question is about how the old Access app is using SQL Server connections, if I understand it correctly.  I just added that it's possible to use an Access/SQL app with that many users if it's done correctly.

Armen
Larry Brister

ASKER
THis put me on the right track

ADP is being used with some vba...however...connections were being left unnecessarily open.