Application with mutiple databases | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Application with mutiple databases

Hi, We have a small issue here. We migrated five databases to SQL 2k. And out of that, one database is being accessed by multiple applications and also sharing data with the remaining databases on the single server. The SQL 2k has been installed using a Named instance. The applications accessing this shared database is on NT4.0. I came to know that such applications cannot access SQL 2k database, that is installed on a named instance. If the SQL 2k is on a default instance, then applications running on NT 4.0 can access the database. Now, my question is, is there a work around for this from database perspective.
We do not want to change any code in the application. Any work arounds on the database can be accomplished. Any help is highly appreciated as it is a high priority. Thanks,

Use servernameinstancename that should work with both TCP/IP and named pipes, servername,portnumber should work with tcp/ip as well. What was the error you getting?
Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
Thanks for the quick reply.
I will check the error number from the application guys and post it.
Hi, I checked on the error. The application is accessing the database using a DSN connection configured through the ODBC panel. I tried with servernameinstance name. I get the following error Connection Failed SQL State – 01000
SQL Server Error – 11001 [ODBC SQL Server Driver][TCP/IP Sockets] Connection Open SQL State – 08001
SQL Server Error – 11 [ODBC SQL Server Driver][TCP/IP Sockets] General Network Error
Does the version of ODBC matter ? It is ver 3.70 Thanks for the help
When you connect to an instance of SQL Server by using SQL Query Analyzer, you can force the connection to use the TCP/IP Net-Library. To do this, type the name of the instance of SQL Server with the tcp prefix in the SQL Server text box in the Connect to SQL Server dialog box. http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q328306 – Potential causes of the "SQL Server Does Not Exist or Access Denied" error message. http://support.microsoft.com/default.aspx?scid=kb;EN-US;265808 – connecting to named instances. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
Thanks so much. The info you provided was really valuable.
]]>