![]() A connection request must specify both the computer name and instance name in order to connect to the instance. A named instance is one where you specify an instance name when installing the instance. If a connection request specifies only the name of the computer, the connection is made to the default instance. One instance can be the default instance. ![]() You can run multiple instances of the Database Engine on a computer. Any data retrieved is returned to the application, along with any messages such as errors. The instance resolves the Transact-SQL statements into operations against the data and objects in the databases, and if the required permissions have been granted to the login credentials, performs the work. When a connection has been completed, an application sends Transact-SQL statements across the connection to the instance. If the application and instance are on the same computer, the SQL Server connection can run as either a network connection or an in-memory connection. The connection runs through a network connection if the application and instance are on separate computers. It is the target of the connection requests (logins) from applications. InstancesĪn instance of the Database Engine operates as a service that handles all application requests to work with the data in any of the databases managed by that instance. Applications connect to the instance in order to perform work in a database managed by the instance. Each computer can run multiple instances of the Database Engine. Each instance manages several system databases and one or more user databases. Similar to if you tried to connect to the server myserver\myserver as sa but had the wrong password, you would not expect that to show up in the log for myserverold\myserver as you were not connecting to myserverold\myserver.An instance of the Database Engine is a copy of the sqlservr.exe executable that runs as an operating system service. The reason it is NOT in the old server log is that it is not failing to connect to the old server. I am confident that if you look up that IP, it will tie back to MyserverOld and not an end user machine. is going to be the IP of the computer trying to connect to Myserver\myserver. You can verify where the connection is coming from by looking at that CLIENT: section of the error. When you connect to the SQL instance, since it is a named instance, you would use the name "myserver\myserver" when connecting (unless you have a SQL alias set up) and the SQL browser service will pass you over to the proper port. So the services are trying to connect to "Myserver\myserver" not "localhost\myserver" or "MyserverOld\myserver" or ".\myserver" and "Myserver\myserver" is the NEW server. So when the old server was renamed to "Myserverold", nothing was changed on the SQL side to tell the services to look for "MyserverOld", so all of the services are still looking at "Myserver\myserver". When SQL was installed originally on the old server, the SQL instance name was "Myserver\myserver" (computer name\instance name). My expectation is it isn't taking precedence for one over the other, it is configured to use one over the other. ![]() This has nothing to do with the computer name and/or SQL Server name look ups or with having 2 instances with the same SQL Server names and it is not weird that it goes into the new server log because that is the server that is getting the connection. The easy fix - turn off the old server if it is no longer required or disable the SQL services on the old server that are migrated to the new one. This fails and thus you are getting that error. My expectation is that one of these services is currently running now and since its configuration says to look for MyServer\MyServer for the SQL Server, it tries to connect using that connection and the computer name. I expect that it has some SQL related services still installed on it and set to start automatically. What I am expecting is that the OLD server is still online with the name myServerOld. Since the login has a $ at the end, it is (usually) a computer. The CLIENT value of that is the IP of the machine trying to connect. A LOGIN FAILED message in the log means that a login was attempted but was not successful. ![]() I think you are mixing some things up and getting confused.
0 Comments
Leave a Reply. |