Creation of a web service to update client Access databases from central SQL database
Budget: $250 – $750 AUD
We have a SQL database containing information which is updated regularly, and needs certain information updated into client Access databases.
Ideally a SQL job or web service etc. that can poll our SQL database looking for relevant data to be updated on the customers ends, then connect to the access DB and update the information in the appropriate fields at the customer end. We would also like for the service to have to authenticate with a DB user (same user on each DB).
Very open to solution options based on your knowledge. After something quick and simple which will perform the above function reliably.
Considerations:
1. Keep it simple, prefer not to have to install anything at client end.
2. Prefer polling at server end, and pushing to client DB
3. Prefer web protocols, keep it simple for firewalls
4. Would like the option to authenticate using a specified username/password for the push
5. Server DB will have certain fields with certain information that needs to be pushed to the client. Client will be identifiable within the server DB.
6. Need to be able to map the client to their IP address for the communications to happen (assuming it will be IP based)
7. There is no PII or other senstive information involved.
Ideally a SQL job or web service etc. that can poll our SQL database looking for relevant data to be updated on the customers ends, then connect to the access DB and update the information in the appropriate fields at the customer end. We would also like for the service to have to authenticate with a DB user (same user on each DB).
Very open to solution options based on your knowledge. After something quick and simple which will perform the above function reliably.
Considerations:
1. Keep it simple, prefer not to have to install anything at client end.
2. Prefer polling at server end, and pushing to client DB
3. Prefer web protocols, keep it simple for firewalls
4. Would like the option to authenticate using a specified username/password for the push
5. Server DB will have certain fields with certain information that needs to be pushed to the client. Client will be identifiable within the server DB.
6. Need to be able to map the client to their IP address for the communications to happen (assuming it will be IP based)
7. There is no PII or other senstive information involved.