Re: using (local) server on SQL 2K

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: William \(Bill\) Vaughn (billvaRemoveThis_at_nwlink.com)
Date: 07/31/04 

Date: Sat, 31 Jul 2004 09:23:47 -0700

(local) or "." addressing points to the "default" SQL Server instance. If
you install MSDE or SQL Server Express with a name, it installs as a named
instance and should be addressed using the "\<instanceName>" syntax. In the
future MS will encourage you to use the SQLEXPRESS instance name (which will
be used by default during setup) and to share this common instance with
other applications.

hth 

-- 
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"patrick" <patrick@discussions.microsoft.com> wrote in message
news:A3DBAACB-DB4C-4384-9413-27881CE508CF@microsoft.com...
> oSheesh, I never thought of putting my conn string in an external file,
thanks a lot Chris! I also haven't tried the localhost or local URL either,
I will try those, THANKS!
> patrick
>
> "Chris Taylor" wrote:
>
> > Hi Patrick,
> >
> > You should definately consider putting the connection string in a
> > configuration file so that it can be changed easily. You can localhost
or
> > 127.0.0.1.
> >
> > Hope this helps
> >
> > -- 
> > Chris Taylor
> > http://dotnetjunkies.com/weblog/chris.taylor
> >
> >
> > "patrick" <patrick@discussions.microsoft.com> wrote in message
> > news:9D27AEBA-4F9E-4C33-8035-79E9881C17AA@microsoft.com...
> > > I am trying to create my first SQL Server 2000 app deployment. What I
am
> > concerned about is the app won't be able to connect to another machine
via
> > MSDE 2000 once installed because I have my own machine name/SQL server
name
> > coded into the connection string. I know how to make the string use
> > variables, but how do I find the right variables for a foreign machine,
ie.,
> > machine name and server name?
> > >
> > > When I used SQL server 7 or the MSDE version from 1998, I could set my
> > conn str server property to
> > >
> > > server=(local)
> > >
> > > and that would work. But I think I was using ODBC, not OLDB for
sqlserver,
> > and it wasn't in .NET. I have never been able to connect to my SQL 2000
> > using the (local) setting. Why not? None of the books I have says much
on
> > this except that I should be able to connect via (local). TIA,
> > psully@nospam.eatel.net
> > >
> > >
> >
> >
> >

Relevant Pages

  • Re: Win2.3k and dotnet. Urgent please
    ... Did you install MSDE as an instance? ... connection string, unless it is the default instance. ... ASP.NET application and MSDE installed on our Win2k dev server. ... Then I installed SQL server client tools only. ...
    (microsoft.public.inetserver.asp.general)
  • Re: New Event Log Errors!
    ... Somehow along those lines I'd also installed the Certificate Authority ... Did you apply the last Server Pack for SBS Server? ... Please install Windows Support Tools on the win2k3 sp1 problematic ... Microsoft is providing this information only as a convenience to you: ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... everywhere and sitting on the case of the server is the old board - balanced ... slip stream SBS you would have had it ages ago. ... My main reason for slipstreaming the install is because I cannot get ... updates that need to be applied if one is to have a succesful outcome ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... everywhere and sitting on the case of the server is the old board - balanced ... slip stream SBS you would have had it ages ago. ... My main reason for slipstreaming the install is because I cannot get ... updates that need to be applied if one is to have a succesful outcome ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... the old array was a raid 5 that should not have become so rooted but the twit who built the server did not actually enable the spare drive to act as a spare!! ... The problem is SBS is unique and I've rarely if ever seen it work. ... The server has been chugging away in a small business environment for several years and I have administered it for them for about a year making sure that the updates were installed and their mailboxes were managed etc etc. ... My main reason for slipstreaming the install is because I cannot get the original 2003 server install to cope with the new hardware and it falls over part way into the install - BSOD bit. ...
    (microsoft.public.windows.server.sbs)