Connection String question

  • Thread starter Thread starter William
  • Start date Start date
W

William

I am using SQL MSDE edition due to financial reasons (it's free). I have a
question regarding connection strings. Almost every publication, online
example or website uses some version of the following connection string:

data source=localhost;initial catalog=pubs;user id=sa

and it seems to work for them. However, in my particular setup I have to
use either the server name or '(local)' including the parenthesis. Any
deviation returns a cannot find server error. This is not a huge issue but
it is kind of annoying me and I would like to know why it is.

Thanks
 
I am using SQL MSDE edition due to financial reasons (it's free). I have a
question regarding connection strings. Almost every publication, online
example or website uses some version of the following connection string:

data source=localhost;initial catalog=pubs;user id=sa

and it seems to work for them. However, in my particular setup I have to
use either the server name or '(local)' including the parenthesis. Any
deviation returns a cannot find server error. This is not a huge issue but
it is kind of annoying me and I would like to know why it is.
Click to expand...

You may have network protocols disabled for your MSDE installation (that's
the default). As such, localhost will fail because that will be turned into
an IP address and a TCP/IP connection to MSDE will be attempted. (local), on
the other hand, uses named pipes, I believe.

I could be wrong. You'd probably be better off asking in
microsoft.public.sqlserver.msde.
 
I think I ran into this issue when I did a clean install of MSDE with SP3a.
SP3a disables some network stuff by default (it does not do this during an
upgrade).

I think this deals with subject from the SP3a readme:

3.7.2 Security Considerations for MSDE 2000 SP3a
The following information applies only to Desktop Engine (MSDE 2000).

The behavior of MSDE 2000 setup has been changed in SP3a so that the default
settings result in a more secure configuration.

Desktop Engine SP3a changes the default behavior of the
DISABLENETWORKPROTOCOLS setup parameter that specifies the configuration of
the network connection support for an instance of MSDE 2000. If no
application running on another computer will connect to your instance of
MSDE 2000, the instance has no need for network support and it is prudent to
turn off a resource that is not being used. SP3a will turn off the network
support by default when installing new instances of MSDE 2000. If you
disable the network support when installing an instance of MSDE 2000 SP3a,
you can later reconfigure the instance to enable the support. For more
information about disabling and restoring network access, see Microsoft
Knowledge Base article 814130.


Not sure how that all relates (if at all), but I now just use (local) and
not localhost for everything. It seems to be less problematic for me.

Greg
 
I think I ran into this issue when I did a clean install of MSDE with SP3a.
SP3a disables some network stuff by default (it does not do this during an
upgrade).
Click to expand...

You're right. 99% of the MSDE installs I've done have been clean installs
and SP3a. I forgot that this was not always the behavior.
 
¤ I am using SQL MSDE edition due to financial reasons (it's free). I have a
¤ question regarding connection strings. Almost every publication, online
¤ example or website uses some version of the following connection string:
¤
¤ data source=localhost;initial catalog=pubs;user id=sa
¤
¤ and it seems to work for them. However, in my particular setup I have to
¤ use either the server name or '(local)' including the parenthesis. Any
¤ deviation returns a cannot find server error. This is not a huge issue but
¤ it is kind of annoying me and I would like to know why it is.

Never used localhost unless if was for a local web server address. The (local) data source should be
appropriate.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
Back
Top