I have a tiny little bit of experience with linux, but I am still very green. I am attempting to find a replacement database/Contact Manager to replace ACT 6. The newer versions of ACT require winbloz server 2003....no thanx...

I have started personally using Outlook Business Contact Manager, does anyone have any luck with it? It automatically installs an sql server on the local workstation, and allows sharing of the database in the lan. This leads me to believe it could be hosted on my fc3 server. I would prefer not to have the primary databases/emails/etc stored on the local machines for security, backup, and lan bandwidth reasons. Plus if a machine is not online or is out of the office I could not be without the info.

Now to my question, I have an FC3 server, and I would like to share the databases from that location, as well as be able to back them up to a workstation via retrospect network/server edition. As far as I can tell sql has not been installed on that server. I am guessing I could use yum install mysql and it would install? The only issue is that this is a production machine and I can only have it down for an evening here or there, or a weekend. The only other service it provides is smb shares.

Help out the ! Thanx...

I haven't used Outlook Business Contact Manager, but it probably uses a version of the "Microsoft SQL Server". This being Microsoft, I wouldn't expect the product to work with any other brand of SQL database.

Personally, I would suggest either looking for an Open Source (or at least Linux friendly) application, or accept the requirements for whatever Windows-based app you choose. If you are prepared to live without Outlook integration, then there is likely to be a Web application that will provide you with addressbook/CRM functionality. Groupware apps like eGroupware or the Horde are most likely to have modules for this kind of thing.

I'd also suggest doing at least one trial-run on a virtual machine (VMware player image) or test machine, and using that test system for a couple of days. Document the steps that you took to get it all working and configured to your satisfaction. You can then confidently reproduce the steps on the live system and even copy databases, config files etc. across to speed up the process.

FWIW, you only ever need to down a Linux box to upgrade the kernel - you can happily install and configure a bunch of new software whilst the existing services tick along. Although it's best to schedule downtime, if only to ensure that people don't distract you whilst you are working .