Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Can’t use connect using (local) or localhost as a server name Expand / Collapse
Author
Message
Posted Thursday, July 18, 2013 9:59 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 3:43 PM
Points: 187, Visits: 1,156
Hello everyone

I have a laptop with SQL Server 2008 installed locally. I can only connect to the server by specifying the instance name (this is true of connection attempts using SSMS, datasources in SSRS, etc.)

It would greatly simplify things if I could connect using (local) instead of the instance name.

When I try using (local), it tells me the “server was not found or is inaccessible”.

Can anyone please tell me what I should do to configure this?
Thanks in advance for your help.
Post #1475114
Posted Thursday, July 18, 2013 10:24 AM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 2:01 PM
Points: 20,704, Visits: 32,349
Did you rom the sounds of it, you installed a named instance, which means you have to specify the instance to which you are connecting.


Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Post #1475133
Posted Thursday, July 18, 2013 1:47 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 3:43 PM
Points: 187, Visits: 1,156
Thanks for the response, Lynn. The software was installed by someone else but I was unaware that using a named instance would create this issue so I wouldn't have known any better myself. I thought if you were working on the same box that had the database engine, you could always use local.
Post #1475203
Posted Monday, July 22, 2013 5:05 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Today @ 5:51 AM
Points: 916, Visits: 2,881
jshahan (7/18/2013)
I thought if you were working on the same box that had the database engine, you could always use local.

The box can host more than one instance of the engine, and therefore any instances must be referred to by name. Only the default instance allows you to connect using (local).

You can run SQL Server Configuration Manager to see installed instances.




The SQL Guy @ blogspot

@SeanPearceSQL

About Me
Post #1475940
Posted Tuesday, July 23, 2013 7:20 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, September 26, 2014 6:02 AM
Points: 919, Visits: 1,434
Well you could always connect:

[servername],port

This will prevent you from needing the instance name. Quirky but works.

Steve



Post #1476564
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse