![]() Now what we’re going to do is create five objects: $SqlConnection1 = New-Object ($ConnectionString) The above connection string is rather simple, but I am specifying the Application Name parameter so that we can easily parse sys.dm_exec_sessions in a below query to further prove connection pooling. ![]() I’ll start off by creating a connection string that my application will use to connect to the default instance on SQLBOX1: $ConnectionString = "data source=sqlbox1 initial catalog=master trusted_connection=true application name=ConnPoolTest" In my case, I’m going to use a PowerShell process to mimic this behavior. NET Data Provider for SQL Server (the namespace), but the ideas proposed should propagate to other popular providers used today.Īn application utilizes a provider to make connections to an instance of SQL Server. I will show an example of this below using the. ![]() ![]() The answer that enterprise DBAs need to be giving to these inquiries is that it is provider-specific. In other words, it is on the client/application side that connection pooling is handled. Far too often application teams, or network admins, or approach the DBA with questions regarding connection pooling, and whether or not it is functioning correctly or even happening. One of those aspects is connection pooling. There are a handful of questions that DBAs get in the wild that aren’t necessarily under the jurisdiction of the typical DBA.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |