Discussion Locked

SQL 7.0 INSTALL PROBLEMS

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

My company is going through a conversion that will eventually use Microsoft SQL Server 7.0 as its database platform. When it was originally installed, the data was installed on the system drive (C:) rather than our raid 5 configuration (the D: located on the same server). This was not known until after development had started taking place. We were able to export all the data and its corresponding objects to a standalone version of SQL so that we could uninstall the previous version of SQL onour server. We uninstalled SQL 7.0 and then reinstalled it, telling it to install the data files onto the raid 5 configuration (D:). The installation appears to run fine until it gets to the point where it wants to connect to SQL Server. At this point it pauses, states that the Connect fails and retries only to stop with an error message stating that the it could not connect to the server. I check my confgsvr.out file and it basically states that the server configuration failed. So I reinstalled SQL with the data residing on the system drive and everything works correctly. The question I have is there some registry setting that I have to change prior to installing SQL to allow it to install the data files onto the network (raid 5 drive system)? Or is there anything else I should be looking at as to why this happens? Thank you very much in advance for any assistance that can be provided.
Sean McLaughlin

4 replies

by glen_mcleod

You can leave the SQL system files on your C: drive, and when you start creating databases you can specify that the data files should go on your RAID drive. If they're already created and on your C: then try detaching the databases, moving the files, then re-attaching. You can even create/specify filegroups for your data files on whatever drives are available on your system. But leaving the SQL Server Master databases on the C: shouldn't pose a problem.

You should put your log files on a RAID 1 (mirrored) drive and you data files on your RAID 5 drive. This will avoid the log writer and the checkpoint writer conflicting trying to write to the dame physical drive.

Check out SQL Books Online for more specific information.

Glen

by smcl99_2000

Thank you very much for your assistance. We used your answer to move the database and its corresponding objects onto our Raid 5 drive. Thanks again

This discussion is closed to new replies.