Corrupting database

Hello:
I am using SQL 2005 on a W2K3 Standard server. The database is being
installed to a external HP disk cage called an MSA 30. After the database
installs it become corrupt almost right away. Does anyone have any
experience with SQL databases on external disk cages.
Harrison MidkiffHarrison,
There is no logical difference between an internal disk and an external disk
array as far as SQL Server is concerned. I would bet your problem is caused
by some hardware anomaly. I copied this from my prior post on another group:
I've seen similar things happen with intermittent h/w failures. In one
specific case it was a newer Perc card that was supposed to be backward
compatible with an older disk array. It wasn't, and would cause the server
to shut down intermittently. It did leave bread crumbs in the Event Log, so
we were able to work our way through it. You might want to check the Event
Log.
Check the SQL Server Log and the Windows Event Log. I bet there is a
reference to some sort of I/O or other hardware error. Possibly, you have a
version compatibility issue with your SCSI controller or drivers as I did.
Or, you may have some sort of fatal hardware issue with the array itself. If
there is no error there, I would suspect faulty write cacheing on the array
side. Turn off write cacheing if it is on.
-- Bill
"Harrison Midkiff" <HMidkiff@.aviinc.com> wrote in message
news:%23H7vfI%23SHHA.5100@.TK2MSFTNGP06.phx.gbl...
> Hello:
> I am using SQL 2005 on a W2K3 Standard server. The database is being
> installed to a external HP disk cage called an MSA 30. After the database
> installs it become corrupt almost right away. Does anyone have any
> experience with SQL databases on external disk cages.
> Harrison Midkiff
>|||Hi
Use SQLIOSim, available from http://support.microsoft.com/kb/231619 to test
your disk subsystem.
It sounds like you have an IO system that is not performing correctly.
Regards
Michel Epprecht [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"AlterEgo" <alterego55@.dslextreme.com> wrote in message
news:OWK%238o%23SHHA.4252@.TK2MSFTNGP05.phx.gbl...
> Harrison,
> There is no logical difference between an internal disk and an external
> disk array as far as SQL Server is concerned. I would bet your problem is
> caused by some hardware anomaly. I copied this from my prior post on
> another group:
> I've seen similar things happen with intermittent h/w failures. In one
> specific case it was a newer Perc card that was supposed to be backward
> compatible with an older disk array. It wasn't, and would cause the server
> to shut down intermittently. It did leave bread crumbs in the Event Log,
> so
> we were able to work our way through it. You might want to check the Event
> Log.
> Check the SQL Server Log and the Windows Event Log. I bet there is a
> reference to some sort of I/O or other hardware error. Possibly, you have
> a version compatibility issue with your SCSI controller or drivers as I
> did. Or, you may have some sort of fatal hardware issue with the array
> itself. If there is no error there, I would suspect faulty write cacheing
> on the array side. Turn off write cacheing if it is on.
> -- Bill
>
> "Harrison Midkiff" <HMidkiff@.aviinc.com> wrote in message
> news:%23H7vfI%23SHHA.5100@.TK2MSFTNGP06.phx.gbl...
>