|
Home > Archive > microsoft.public.sqlserver.server > November 2002 > SQL Server 2000 slow down in performance
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SQL Server 2000 slow down in performance
|
|
| SQLKIDA 2002-11-29, 3:23 am |
| Dear Friends
I have a small network of 24 users with three depatments.
The data is not huge, I have 2.5 GB ram on the server and
it Hardly use the 30% of the same.
But still i get the complaints from the users that the
acces to the server is slow. We ar using MS-Access as a
front end.
Please suggest what is to be done to increase the
performance.
Thanks and best regards
SQLKIDA
| |
| Tibor Karaszi 2002-11-29, 4:23 am |
| 99% of performance is how the application is written. I suggest that you get a good book on how
to use Access with SQL Server (I'm no expert myself in this area, but things like only fetch the
data you need and not the whole tables etc). And also analyze the slow queries to see if you can
create supporting indexes etc.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ublic.sqlserver
"SQLKIDA" <SG@geminicorp.be> wrote in message
news:1ec4501c29788$9fdbbe00$89
f82ecf@TK2MSFTNGXA01...
> Dear Friends
>
> I have a small network of 24 users with three depatments.
> The data is not huge, I have 2.5 GB ram on the server and
> it Hardly use the 30% of the same.
>
> But still i get the complaints from the users that the
> acces to the server is slow. We ar using MS-Access as a
> front end.
>
> Please suggest what is to be done to increase the
> performance.
>
> Thanks and best regards
> SQLKIDA
| |
| Jacco Schalkwijk 2002-11-29, 4:23 am |
| Hi,
In this scenario I would put my money on the Access front end causing the
performance problems.
Do you use data projects (in Access 2000 or higher)? That should give a
decent performance, as all the work is done on the server.
But if you have a few SQL statements in Access itself it will pull all the
rows in the table over the network, and process them on the client machine,
and that will hurt performance on any but the smallest tables (say up to 100
rows).
Jacco
"SQLKIDA" <SG@geminicorp.be> wrote in message
news:1ec4501c29788$9fdbbe00$89
f82ecf@TK2MSFTNGXA01...
> Dear Friends
>
> I have a small network of 24 users with three depatments.
> The data is not huge, I have 2.5 GB ram on the server and
> it Hardly use the 30% of the same.
>
> But still i get the complaints from the users that the
> acces to the server is slow. We ar using MS-Access as a
> front end.
>
> Please suggest what is to be done to increase the
> performance.
>
> Thanks and best regards
> SQLKIDA
| |
| Brad Wartman 2002-11-30, 8:23 am |
| Access does a lot of client-side processing, so I'd look there first.
Rewriting the Access app to use more server-side processing (e.g.
stored procedures & views) will help but the best thing you could do
to increase performance is to rewrite the app in VB.
On Fri, 29 Nov 2002 01:20:57 -0800, "SQLKIDA" <SG@geminicorp.be>
wrote:
>Dear Friends
>
>I have a small network of 24 users with three depatments.
>The data is not huge, I have 2.5 GB ram on the server and
>it Hardly use the 30% of the same.
>
>But still i get the complaints from the users that the
>acces to the server is slow. We ar using MS-Access as a
>front end.
>
>Please suggest what is to be done to increase the
>performance.
>
>Thanks and best regards
>SQLKIDA
|
|
|
|
|