During the MVP Summit I had an opportunity to interact with members of the SQL Client team (in the SQL Server group). While I can’t talk about their future plans, I can talk about the suggestions I made:
- The SqlClient Connection close method. Today (ADO.NET 3.5) when you close a connection the connection handle is returned to the pool where it waits for another application to reuse it. When another Open is executed, the dormant Connection handle is passed to the application but only after the Connection Reset operation has been executed. See https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=420307
- SQL Server Surface Area Configuration tool should be resurrected. While some IT organizations were made nervous by this very useful tool, SQL Express and smaller org companies found this tool very useful, one-stop-gui interface to manage their instances.
- Graphical connection debugger. One of the most pervasive problems faced by developers is getting connected. We still need a GUI tool that helps developers figure out why they aren’t getting connected or show the state of connections to servers.
- Adding CommandBehavior.CloseConnection on other SqlCommand.Executexxx methods. Only the ExecuteReader supports this method which permits the developer to automatically free the owned connection while its still in scope. This addresses the pervasive problem of connection leakage.
- Faster population of Enumerate Servers list. The dialog exposed by the SqlClient data provider permits developers to expose visible servers but it takes FAR too long to populate.