You already might know this:

you need:

at least one more volume in the shared storage (SAN)

one more IP Address

one more network name

Create the Storage Zoning etc..

On Node1 assign the letter...

did you reboot the box after the settings, some settings are not propagated even after you apply the setting, but need the server to be restarted.

you should follow the link from deepak and also check this out:

http://support.microsoft.com/kb/909967

is this what you need:

select st.text, * from master..sysprocesses

cross apply sys.dm_exec_sql_text(sql_handle) st

OR select st.text,ec.* from sys.dm_exec_connections ec

cross apply sys.dm_exec_sql_text(most_recent_sql_handle) st

or use this:

select st.text, * from master..sysprocesses

cross apply sys.dm_exec_sql_text(sql_handle) st

OR select st.text,ec.* from sys.dm_exec_connections ec

cross apply sys.dm_exec_sql_text(most_recent_sql_handle) st

On the Data sources Folder, right click and properties -> uncheck the Box "Hidden in List View"

select @@version

check SERVERPROPERTY in BOL.

to check for Servers, OSQL -L or SQLCMD -L

Also check this Link for more info.

http://www.sqlteam.com/article/finding-sql-servers-running-on-a-network

Check SQL Server Integration SErvices in installed in the services window.

In SQL Server configuration-> click on SQL Server 2005 Services and check to see for SQL Server Integration Services Service.

To add to the above list: http://www.krell-software.com/mssql-builds.asp

The most simplest approach you can take is :

sp_dropserver [servername]

sp_addserver [new server name], local

I hope you have disabled or Shutdown the previous server before this one goes online.

Recreting the index on 132,873,975 Rows can be a good option agains doing a BCP with them on, shich will consume more time for sure..

Are you using the /b option...

Is it a BIG Deal to get more RAM. This can solve lot of your Problems, including the ones that will arise by limiting the RAM to Per instance.

how many...

ok atleast now we know what the issue is..

you Just have to perform the above Query once you have some time for outage.... the Model Db is not attached...

SQL Server Management Studio, is what you should be using to manage your SQL Server 2005 instance.

SQL Server Enterprise Manager (SQL 2000) will not work over SQL Server 2005 Databases.

Here is another trick:

Run this Query and Post the results:

select name,dbid from sysdatabases

where dbid<=4

and verify to see the DBID of Model Database, i bet it will not be 3, so...