CODEWITHSUNDEEP
sql-server-2005
jsd3
jsd3

Reputation: 1

what might cause SQLServer to stop accepting new database connections while preserving old ones?

A working IIS7 website gets restarted and its websites cannot connect to the database server. All code is fine and unchanged and works if I point to another database server. Database server has been restarted and shows no errors. Network connections seem fine (syn-ack ok between servers). The only errors are app pool crash errors on IIS server. There was a failed red-gate backup job not long before I expreienced these problems, but all database hardware seems fine. I'm guessing that something's wrong on the database server (OS or application) but I haven't found anything yet.... thanks, in advance, for any informed ideas!

Upvotes: 0

Views: 428

Answers (2)

gbn
gbn

Reputation: 432421

  • changing DB server will reset connection pool
  • have you restarted web server? not just IIS... you bounced the DB box so why not web
  • what is the actual error in web code?

I agree with tommieb75: "smells" like connection pooling

Upvotes: 0

t0mm13b
t0mm13b

Reputation: 34592

Could it be the connections to the server pool has been exhausted or are limited by the server and it's connections? Since the database server has been restarted, it would mean the number of the database connections would have been reset. FYI there was an article on CodeProject about connection pooling and ADO.NET here. It could be down to poor programming practice where the connection is being kept open and not disposed of.

Hope this helps, Best regards, Tom.

Upvotes: 1

Related Questions