Database Server Migration

By jandres_sandisk ·
Hi to everyone,

We have an old HP ML350, that has 4 SCSI drives configured in RAID 5, and it contains our database. My issue is, we have a new HP ML350 G5 that doesn't support SCSI, it only supports SAS and SATA. Is it possible to transfer the database on those new SAS or SATA drives and configure them in RAID 5, without any loosing the data.

By the way we are using Windows 2003 and an MS SQL for our database

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

the drive types ...

by Churdoo In reply to Database Server Migration

are irrelevant. What is important in your case are what application(s) you're using to access the database, and the versions of MS SQL Server you're using. What version of SQL Server is on your older ML350, and by the way, what generation is your older M350? G3? And will you be moving to SQL Server 2005 on your G5?

The high level process in your case, will likely be:
a) On the G5 server, you'll configure the drive arrays the way you wish, and typically one might use RAID 1 (or 1+0) for O/S, application binaries, and database LOG volumes, and RAID 5 for the database and other dynamic data, for performance reasons.
b) on the G5, use smartstart and install and configure O/S and join to your Active Directory as applicable
c) install MS SQL Server (2005?) and configure
d) use MS SQL Server migration tools to migrate your database from the old ML350, here's a potentially useful article:,289483,sid87_gci1257496,00.html
e) after complete testing, re-migrate the data and change the connection strings for your app(s) to point to the migrated database on the G5 server

Hope this is helpful

Collapse -

Hard to beat Churdoo answer

by CG IT In reply to the drive types ...

import and export of databases on SQL isn't all that problematic. SQL tools are pretty good in doing this. The big problem is the frontend application being used to access the database and present the data to a user in usable form. Often the front end application path to the data is specifically set. Maintaining good paths to the data is the gotcha as churdoo pointed out.

Related Discussions

Related Forums