 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / General / Setup / August 2005Sql Server 2000 Multiple Instance problem
We have multiple instances of SQL Server to support development and testing of our applications. But when I run the application from our testing server, the wrong instance of SQL Server is responding to queries. I have set up remote debugging to find that the application on the testing server has the correct connection string, but the results are definitely coming from an instance of SQL Server other than the one in the connection string. What could be causing this to occur? This all used to work fine, but we recently upgraded from a Windows NT domain controller to a Win 2003 Server AD Domain. Wondering if something in the domain may be causing this to occur. Are you specifying the IP address in the connection string or an alias? Sounds like the DNS server has the wrong IP assigned to that alias.  SignatureAndrew J. Kelly SQL MVP > We have multiple instances of SQL Server to support development and > testing of our applications. But when I run the application from our [quoted text clipped - 7 lines] > domain controller to a Win 2003 Server AD Domain. Wondering if something > in the domain may be causing this to occur. > Are you specifying the IP address in the connection string or an alias? > Sounds like the DNS server has the wrong IP assigned to that alias. The instances of SQL Server are all on the same server. The server only has one IP address. Should each instance have it's own IP? They never have, and this setup was working fine before. Each instance will have a different port number. If you don't specify the named instance you will get the default instance. What does the connection string look like? SignatureAndrew J. Kelly SQL MVP >> Are you specifying the IP address in the connection string or an alias? >> Sounds like the DNS server has the wrong IP assigned to that alias. >> > The instances of SQL Server are all on the same server. The server only > has one IP address. Should each instance have it's own IP? They never > have, and this setup was working fine before. I am specifying a named instance in the connection string, but I am getting the default instance. The connection string is something like: server=DBSRV\TEST;database=TESTDB;integrated security=sspi My three instances are: DBSRV - default instance DBSRV\DEV - instance to support development DBSRV\TEST - instance to support testing On the test webserver, the connection string is specifying the correct instance, but the data that is retrieved is from the default instance. If I change the connection string on the test webserver to specify the DEV instance, it works as it should. The development computers are able to run the app against both DEV and TEST instances without issue. For some reason, the test webserver is not connecting the the TEST instance. It appears to be connecting to the default instance, even though the connection string specifies the named TEST instance. > Each instance will have a different port number. If you don't specify the > named instance you will get the default instance. What does the connection > string look like? Doesn't make much sense if you can change it to the dev and it works. Any chance you are calling sp's to retrieve the results that might be pointing to the other instance? Do you see the connection to the default instance with sp_who2 or profiler or to Test? SignatureAndrew J. Kelly SQL MVP >I am specifying a named instance in the connection string, but I am getting >the default instance. The connection string is something like: [quoted text clipped - 20 lines] >> the named instance you will get the default instance. What does the >> connection string look like? You're right, it doesn't make much sense. It has the dba and me totally baffled. Our dba checked the sp's, actually he scripted the entire database out to DDL and he said he found no reference to the default instance. As for your last question, I will have the dba look into it. > Doesn't make much sense if you can change it to the dev and it works. Any > chance you are calling sp's to retrieve the results that might be pointing > to the other instance? Do you see the connection to the default instance > with sp_who2 or profiler or to Test? |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.