c# - Client Access to SQL Server over the Internet -

Is there any feedback on the best ways to connect the client to the client to obtain any data.

Then I can say that I have no C # Datagreat view in the Winform on the internal network and I need to load it with so many data.

At present, we open a connection to the SQL Server, a component called SQLDataAdapter in which to access the data, loads a dataset and then closes the DB connection. This is using SQL Server authentication and many applications are running on the Internet connecting the same way at the same time.

So I do not want to increase security and downgrade performance. Which of these options or other options should be considered?

- Connect in the same way, but open the connection to the user's time period in the app.

- Create web server services and archive a dataset or client.

- Create a WCF server and connect to DB. (LINQ, Ident Framework, ADO.NET ...?)

- Create both WebSites and WCF servers, the client connects to WCF, which receives data from the WSE server that connects to SQL Server And the collection or dataset passes back to the client

Personally I like the last option for some reasons 1. It will be easy to take those components, which we have already created and left them in web services. 2. This will allow our ASP.NET websites to stop direct access to the database, but connect with the Web Services Server (ASMX = Good?). 3. We can better control what data is used and given outside of our network. And now we do not have to keep the connection string in our applications.

Do anyone have experience combining these options or? I am somewhat careful because I have heard horror stories about the server such that these funnels are points when no problem is directly connected to the SQL server.

Jason Stone

-

In my opinion, you need a very compelling reason to allow direct connections to your database, allowing remote SQL connections from outside your network to be a big security risk, if correctly The industry has learned hard work with SQL Slamer virus etc. ...

Winforms / Wpf Client app -> Doubles UCF -> Database works really well in the real world. Also, while hiding the usage of data behind a service for your remote apps, you can change your database and related objects without any change of customer, as long as the data shape is not close and backward.

On the flip side, any such apps that serve a lot of concurrent users from a logical example (such as web applications / sites) let them connect directly to the database.

In either example, I do not really see the value of having another set of web services to hide the database from my WCF and web application unless we talk about a huge incompatible enterprise system are doing.