[AccessD] Replication - A2K

True, replication wouldn't slow down the normal 'running' processes, but I'm
adding in the sync time to replicate it on every database.

Drew

>  -----Original Message-----
> From: 	John W. Colby [mailto:jcolby at colbyconsulting.com] 
> Sent:	Thursday, March 27, 2003 7:46 PM
> To:	accessd at databaseadvisors.com
> Subject:	RE: [AccessD] Replication - A2K
> 
> Why would the replication slow things down?  The FE/BE running locally
> speeds things up by a factor of two.  Replication simply allows me to run
> the BE/FE locally on every machine.
> 
> John W. Colby
> Colby Consulting
> www.ColbyConsulting.com
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Drew Wutka
> Sent: Thursday, March 27, 2003 8: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
> 
> 
> 
> ----------------------------------------------------
> Is email taking over your day?  Manage your time with eMailBoss.  
> Try it free!  http://www.eMailBoss.com << File: ATT109592.txt >>