Hello Carlo,
Once you have installed the first instance of virtual SQL Server 2000 then the steps for installing the second instance of virtual SQL Server 2000 is exactly the same. The second virtual instance of SQL Server 2000
will need a seperate shared drive (you cannot use the shared drive that you used for the first instance), unique SQL IP Address (again you cannot use the one you used for your windows cluster ip or the first sql
server ip) and unique SQL network name. Also, if the first virtual instance is a default instance then the second instance can ONLY be a named instance. You CANNOT have two default virtual SQL Server 2000
instance on the same cluster. To have both the instances similar, many customers install both instances of virtual SQL Server 2000 as named instances.
Since you have multiple instances (2 in your case), you will need to ensure that all server nodes have the same resources (processor, memory) and it is enough to handle the instances that could potentially fail to
that node. Another important consideration is to cap memory usage of the instance of SQL Server 2000 with max server memory. Especially if AWE memory is enabled, max server memory must be set in a
multiple-instance cluster to prevent starving the server node.
If you have a Windows Server 2003 EE cluster then you may find the following webcast useful
TechNet Support WebCast: How to install a Microsoft SQL Server 2000 virtual server on a Microsoft Windows Server 2003 cluster
Discusses how to install Microsoft SQL Server 2000 clustering on Microsoft Windows Server 2003 and differences between Microsoft Windows 2000 Server and Windows Server 2003.
http://support.microsoft.com/default.aspx?scid=kb;en-us;888121
For Win2K Adv Server cluster, you may find the following whitepaper useful
SQL Server 2000 Failover Clustering
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx
Review the above and feel free to post any other qs that you may have.
Additional Information
=======================
Here is some other related links that you may find useful
INF: Clustered SQL Server Do's, Don'ts, and Basic Warnings
http://support.microsoft.com/?kbid=254321
Introduction to Microsoft SQL Server 2000 Clustering
http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/wc051001/w
cblurb051001.asp
Microsoft SQL Server 2000 Virtual Server: Things You Should Know
http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/wc032602/w
cblurb032602.asp
Microsoft SQL Server 2000 Virtual Server Basic Setup, Maintenance, and Service Pack http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/wcd061002/
wcdblurb061002.asp
Microsoft SQL Server 2000 Failover Clustering Disaster Recovery Procedures
http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/wcd101802/
wcdblurb101802.asp
Troubleshooting SQL 2000 Virtual Server and Service Pack Setups for Failover Clustering
http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/wcd020703/
wcdblurb020703.asp
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation

Signature
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
Carlo Sorrel - 27 Jan 2005 01:22 GMT
first, sorry my english..., apears this error during instalattion the second instance on Cluster Windows 2003.
The description for Event ID ( 17052 ) in Source ( MSSQL$LASCAR ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [sqsrvres] checkODBCConnectError: sqlstate = 01000; native error = 35; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Tahnk's.
Carlo Sorrel.
> Hello Carlo,
>
[quoted text clipped - 55 lines]
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
Hi
Just be aware, Active-Active does not mean load balancing. It means 2
instances of different databases, each running by default on one of the
nodes of a cluster.
The references Uttam has supplied are great and will help you along.
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/
> My friends:
>
[quoted text clipped - 14 lines]
>
> Carlo Sorrel