March 9, 2011 at 4:38 am
Hi,
a few days ago we noticed that the login thru the management studio is very slow when we try to connect to the SQL Server - if we are using the IP adress. If we enter the server name, it connects really fast. Same goes for query execution.
Anyone had probs with this and how was it solved?
March 9, 2011 at 9:19 am
Is this for a local instance of SQL Server?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 9, 2011 at 10:07 am
No. In local it works fine with IP adress or name. I know that it sounds its more a network thing (and probably is)- but our admins say that nothing was changed and that no updates were installed. It was working one day fine, and the next it was working very slow - and still is.
Thats why Im asking if anzoe had similar problems
March 9, 2011 at 10:39 am
Sounds like it could be a network route issue. From your machine, what IP does the server name resolve to? Is it the same as the IP address you were using?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 10, 2011 at 3:53 am
Yes-it is the same
March 10, 2011 at 7:22 am
Are you comparing apples to apples...are:
- both connections from SSMS on the same machine?
- both connections from SSMS but on different machines?
- you using SSMS using instance-name and some web app using IP?
Sorry to ask the basics but this one makes little sense...
I would run Profiler, kick off two connections simultaneously and watch to see if there are any differences from SQL Server's perspective as to when they arrive and what they do when they arrive, etc. It might also be worth getting your network team (if they'll believe you) to setup a sniffer to watch the network traffic while that is going on.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 10, 2011 at 7:57 am
Yes, we tried it all and we always have the same results. On the same work station and other ones. It goes slow when using IP adress if I use management studio or a application- it goes fast if we use name when we use it from managememnt studio or a application.
March 10, 2011 at 11:56 am
Do you get similar results when you use the tracert command to both the name and the IP?
March 11, 2011 at 8:15 am
Did you check out the server firewall and how it setup?
your rules can be setup diff
auth type can be issues also if you are using ip, found
this out the hard way with unc drive mappings. for some
reason at times the ip auth and named auth via network
connect is treated diff.
using named you can get to the drive while not via ip.
March 11, 2011 at 11:48 am
Chrissy321 (3/10/2011)
Do you get similar results when you use the tracert command to both the name and the IP?
I'm really looking forward to read the answer to this question.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.March 11, 2011 at 5:35 pm
Have you checked the sys.dm_exec_connections view to see if you connect via a different method by name than by IP? (Maybe by name uses named pipes while by IP address uses TCP?)
March 12, 2011 at 3:43 am
I'm really looking forward to read the answer to this question too
January 6, 2012 at 3:55 pm
We were able to fix this problem by adding PTR records in DNS for the target servers. I'd imagine this should fix it for you. Alternate fix is to add an entry to the hosts files of the client computers.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply