Hi
You have to use SQL 2000 tools for SQL 2000. There are a number of changes
introduced in SQL 2000 that the old tools do not understand.
Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike DeleteThis @epprecht.net
MVP Program: <a rel="nofollow" style='text-decoration: none;' href="http://www.microsoft.com/mvp" target="_blank">http://www.microsoft.com/mvp</a>
Blog: <a rel="nofollow" style='text-decoration: none;' href="http://www.msmvps.com/epprecht/" target="_blank">http://www.msmvps.com/epprecht/</a>
"Ray Woerner" wrote in message
> I'm a newbie at SQL Server connections. I've contracted for a SQL 2000
> database with my hosting ISP but have Client Network Utility and
Enterprise
> Manager from SQL Server 7 which was loaded during my install of Visual
> Studio .NET 2003.
>
> I've read that I must "add an alias that points to
> \\computername\pipe\MSSQL$instancename\sql\query".
>
> However, I still can't get the connection set up correctly.
>
> For example, with Server IP address of 11.22.33.44, using TCP/IP on port
> 1234 with instance name SQL101/I1; I've used this setup in Client Network
> Utility (please don't laugh TOO hard):
>
> Server alias = websql; Network Library = TCP/IP;
> Connection parameters = \\11.22.33.44\pipe\MSSQL$SQL101\I1\sql\query
> Port number = 1234
>
> In Enterprise Manager, I've set the SQL Server Registration to "Use SQL
> Server Authentication" and to prompt me for the name and password.
>
> My login fails.
>
> Any help would be appreciated. Please be specific about parameter
settings -
> I'm completely new at SQL server connections.
>
> Thanks,
>
> Ray
>
>
>
>> Stay informed about: SQL 2000 with SQL 7 tools