RE: SQL Server s-l-o-w to connect to with Access DB

#1

Hi Andrew,

From your description, "When the users first open a form, it takes a couple
of minutes before anything happens". I would take the following approach to
check if the problem is because the connectivity or the Access form has
performed some operations that need time.
1. I would check if the connectivity from Access to SQL Server 2000 is
slow. On the Access database computer, I would install Query Analyzer,
connect to SQL Server 2000 and run some simple query (e.g. select * from
sysobjects). If it is very slow, I would troubleshoot slow connectivity
problem first.
2. If the speed is good, I would check what the Access form does and check
if the query run in the form is the cause of slowness.

I would use the methods in the following article.
224587.KB.EN-US INF: Troubleshooting Application Performance with SQL Ser
http://support.microsoft.com/default...B;EN-US;224587

This posting is provided "AS IS" with no warranties, and confers no rights.

Regards,

Bill Cheng
Microsoft Support Engineer
--------------------

Quote:

From: "Andrew Kidd" <andrew (AT) nospam (DOT) com
Subject: SQL Server s-l-o-w to connect to with Access DB
Date: Wed, 2 Jul 2003 09:57:55 +0100
Lines: 83
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0014_01C34080.690A4C60"
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <u4x96dHQDHA.1556 (AT) TK2MSFTNGP10 (DOT) phx.gbl
Newsgroups:
microsoft.public.sqlserver.clients,microsoft.publi c.sqlserver.odbc
NNTP-Posting-Host: host217-35-38-237.in-addr.btopenworld.com 217.35.38.237
Path: cpmsftngxa09.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP10.phx.gbl
Xref: cpmsftngxa09.phx.gbl microsoft.public.sqlserver.odbc:1096
microsoft.public.sqlserver.clients:1324
X-Tomcat-NG: microsoft.public.sqlserver.clients

Hi,
I've upsized an Access 2000 database to SQL Server 2000 and the database
is now split into front-end (Access .mdb) and back-end (SQL Server),

connected via an ODBC File DSN.

Quote:

When the users first open a form, it takes a couple of minutes before
anything happens, but after a while everything runs normally.
The network consists of several Windows 2000 Pro PCs all connected via a
switch to a Dell SBS 2000 Server, with 512Mb RAM.
Is there anything obvious that I've done wrong or should be looking at?
The same Access front-end and SQL back-end running on my SBS 2000 network
runs fine right from the off - I'm stumped...!
Thanks in advance for any advice.
Regards,
Andy

#2

Hi Bill,

Thanks for the reply - I'll go through these options.

Andy

"Bill Cheng [MSFT]" <billchng (AT) online (DOT) microsoft.com> wrote

Quote:

Hi Andrew,

From your description, "When the users first open a form, it takes a
couple
of minutes before anything happens". I would take the following approach
to
check if the problem is because the connectivity or the Access form has
performed some operations that need time.
1. I would check if the connectivity from Access to SQL Server 2000 is
slow. On the Access database computer, I would install Query Analyzer,
connect to SQL Server 2000 and run some simple query (e.g. select * from
sysobjects). If it is very slow, I would troubleshoot slow connectivity
problem first.
2. If the speed is good, I would check what the Access form does and check
if the query run in the form is the cause of slowness.

I would use the methods in the following article.
224587.KB.EN-US INF: Troubleshooting Application Performance with SQL Ser
http://support.microsoft.com/default...B;EN-US;224587

This posting is provided "AS IS" with no warranties, and confers no
rights.

Regards,

Bill Cheng
Microsoft Support Engineer
--------------------
| From: "Andrew Kidd" <andrew (AT) nospam (DOT) com
| Subject: SQL Server s-l-o-w to connect to with Access DB
| Date: Wed, 2 Jul 2003 09:57:55 +0100
| Lines: 83
| MIME-Version: 1.0
| Content-Type: multipart/alternative;
| boundary="----=_NextPart_000_0014_01C34080.690A4C60"
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <u4x96dHQDHA.1556 (AT) TK2MSFTNGP10 (DOT) phx.gbl
| Newsgroups:
microsoft.public.sqlserver.clients,microsoft.publi c.sqlserver.odbc
| NNTP-Posting-Host: host217-35-38-237.in-addr.btopenworld.com
217.35.38.237
| Path: cpmsftngxa09.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP10.phx.gbl
| Xref: cpmsftngxa09.phx.gbl microsoft.public.sqlserver.odbc:1096
microsoft.public.sqlserver.clients:1324
| X-Tomcat-NG: microsoft.public.sqlserver.clients
|
| Hi,
| I've upsized an Access 2000 database to SQL Server 2000 and the database
is now split into front-end (Access .mdb) and back-end (SQL Server),
connected via an ODBC File DSN.
| When the users first open a form, it takes a couple of minutes before
anything happens, but after a while everything runs normally.
| The network consists of several Windows 2000 Pro PCs all connected via a
switch to a Dell SBS 2000 Server, with 512Mb RAM.
| Is there anything obvious that I've done wrong or should be looking at?
| The same Access front-end and SQL back-end running on my SBS 2000
network
runs fine right from the off - I'm stumped...!
| Thanks in advance for any advice.
| Regards,
| Andy
|

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

RE: SQL Server s-l-o-w to connect to with Access DB

microsoft.public.sqlserver.clients microsoft.public.sqlserver.clients

RE: SQL Server s-l-o-w to connect to with Access DB - 07-04-2003 , 10:21 AM

Re: SQL Server s-l-o-w to connect to with Access DB - 07-09-2003 , 04:54 PM