Disks not appearing in "My Computer"

I have a clustered environment which includes 2 nodes. The cluster
fails across fine but the only issue is the disks do not appear in My
Computer. When I connect to the disks through Windows disk management
all the disks are there.
Any ideas?
Many thanks
The clustered drives which are called resources are held by the node which is
the active one. At any point of time, only one node can hold the resources.
"Edwin vMierlo [MVP]" wrote:

> Clustered disks are only accessible on the node where they are online.
> Rgds,
> Edwin.
>
> <Joe.Mobley@.nationalexpress.com> wrote in message
> news:1178015037.826526.300420@.h2g2000hsg.googlegro ups.com...
>
>

Disk I/O Errors Error Number 823

Has anyone come across this message when running SQL 2000 Failover clusters ?

I/O error 2(error not found) detected during write at offset 0x00000016d44000 in file 'K:\MSSQL\Data\Int_DB_2_Data.NDF'..

We got this message yesterday, the RAID Array was OK, the Drive could be written to using test editor directly onto the console. We restarted SQL and all came back OK. SPID 3 is the Signal Handler

Any ideas ?Have you check the SQL Error log? My guess is that you may have a torn page in that database.|||I think you should do a full backup, then use this backup version to restore it on another server and run DBCC CHECKDB or DBCC CHECKFILEGROUP to make sure there is no torn page error like joejcheng mentioned. The Error 823 most likey indicate that there is potential disk problem.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_reslsyserr_1_2a0j.asp|||I am chasing a similar problem on HP hardware. Make sure you get a disk consistency check done, as sometimes HP hardware is not good about checking for bad sectors, before writing to them.|||Originally posted by MCrowley
I am chasing a similar problem on HP hardware. Make sure you get a disk consistency check done, as sometimes HP hardware is not good about checking for bad sectors, before writing to them.
Many thanks.

I am running DBCC CHECKDB with ALL_ERRORMSGS , PHYSICAL_ONLY first, then scheduled to run with REPAIR_REBUILD at the weekend.

We are using an HP SAN. I will forward this onto our H/W supplier for info.sql

Disabling the identity column

I have a table that I want to disable the identity column that will be
disabled across different sessions. I cannot use SET IDENTITY_INSERT
table off as it does not persist across columns.
I also do not want to create a tmp table without the identity being
turned on, populate it and then rename the table as this seems a bit
time consuming on a large recordset.
Is there another way?
I will be using SQL server 2000 and/or ado.net
Thanks
Rippo
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!The only way is to drop the column.
AMB
"Rippo" wrote:

> I have a table that I want to disable the identity column that will be
> disabled across different sessions. I cannot use SET IDENTITY_INSERT
> table off as it does not persist across columns.
> I also do not want to create a tmp table without the identity being
> turned on, populate it and then rename the table as this seems a bit
> time consuming on a large recordset.
> Is there another way?
> I will be using SQL server 2000 and/or ado.net
> Thanks
> Rippo
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!
>|||If you can't SET IDENTITY_INSERT for each session then you'll have to
use a non-identity column instead. Why are you using an IDENTITTY in
this situation? The point of an auto-generated surrogate key is that
you shouldn't care what value is inserted. If you want to control the
values externally then IDENTITY isn't the right solution.
--
David Portas
SQL Server MVP
--