When connecting to SQL Server you will see that establishing the connection is one of those things that takes the most. Sharing the connection enables your application to connect just once and thus improving performance while opening other views.

>Does anyone have any experience with optimizing the number of connections to SQL Server? Someone suggested that all views should share a single connection for optimization, but if you have too many views sharing the same connection, it may bog down. Also, I've heard of third party tools for managing connections. Normally, I just create a remote view and let her rip. Is there any rule of thumb here?