Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > SQL Server > SQL Server 2005 > SQL Server 2005
Password Reminder
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
SQL Server 2005 General discussion of SQL Server *2005* version only.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the SQL Server 2005 section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old April 13th, 2007, 05:17 PM
Authorized User
Join Date: Nov 2005
Location: , , .
Posts: 51
Thanks: 0
Thanked 0 Times in 0 Posts
Default Install sql 2000 after sql 2005

What is the Server name syntax for an ODBC to a SQL 2000 instance installed after SQL 2005 default instance?
When I try creating an ODBC connection from a client with MDAC 2.7 it says "Server does not exist or access denied". ODBC to the default instance works fine.

Just the facts:
Server name is SV-01-SQL01
SQL 2005 is default instance, SP1 (installed first, in D:\SQL Server)
SQL 2000 is named instance "SQL2000", SP4 (installed second, in D:\SQL Server 2000)

Named pipes and TCPIP is enabled for both 2005 and 2000
Query analyzer connects to the 2000 instance
MDAC 2.7 installed on a client from which I want to make an ODBC conncetion.

I've tried the following names

Reply With Quote
  #2 (permalink)  
Old April 13th, 2007, 08:13 PM
Authorized User
Join Date: Dec 2006
Location: Lake Wylie, SC, USA.
Posts: 57
Thanks: 0
Thanked 0 Times in 0 Posts

There are many possible issues.

Try to force Named Pipes...

Try to force TCP/IP...
TCP:SV-01-SQL01\SQL2000 (dynamic port determination)
TCP:SV-01-SQL01\SQL2000,<port number>

A link to read through to help troubleshoot.


Adam Gossage
Lake Wylie, SC, USA
Reply With Quote
  #3 (permalink)  
Old April 16th, 2007, 05:10 PM
Authorized User
Join Date: Nov 2005
Location: , , .
Posts: 51
Thanks: 0
Thanked 0 Times in 0 Posts

Using TCP:SV-01-SQL01\SQL2000,port# worked using the default port for sql2000.

Thanks a bunch! (=
Reply With Quote

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Opening SQL 2000 Jobs in SQL 2005 carumuga SQL Server 2005 0 June 16th, 2008 05:00 AM
Upgrade 2000 DBs to 2005 or install SQL 2000/2005 cJeffreywang SQL Server ASP 0 February 13th, 2008 10:44 PM
Install Sql Server 2000 in network kau_shuk SQL Server 2000 1 April 11th, 2007 07:20 AM
Sql 2000 VS Sql 2005 Reporting Service abdul_owiusa Reporting Services 0 June 25th, 2006 12:01 PM
Upgrading SQL 2000 to SQL 2005 gvcooper SQL Server 2005 1 May 9th, 2006 03:24 PM

All times are GMT -4. The time now is 12:45 PM.

Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.