Open MSSQL to the internet or implement a web service on the SQL server
I am moving forward with my Cashless Catering system, and am now planning the Sharepoint WebPart for it.
Now, the problem I have is this - creating one which is installed on a local sharepoint install, within the local network is easy. There's no issues there. However, our sharepoint install isn't local. It is provided by our LEA and as such has its own set of usernames and passwords etc...
This means I have to maintain a link within my software between the LEA provided account names and our parent database. Relatively easy to do, yes.
The big question comes to accessing the data on our network. As far as I can see it, I have a couple of choices.
1. Use a web service - which can be limited to exactly what I want to expose. Disadvantage is adding an extra layer of complexity, and therefore an extra thing to go wrong/maintain.
2. Open the MSSQL server to the internet, and using a limited user account to restrict what that user can do. Disadvantage - potentially easier to 'hack' the server, as it is a direct link to MSSQL rather than via IIS.
3. Hire teams of racing pigeons to carry the data...