Performance question

I have just upsized a FoxPro DB to MSDE.
I use a VB 6 program with ADO to access the DB.
I put the .EXE file on the server with a shortcut to it on each of the
workstations.
Performance is much worse then the FoxPro in some of the tasks.
In my investigations I found that if I put the .EXE on each workstation
performance improved 10 fold.
Can anyone explain why this happened? I would like to only have to have one
version of the .EXE floating around.
Thanks,
Darwin C. Weyh
swdev at superiorheattreat dot com
And for the spammers: dweyh@.weyh.net
The first question I would pose is:
Are you using a client side or server side cursor in your calls to the
database? Also, is your database on a network server? If so, why are you
using MSDE, why not a full blown version of SQL Server? I would guess it
would be possible to place individual instances of MSDE on local machines
which were in essence copies of each other, but it sounds convoluted.
Jamie
"Darwin Weyh" wrote:

> I have just upsized a FoxPro DB to MSDE.
> I use a VB 6 program with ADO to access the DB.
> I put the .EXE file on the server with a shortcut to it on each of the
> workstations.
> Performance is much worse then the FoxPro in some of the tasks.
> In my investigations I found that if I put the .EXE on each workstation
> performance improved 10 fold.
> Can anyone explain why this happened? I would like to only have to have one
> version of the .EXE floating around.
> Thanks,
> --
> Darwin C. Weyh
> swdev at superiorheattreat dot com
> And for the spammers: dweyh@.weyh.net
>
>
|||hi Darwin,
Darwin Weyh wrote:
> I have just upsized a FoxPro DB to MSDE.
> I use a VB 6 program with ADO to access the DB.
> I put the .EXE file on the server with a shortcut to it on each of the
> workstations.
> Performance is much worse then the FoxPro in some of the tasks.
> In my investigations I found that if I put the .EXE on each
> workstation performance improved 10 fold.
> Can anyone explain why this happened? I would like to only have to
> have one version of the .EXE floating around.
> Thanks,
you are actually killing your lan with a lot of unnecessary traffic
(application and data) and using the OSs as a terminal server...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||The MSDE resides on a SBS 2003 machine as did the file served .exe
I'm using server side cursors.
SQL Server cost more.
My original configuration used VFP files on the SBS 2003 server as did the
file served .exe.
And I used client side cursors.
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:EF072B21-7200-4D6E-B0A1-430EF776F661@.microsoft.com...[vbcol=seagreen]
> The first question I would pose is:
> Are you using a client side or server side cursor in your calls to the
> database? Also, is your database on a network server? If so, why are you
> using MSDE, why not a full blown version of SQL Server? I would guess it
> would be possible to place individual instances of MSDE on local machines
> which were in essence copies of each other, but it sounds convoluted.
> Jamie
> "Darwin Weyh" wrote: