Installing MS MSDE on a Non-System Drive

[sunwindandsea]

We currently have a application installed on another drive on our Windows 2003 Server (Std. Edition) and the SQL data files are installed on the system drive, C. Obviously, we're using the copy of MS MSDE SQL that comes with the application.

We are thinking about reinstalling the application after the testing and training phase and placing the SQL data files on the save non-system drive as the application. Assuming the application install will allow this option, what are the potential problems that might arise from MS MSDE not being installed on the system drive? I’ve read some conflicting statements about resetting shares and permissions. What are the group suggestions?

Thanks,

Ed

 

[gmmastros]

My suggestion would be to leave MSDE on the system drive. It doesn't take much room, and quite frankly, doesn't really need to be backed up either.

The data does need to be backed up regularly, though. I have several MSDE installs where the database engine is installed on the system drive, and the database is resides on a non-system drive.

If you follow my suggestion, you don't need to re-install the application or mess around with security settings either. All you really need to do is to detach the database from SQL Server, move the files to the non-system drive, and then attach them from there. Make sure that nobody is using the application at the time you do this.

-George

Strong and bitter words indicate a weak cause. - Fortune cookie wisdom