November 6, 2003 at 4:32 pm
Does anyone know when to use ".\instancename" vs. "(local)\instancename" notations for specifying a server name? I have an app that accesses an MSDE instance on the local machine via a UDL file. My app uses both ADO (MDAC 2.7) and SQL-DMO. In many cases the two notations work interchangeably, but I did run into a couple of of situations where one worked and the other didn't.
My current issue is that the (local) version fails when used by an account without local admin rights whereas the DOT notation succeeds... Any thoughts would be greatly appreciated.
Thanks in advance,
Chris
November 10, 2003 at 8:00 am
This was removed by the editor as SPAM
November 11, 2003 at 3:27 pm
I'd use the dot notation. I think that this is more likely to be supported, but that's an opinion. I don't know if it's really true.
Steve Jones
http://www.sqlservercentral.com/columnists/sjones
The Best of SQL Server Central.com 2002 - http://www.sqlservercentral.com/bestof/
November 12, 2003 at 9:17 am
I wrote some SQL-DMO code and found a similar situation.
SQLServer.Start... on 9x/ME I had to use .\instancename and on NT/2K/XP I had to use (local)\instancename
With SQLServer.Connect, (local)\instancename worked for all platforms.
Weird and I never did find a reason for it.
Paul
November 17, 2003 at 1:58 pm
Now that you mention it, I ran into the same issue earlier and ended up coding around it. I was wondering if perhaps a different network library is being chosen???
November 25, 2003 at 2:38 am
I assumed it was library related, so didn't look into the problem in depth.
December 5, 2003 at 11:52 am
I ran into the same problem where I could not use (local)\instancename, only when trying to connect to MSDE using Shared Memory protocol. I did find that using the specific machine name instead of (local) or DOT worked on all platforms tested(Win98/ME/NT4/2000/XP/2003).
Mark
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply