GoldyLock
asked on
Scheduled task for Web services - SQL Server
Hi,
I need to set up a scheduled task for retrieving information from a web service to enter the information in a SQL server database. What is the best way of setting this up when looking at security aspects. I have to do exports as wel as imports to the SQL server. I preferably want to set it up in c#.
thanks, GL
I need to set up a scheduled task for retrieving information from a web service to enter the information in a SQL server database. What is the best way of setting this up when looking at security aspects. I have to do exports as wel as imports to the SQL server. I preferably want to set it up in c#.
thanks, GL
This is a very broad and general question so I'm not sure you going to get any answers your looking for.
ASKER
I have slowly realised that, since this is my first answer ;-)
Since I preferably wanted to do it with C#, I placed it here, but indead it's not a specifiek code question. Should I rather place it under security? All I wanted to know was actually if a C# executable would be a suitable solution or if it would come with security aspects?
Thanks, GL
Since I preferably wanted to do it with C#, I placed it here, but indead it's not a specifiek code question. Should I rather place it under security? All I wanted to know was actually if a C# executable would be a suitable solution or if it would come with security aspects?
Thanks, GL
GL,
This is a long shot, as you say it is a broad question.
The solution depends on exactly what you are trying to do. You say "retrieving from a web service": I take it you mean pulling data from an external web service on a regular basis into your SQL server? If so then you should be looking at setting up a windows service to interact with the web service, and enter the data into the SQL server via storeed procedures. In terms of security this is fine; the windows service can be run on a minimum permissions account, which will only have permissions on your SQL server to run the insert queries that it needs to.
The bit I don't understand is where you talk about exports: do you mean that this web service is going to then receive data from the web service? If so that implies that people are using the web service to both push data into the sql database and pull it out again? If that is the case it would be more appropriate to link the web service to the database using a data access layer rather than periodically sync the database and web service?
Andy
This is a long shot, as you say it is a broad question.
The solution depends on exactly what you are trying to do. You say "retrieving from a web service": I take it you mean pulling data from an external web service on a regular basis into your SQL server? If so then you should be looking at setting up a windows service to interact with the web service, and enter the data into the SQL server via storeed procedures. In terms of security this is fine; the windows service can be run on a minimum permissions account, which will only have permissions on your SQL server to run the insert queries that it needs to.
The bit I don't understand is where you talk about exports: do you mean that this web service is going to then receive data from the web service? If so that implies that people are using the web service to both push data into the sql database and pull it out again? If that is the case it would be more appropriate to link the web service to the database using a data access layer rather than periodically sync the database and web service?
Andy
ASKER
Hi Andy,
This is what needs to happen:
exports (one time per 24 hours):
data from internal DB gets exported to a external web service that will update the information in a 3rd party application.
(third party is owner of web services)
imports (one time per 24 hours) :
data from the external web services gets retrieved and placed in the internal DB.
Basically a synchronization between two systems.
Help me out a bit more and the points are sure yours.
thanks, GL
This is what needs to happen:
exports (one time per 24 hours):
data from internal DB gets exported to a external web service that will update the information in a 3rd party application.
(third party is owner of web services)
imports (one time per 24 hours) :
data from the external web services gets retrieved and placed in the internal DB.
Basically a synchronization between two systems.
Help me out a bit more and the points are sure yours.
thanks, GL
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Thanks Andy,
and you're right, the 3rd party's application and web services will stay as implemented. Your answer is what I looked for.
and you're right, the 3rd party's application and web services will stay as implemented. Your answer is what I looked for.