February 4, 2010 at 8:52 am
Hi all. We are having a curious issue, and hoping others have seen it. We have created a Windows 2008 R2 64-bit server with a 3rd party app running on it. It uses SQL Native client to connect to its database (on a remote SQL 2005 SP3 cluster instance). We noticed it was taking a long time to start up, and found it was having very slow response to connect to SQL. We tested using SQLCmd, and we had the issue with all Instances running on our SQL 2005 Cluster (Sp3, 32 bit). Interestingly enough, we can connect to any other servers with Instances on them and it is super quick, as well as going across to a different domain that is set up exactly like our production SQL 2005 cluster, and it too was very quick. We do not have firewall blocking this, we have verified that all software on the QA and Prod SQL 2005 cluster is the same, and have verified that we can run the same information from a Windows 2003 R2 server using both SQLCmd and Native Client, and it does not have this problem. Any ideas would be appreciated.
February 11, 2010 at 12:12 pm
If you connect on the actual server using SSMS what is the response?
Have you checked that DNS on all DNS server are correct for all the IPs in the cluster?
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply