Re: SQL 2000 with SQL 7 tools

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Mike Epprecht \(SQL MVP\) (mike_at_epprecht.net)
Date: 02/13/05


Date: Sun, 13 Feb 2005 20:51:41 +0100

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@epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

"Ray Woerner" <rpw_01@netzero.net> wrote in message
news:1108313601.b510a3b1323e463c116912be1b4e6a13@teranews...
> 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
>
>
>



Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)
  • Re: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)
  • Re: SQL Server 2005 Cluster Setup Quiz
    ... I did test and it did not install the client tools. ... http://www.clusterhelp.com - Cluster Training ... Microsoft SQL Server MVP ... Provide a template on how to read SQL Server 2005 setup log files. ...
    (microsoft.public.sqlserver.clustering)
  • Re: WSUS
    ... I'm not seeing performance issues with the full enchilada installed, and 25 users busy hitting SQL. ... WSUS isn't difficult to uninstall - if you have WSUS v2 (installed with SBS R2) uninstall R2 from add/remove programs. ... How can anyone work with 4 instances of SQL Server on the same box? ...
    (microsoft.public.windows.server.sbs)