I am building a desktop app with vb.net and i want the sql server database to be hosted online so anybody anywhere can assess the database through d vb.net software. Please does that means i will embrace cloud computing?

What is the best way of achieving that ?

Thanks

Dear Walterjnr,

The architecture behind this kind of design is flawed and may be impractically to implement.

SQL Server is not build to act like a web server.

One of the issues with this your line of thought is that Sql Server is configured by most hosts to accept 1 or 2 simultaneous connections per database.

As u plan to distribute your client VB.net app to many users on different machines and Ip credentials, the vb.net will be creating multiple instances of ADO.net connections to the database. This can lead to performance penalties and security issues as your connection string has a large surface area for hacking exploits.

In the alternative you can create a data layer vb.net application (server) to talk to the db using 1 sql server connection instance. Your VB.net apps distributed here and there can feed the data layer application and retrieve the required information from the db. This is a better approach

Thanks

Simply put the the database behind a web service (xml web service, WCF service or ASP.NET Web API), and consume the service from any type of application (windows, mobile, web, etc.). The service should be hosted on the internet (on a shared host, VPS, Dedicated Server, Cloud (Azure, AWS, etc.)). This way, your windows application installed on any desktop anywhere in the world with internet connection can consume the web service for its normal operation.

The choice of web host selected will depend on a lot of factors. So choose appropriately based on your current need.

Bros1:
Dear Walterjnr,

The architecture behind this kind of design is flawed and may be impractically to implement.

SQL Server is not build to act like a web server.

One of the issues with this your line of thought is that Sql Server is configured by most hosts to accept 1 or 2 simultaneous connections per database.

As u plan to distribute your client VB.net app to many users on different machines and Ip credentials, the vb.net will be creating multiple instances of ADO.net connections to the database. This can lead to performance penalties and security issues as your connection string has a large surface area for hacking exploits.

In the alternative you can create a data layer vb.net application (server) to talk to the db using 1 sql server connection instance. Your VB.net apps distributed here and there can feed the data layer application and retrieve the required information from the db. This is a better approach

Thanks

Thanks man like this.