Connecting to Sql Server 2005 on Win2K3 Server

Hello,
I have a Win2K3 Server running .Net Framework 2.0 applications. When I
run an application for the first time on a particular day, the first
connection takes an extremely long time to connect (60 seconds or
more). Other connections afterwards are fine.
I am running the application on the same machine as the db server. So
network issues should not be a factor.
I can connect with Sql Server Management Studio fine. As a matter of
fact, I can connect with Sql Server Management Studio first. But the
first time I run an application on any day, it takes an extremely long
time to connect. I am using the Enterprise Library Data Application
Block for data access in my applications. It's the January 2006 version
of the data application block.
Anyone know why this happens?
Thanks.
IT takes a while for the DAAB to obtain all of the metadata that it requires
to continue to function properly.
I suggest that if you can't live with the 'setup' time issue, that perhaps
you should investigate direct connections using stored procedures instead of
the DAAB.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
<rmgalante@.yahoo.com> wrote in message
news:1166105657.334884.75560@.73g2000cwn.googlegrou ps.com...
> Hello,
> I have a Win2K3 Server running .Net Framework 2.0 applications. When I
> run an application for the first time on a particular day, the first
> connection takes an extremely long time to connect (60 seconds or
> more). Other connections afterwards are fine.
> I am running the application on the same machine as the db server. So
> network issues should not be a factor.
> I can connect with Sql Server Management Studio fine. As a matter of
> fact, I can connect with Sql Server Management Studio first. But the
> first time I run an application on any day, it takes an extremely long
> time to connect. I am using the Enterprise Library Data Application
> Block for data access in my applications. It's the January 2006 version
> of the data application block.
> Anyone know why this happens?
> Thanks.
>