we are currently building an online solution that has a number of parts. It is built up of three parts that interact with each other. One part relies on the other to run else it fails.
Due to this we want to host those two parts at the client end with the third part running on a hosted Remote App server. (so it is accessible anywhere).
The server infrastructure of this program is SQL Server and it runs on an SQL Database. One of the items relies on that SQL Server so we belive it needs to be in the same network so that if the internet drops, the program does not shut down.
However the RemoteApp program also requires to access the SQL server to function but it does not function 24/7, only on demand.
The current idea is that when the client connects to the RemoteApp server a link is established. It appears that link works much like windows networking as if you enable all options such as ports and drives you can see the computer name in the hard disk list etc to save locally on the client.
Am i right in thinking that once this link is established that the RemoteApp server could access that clients SQL instance by either the following (as long as the user selects to open ports on the Remote App login page)
and if i am not right, is there any other way you can suggest to enable this to work?