Import Echange 2003 Public folder information into a SQL 2005 DB table

We have an internally developed transaction tracker that is built on a web front end and a SQL back end (Enterprise 2005).  This tracker keeps tracker of deals, contracts in-force, items to be looked at and worked out and then where monthly notices need to be sent to confirm receipt of payments.  The solution works well and integrates with many different database systems that have been purchased or forced on the company.

The function that the developers are trying to implement now is to use a standing address book with contact information containing standard outlook fields and some user defined fields (like "does client get a monthly report" tick yes, blank no).  The contacts are stored in an Exchange 2003 Enterprise Public Folder.

We were looking at a product like "Prophet", which is a full blown low-level CRM system, to pull data from the Public Folders and then push out data into the SQL server, generating a unique GUID for each contact record and such.  

The issue is, it seems a waste to use this system as just a courier between Exchange Public Folder and the SQL DB.

Is there a way to:

1. Do a single export of the public folder to a SQL table, retaining all (or a defined list) of the Outlook fields?
2. Have a schedule event where the data from the PF gets updated to the SQL table, either by a trigger when a change is made or on an hourly time setting?

The developers are not asking for the data to be updated in the web form.  The only place that we need to update the contact information is in the public folder.  A synchronization process is required, as well as the creation a a unique GUID for each contact.

Help on how to do this, being pointed to a KB or white paper or products that might assist are all welcome.

Thank you.
hglobusAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AbhijeetNigamCommented:
Exchange Uses Jet Engine and SQL database use there own. I haven't seen/heard about exporting data from PF directly to SQL however I know that using WMI scripting you can create a tool to export data and from Exchange and put it to SQL database.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.