Bad Idea. Very bad idea. Moving cables from a crashed server to a good
server is a great way to corrupt the data array, especially if it is a SCSI
storage sytem with a cache-accellerated controller card. Either you can
afford the downtime or you can afford clustering. There is no cheap way
solution for increased availability.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org [quoted text, click to view] "tjchamp" <tjchamp@qwest.net> wrote in message
news:ee9608E5EHA.1400@TK2MSFTNGP11.phx.gbl...
> We presently have a server running sql server for our Great Plains
> accounting application. The server has an attached array that contains the
> database data files, tempdb, and backups. The server contains the
operating
> system, and sql server database log files on internal drives. Company
does
> not want to spend the money on licensing for clustering (additional sql
> server), but is nervous about extended hardware downtime.
>
> An idea has been presented to buy another server configured identically to
> the above noted server. If the first server were to crash, we would
simply
> move the cables attached to the array from one server to the other server,
> and be back up quicker than having to wait for support to determine what
> crashed the system and get it fixed.
>
> Could this work? Does sql server store information in the registry that
> would prevent us from coming up clean on the "backup" server?
>
>
>
