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.

.

Relevant Pages

  • Re: prob with Dns.Resolve(). Plz help!
    ... Its true that i'm connecting to the server on my local machine. ... /// Set the connection flag to false ... But plz mind, this happens only the first time, the button is clicked. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Newsgroups question
    ... Lucy, not likin a tornado ... I was working from home today using a remote connection to their server, ... for the first time, and it was the first time newsgroups pooped out on ...
    (rec.pets.cats.community)
  • Re: prob with Dns.Resolve(). Plz help!
    ... And Dns.GetHostByNamedoes the right thing in the case of getting remote ... DNS server which *does* know is not itself known to your network card, ... /// Set the connection flag to false ... But plz mind, this happens only the first time, the button is clicked. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: URGENT: Application_Start - doesnt fire
    ... It's as if the Web site simply ignores ANY ... > changes I make once the exception is encountered for the first time. ... You never said what the exception was. ... How can I get the Web server itself to ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: messages stuck and then released after exchange reboot
    ... any messages stuck in an outbox on the web or in outlook. ... checked with the users and the messages were delivered the first time. ... Both times the backend server was rebooted. ... All of the users were from the same exchange server. ...
    (microsoft.public.exchange.admin)
Loading