D
dwhalen
Hello all.
I have been debugging with a Connection pool overflow issue, and I'm
seeing something very unusual.
Using performance monitor, I am tracking the number of Current Pooled
Connections. The number stays fairly low as I connect to the database,
execute my query, and fill my DataTable.
However, once I evoke DataBind() for my datagrid, the number of pooled
connections shoots up an amount equal to the number of rows in the
grid! So, in my case I'm showing 20 rows, so 20 additional connections
get used in the pool.
I'm at a real loss to understand this one. Why would DataBinding use
connections at all if I already have a filled DataTable?
Thanks in advance for your insights/opinions/etc.
DW
I have been debugging with a Connection pool overflow issue, and I'm
seeing something very unusual.
Using performance monitor, I am tracking the number of Current Pooled
Connections. The number stays fairly low as I connect to the database,
execute my query, and fill my DataTable.
However, once I evoke DataBind() for my datagrid, the number of pooled
connections shoots up an amount equal to the number of rows in the
grid! So, in my case I'm showing 20 rows, so 20 additional connections
get used in the pool.
I'm at a real loss to understand this one. Why would DataBinding use
connections at all if I already have a filled DataTable?
Thanks in advance for your insights/opinions/etc.
DW