[AccessD] Replication - A2K

Drew Wutka DWUTKA at marlow.com
Thu Mar 27 20:14:46 CST 2003


I realize that, I know that immediate processes will speed up, but
replication is going to add to the over all processing time.  

Drew

-----Original Message-----
From: Charlotte Foust [mailto:cfoust at infostatsystems.com]
Sent: Thursday, March 27, 2003 7:48 PM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] Replication - A2K


Drew,

That makes no sense.  It's the back end that gets replicated, which
gives the user a local backend to work with.  That has to be faster than
a LAN-based back end.  It isn't like the replicas are synced constantly.

Charlotte Foust

-----Original Message-----
From: Drew Wutka [mailto:DWUTKA at marlow.com] 
Sent: Thursday, March 27, 2003 5:37 PM
To: 'accessd at databaseadvisors.com'
Subject: RE: [AccessD] Replication - A2K


Just out of curiousity, what all have you tried to speed things up?  It
sounds like you want to replicate a database to run 'locally' on
everyone's machine.  I would be willing to be that would slow things
down on it's own, even if the db is running locally.

Are all of the users on a LAN, or are some accessing this through a VPN?
In that case I could see replication being used.

Drew

-----Original Message-----
From: John W. Colby [mailto:jcolby at colbyconsulting.com]
Sent: Thursday, March 27, 2003 7:24 PM
To: AccessD
Subject: [AccessD] Replication - A2K


I need any info / experiences anyone can share re replication.  My
insurance client has a functioning database now that is SLOOOOOooooow.
They came from a "flat file" where they had basically a single table
with 125+ fields to a fully relational FE/BE with of course much
expanded functionality - and of course the speed isn't anywhere close to
the same as the old.  No matter how you explain, the user doesn't know
what goes on behind the scenes, and doesn't care.  All they know is that
it is slower.  Plus they are adding more employees (up to about 25 now
from under 20 when I started the project - and still climbing).

They will probably go to SQl Server someday but now is not the time
(money). I have been discussing options with them and explained to the
tech contact the idea behind replication.  He has been running a FE / BE
development copy of the db on his desktop and it is about twice as fast.
Therefore he thinks that replication might solve their speed issues for
the short term (for a year or so) until such time as they could make the
move to SQL Server.

So I need info.  I have done replication one time, just on my own
system, just to see how it worked - and that was a long time ago.  So I
need to start a thread with anyone who has current experience on how to
set it up, what is involved, any good reference material to read, would
it work to merge the BE/FE back in and also replicate design changes,
etc.

Anyone with info out there?

Thanks,

John W. Colby
Colby Consulting
www.ColbyConsulting.com

----------------------------------------------------
Is email taking over your day?  Manage your time with eMailBoss. Try it
free!  http://www.eMailBoss.com


_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


More information about the AccessD mailing list