[AccessD] Replication - A2K

Hi John:

I recently convinced a client to go to a SQL2000 BE with a 12
user/connection license. The price was only $1600.00 CAN. Not at all
expensive considering the features and performance boost. SQL of course
handles everything, row-locking, all the queries, backups even replication.
The performance is awesome and they are still under the delusion that I am a
god...that will pass quick enough.

They have about 30 potential users. This should be no problem as I just
finished on SQL7, after five years, on an off-and-on government contract and
they were a 10 user/connection license and 65 users, province wide. The
application had to be designed with these limitations in mind but SQL worked
amazingly well. Time-outs were very rare.

Sadly, the application has just been replaced with a massive Oracle system,
covering the whole Ministry, implemented by an equally massive System House.
The branch client fought hard to keep their program but...

My recommendation is to try and convince them to go SQL. If they wouldn't
pay for MS SQL maybe an Access, Apache and MySQL combo will be the ticket.
Apache and MySQL are free and runs on NT, 2000 and even Windows98. :-| (The
latter is an unsubstantiated statement from a acquaintance.) The replication
issue is unmanaged but a Windows2000 server has that functionality built
in...I have read about it but never tried it.

Hope this helps
Jim
Creative Systems Design

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of John W. Colby
Sent: Thursday, March 27, 2003 5: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