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

Cant see SQL Server 2008 R2 on local, no matter what Expand / Collapse
Author
Message
Posted Tuesday, March 26, 2013 6:22 PM
SSC-Enthusiastic

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

Group: General Forum Members
Last Login: Thursday, July 10, 2014 8:44 AM
Points: 146, Visits: 358
Hi, no matter I tried I still can't access instance of MSSQLServer I install on my machine, and I'm trying to do it thru MS SSMS on local machine,
I see Instance MSSQLSERVER in configuration, I started all services (SQL Server, SQL Browser), enabled TCP (port 1433) , (Shared memory also ENABLED). REstarted all services.
Using W authentication on SSMS, going to .\MSSQLSERVER, localhost\MSSQLSERVER, t410\MSSQLServer...
user Name = T410\lenovo which is confirmed correct.

... and still geting error 87 "A network-related or instance-specific error occured while connecting to MSSQL server.
checked firewall for tcp/1433 http://msdn.microsoft.com/en-us/library/ms175043.aspx


In my SSMS ServerName dropdown, I still have stored sqlexpress instance, should be lef from my prev installaion of express. But now I'm on 2008 R2, running W7 64. I also have <Microsoft SQL Server 2008> folder I think left from prev install, it has only Configuration tools.
All new install in <Microsoft SQL Server 2008 R2>

Looks like only thing left is firewall? That what I learned from www, but I'm local so should be the case either. Is there any more diagnostics I can run, not sure about isql -L?

APpreciate all help. How to make it work,

Thanks
V
Post #1435722
Posted Tuesday, March 26, 2013 7:02 PM
SSC Eights!

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

Group: General Forum Members
Last Login: Thursday, July 3, 2014 12:58 AM
Points: 999, Visits: 13,470
Have you got a named instance called MSSQLSERVER? If not and your just trying to connect to the default instance then drop the /MSSQLSERVER from the end of your connections. So (local), . , <servername> should all work

Also have you tried a local copy of SSMS to rule out firewalls etc?
Post #1435730
Posted Tuesday, March 26, 2013 11:52 PM
SSC-Enthusiastic

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

Group: General Forum Members
Last Login: Thursday, July 10, 2014 8:44 AM
Points: 146, Visits: 358
Thanks, Animal Magic
I did not created named instance, now in Services I have (MSSQLSERVER).
And I open FW for TCP/1433

And just tried to connect to <tcp:T410> and got connected to default engine.
So probably I'm OK !!

So "MSSQLSERVER" I see in services is default?

Can I convert default to named instance? I plan to play witn linked servers, not sure will it work for default.
I'm just itching to try it all.

Tx again to all
V
Post #1435773
Posted Wednesday, March 27, 2013 1:32 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: Thursday, July 3, 2014 12:58 AM
Points: 999, Visits: 13,470
Hi,

Yes a default instance is fine for everything you will want to do. You only need named instances when you need more than one instance as you can only have one default instance.

John

Post #1435786
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse