i m using sql server 2005 with service pack-2.
When I connect sql server with by registering the remote server with IP, username and password. I have done all the neccessary setting for connecting remotely "SQL Server 2005 Surface Area Configuration".
i got following error while connection:
This version of Microsoft SQL Server Management Studio can only be used to connect to SQL Server 2000 and SQL Server 2005 servers. (ConnectionDlg)
Can you please provide me possible reasons for the above mentioned error.
Thanks,
Saurabh
I would also add that this can also happen if you are trying to connect to a lower version too!
I would also suggest checking which version of SQL 2005 you are attempting to connect to and make sure it is a RTM or higher, and not an older CTP release.
The other possibility is that there is another SQL Server instance (not 2000, or 2005) running on the IP that you are connecting to. Try connecting via server or instance name if possible.
Kev
Only reason for this can be if you are trying to connect to higher version of SQL Server. Please check again if it is SQL Server 2005 or 2008 you are trying to connect.
Here is similar problem and solution for it at sql-server-performance site
edit:- also if you have installed some version of SQL Server 2008 it may also break Management Studio.
Right - to get to the bottom of this I would check the version from the command prompt, from the machine experiencing the problem:
sqlcmd -Q "SELECT ##VERSION" -S myserver\myInstance -U myUserName -P myPassword
This will give you the version of SQL Server you are connecting to. 'sqlcmd' will run against old and new versions of SQL Server.
You can use the same technique, with different SQL to identify which server you are really connecting to, etc.
Related
I created a project in visual studio and I want to use SQL Server Management Studio to see database. What should be the server name?
On connecting to sql server, it gives error:
I tried finding server name using cmd so the result was:
Note:
My sql server configuration manager doesn't contain any sql server services. I was using sql server 2012 so now I downloaded sql server 2017 but same, so services are shown.
How can I connect to sql server?
You will not be able to connect to the SQL server if the SQL Server service is not running. Once you have verified your service is running, you can use the option in the Server name to select your SQL Server Name.
Irfan.
You can connect to SQLServer with two ways:
Usually you run SQLServer instance as service and connect using server credentionals
Sqlexpress "embedded" style - connect to mdf/mdb-file. Behind the scenes it will start localdb service and attach db-file.
First way is recommended in most cases.
Run services.msc and look for sqlserver instances. If they are down - start one. If they are notexistent - rerun installation and check options.
https://support.microsoft.com/en-us/help/3135244/tls-1.2-support-for-microsoft-sql-server
TLS1.1 and TLS1.2 are the only things I have enabled and I have disabled TSL 1.0 and SSL as seen below:
I have two instances of SQL Servers on my machine: A 2008 SQL Express R2 and a SQL 2014.
With those network settings I can still through SSMS connect to SQL 2014 but NOT to 2008 Express R2
So is that a known thing about SQL Servers? Can you explain what is happening?
The error says that the server was not found, I think you did not use the correct server name, that is, if you have 2 instances, one of them is the default(I think 2014), the other one is a named instance, and if you didn't change the name offered by istallation the instance
name is SQLExpress, so if you connect locally, you can use .\SQLExpress or localhost\SQLExpress or (local)\SQLExpress, if you connect remotely you should use yourCompName\SQLExpress and your SQL Server browser must be started (or you can use yourCompName,port_name instead and use no Browser)
I dont know much about sql server.
I have just re-installed windows 7 on my laptop. After that I installed Visual Studio 2012 Express Edition. I also Installed SQL Server Management Studio 2008 R2.
Now when I try to log in to sql server management studio by using server name as . or (local) or .\SQLEXPRESS or PC-Name\SQLEXPRESS and using Windows Authentication I get the error as below.
Please dont mark this question as negative as I have searched on google for last 4 hours but did not understand the problem.
Update:
There are many reasons that may cautioning the problem:
SQL Server is not running
SQL Server is not properly configured
You try to connect with a worng instance Name
You can try the following:
Go to Mycomputer->Rigt Click->Manage->Application and Services
And from there check that SQL Server Express is running
2.From there also, gCheck the Instance name of your SQL Express and be sure when you log on to Management Studio you Provide the same Instance name
Confirm that the service is installed and running. Under Computer Management, drill-down into Services and Applications -> Services.
There should be a service named "SQL Server (SQLEXPRESS)". Try a restart or start of the service.
If any other instance of SQL Server is installed it will be listed - try connecting to LOCALHOST(whatever the instance is listed as) to verify the installation is functional.
UPDATED following further information from comments:
You may have only installed the client tools (management studio), and have not installed the database service. Ensure you have the correct installer which includes the database services engine.
First check that the SQL Server parameters are set accordingly.
Go to Start -
All Programs — Microsoft SQL Server 2008 R2 — Configuration tools —
SQL Server Configuration Manager
Under SQL Server Services, make sure that the instance is running :
SQL Server ()
SQL Server Browser
Under SQL Server Network Configuration - Protocols for (), these are enabled:
TCP/IP
Named Pipes
Do the same under SQL Native Client 10.0 under Client Protocols
I am trying to connect to a SQL Server Express instance on my laptop; I have SQL Server 2008 installed in my system, but when I try to put the instance (local)/SQLEXPRESS or Jashobanta-PC/SQLEXPRESS in my system, I am not able to connect to it. It is appearing that it is not even present in my system.
I am getting the following error :-
A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..
I have tried using the SQLCMD command tool also for this, but the result is same:-
sqlcmd -E -S .\SQLEXPRESS
Here also the same error is appearing.
Is there any chance that SQLEXPRESS is not installed in my system? But as MVC Code First uses SQL Server Express, I need it. When I use code first, then the files are created fine, but how it is connecting, where it is creating the database, it is not known.
Any suggestions will be helpful.
Thanks in advance
Jashobanta
I had a similar issue to this, so for google purposes I'll list my result.
My take on the problem was that I had a SQL2008 Express instance, that had 'gone dark' because I'd installed a full instance of SQL2008R2 and/or SQL Express 2012. My guess is that one or the other of these turns off the out-of-date express instance as a security risk.
These instances were installed as fresh instance names, but somewhere along the way my (local)\SQLEXPRESS instance was disabled.
Using this link I used the SQL2008R2 installer to upgrade the SQLEXPRESS instance that the installer detected.
Once the SQLEXPRESS instance was upgraded to 2008R2 it was happily re-enabled and accessible at (local)\SQLEXPRESS, with all my previous databases inside it.
I have a same problem just now. What you need to do to resolve the problem is to install SQL Server 2008 Express edition.
You can do this by searching "SQL Express" from Web Platform Installer and install "SQL Server 2008 Express with Advanced Series" and "SQL Server 2008 Express with Tools".
Or
Download from this url and install.
http://www.microsoft.com/en-us/download/details.aspx?id=1695
.\SQLEXPRESS is SQL Express for SQL Server 2008 while
(LocalDB)\v11.0 is SQL Express for SQL Server 2012 / 14
I can connect to a remote SQL 2008 Server instance, but I cannot see all the databases in the instance using SQL Server 2008 Management Studio.
I suspect that my problem has something to do with not all database in the remote instance having the same version. For example, I "upgraded" a 2005 database to 2008 by doing a backup from 2005 and importing it into 2008.
When I realized that this was not one of the database that I could see from my other PC, I noticed that the compatibility level of the imported was still 2005, so I changed it to 2008. Still I could not see the database.
On that remote server, the instance node is named "sql2008", and is "Version 10".
When I connect to the sql2008 remote instance from my local PC, the connection is shown locally as being a "SQL Server Version 8.0" instance.
I suspect that locally, I am only being shown databases that are somehow in the remote 2008 instance but have not been upgraded.
I guess I don't know what constitutes an upgraded database and I don't know how to connect to see all the databases, even if this requires multiple connections from the source PC.
The local machine is Windows 7 Ultimate. The remote host is Windows XP Pro.
Related -not being able to see the SQL Server 2008 instance.
Update:
This is what I see on the remote server using Mgt Studio, namely, a SQL 2008 instance and a 2000 instance.
When I log onto the SQL 2008 instance and perform the following query
SELECT
##VERSION As Version,
SERVERPROPERTY('ComputerNamePhysicalNetBIOS') as ComputerNamePhysicalNetBIOS,
SERVERPROPERTY('ServerName') As ServerName,
SERVERPROPERTY('MachineName') As MachineName
The result re-confirms that the 2008b instance shown above with a version of 10 is a 2008 instance:
Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (Intel X86) Mar 29 2009 10:27:29 Copyright (c) 1988-2008 Microsoft Corporation Developer Edition on Windows NT 5.1 <X86> (Build 2600: Service Pack 3)
USPL-DOKMANC2 USPL-DOKMANC2\SQL2008B USPL-DOKMANC2
OK, now from my LOCAL box, I used SQL Mgt Studio to try and connect to USPL-DOKMANC2 (the remote box.)
alt text http://content.screencast.com/users/Dokmanc/folders/Jing/media/ec146f56-5651-4968-9286-82508dc5d3b2/2010-05-22_1426.png
...I connect to the remote w/o the port I get this error:
alt text http://content.screencast.com/users/Dokmanc/folders/Jing/media/d3c5bc46-c286-4708-a2f5-282fc76124cb/2010-05-22_1427.png
But if I enter the DEFAULT port, I am able to connect. Note that the SQL2008 connection that I just added appears as being version "8" (SQL 2000).
alt text http://content.screencast.com/users/Dokmanc/folders/Jing/media/ea80af5e-4a1f-4417-9327-0b76476b4d14/2010-05-22_1426.png
I seem to be connecting to my SQL2000 instance again even though I specified in my connection params to connect to SQL2008b, a 2008 instance.
I can't seem to see my remote 2008 instance on uspl-dokmanc2. I keep getting my 2000 default instance databases showing up under sql2008b.
2nd Update:
Based on excellenf feedback below that SQL is most likely disregarding the name of the instance when tryingt o connect and determining the instance from the port specified. Now I just need to know the port that the SQL2008b instance is running on. I expected that SQL Mgt Config would tell me. The port is blank. Does this imply a default port? What would it be for 2008, not ethat I already have another 2008 instance, so if they all have to have separate ports, the normal 2008 default is probably not it.
Here's what I see in SQL Mgt Config for the 2008b instance. No port mentioned:
The remote instance (8.0) is a SQL Server 2000 instance
There is no such concept as "database version" that relates to visibility or permissions: every DB on a given server (version, SP and hotfix included) is at some internal version. This is why you can't restore or attach a SQL Server 2008 DB onto SQL Server 2005
I would run this to get the full details
SELECT
##VERSION,
SERVERPROPERTY('ComputerNamePhysicalNetBIOS'),
SERVERPROPERTY('ServerName'),
SERVERPROPERTY('MachineName')
For example, you may have a client alias that means you're connecting to the wrong server.
Also, you have to explicitly DENY ANY VIEW DATABASE TO public to "hide" databases
Are you sure your 2008 instance uses 1433 port? MS SQL seem to disregard a name of a instance and connect with the given port in most cases. Use the Configuration Manager to check the port.
Also, check if the SQL Browser is available from the remote machine - you'll have to add 1434 on UDP to your firewall settings. Remember to make sure that the SQL Browser is running on your server of course. See: http://support.microsoft.com/kb/914277