> We installed MS SQL Server to our drive D drive E was the CDROM Drive.
> We wanted to move the CDROM drive to drive D and the hard drive to drive
> E. We change that around and corrected the registry entries -
> repointing everything to drive E instead of D. SQL Server however will
> not start it says it cannot find the databases. Where is this
> information stored. How can I go about changing it?
>
> ~Todd
To do this safely you may have to change the E/D drives back to what
they were, then swap them again as you go through the proper sequence
of attaching and detaching.
Re: SQL 2005 Best Practice vs SQL 2000: Application Files Separate from data (and log) files ... choice to install sql server binaries of the SQL Server on C drive, ... appears that I am not given the choice to install system databases/log files...drives must be physically seperated so that you'll gain performance ... We are physically separating log and data files on separate disks. ... (microsoft.public.sqlserver.setup)
Re: SQL 2005 Best Practice vs SQL 2000: Application Files Separate from data (and log) files ... button in the "Components to Install" window in SQL Server 2005 Setup. ... In 2005 I appear not to be given the choice to install sql server binaries of the SQL Server on C drive, it appears that I am not given the choice to install system databases/log files on a separate drive, as I could in 2000. ... If it's being used intensively in your environment then you should locate it's log and data files on different physical disks. ... Of course these drives must be physically seperated so that you'll gain performance benefits. ... (microsoft.public.sqlserver.setup)
Re: SQL 2005 hardware recommendations ... If I opted for purchasing six 36 GB drives, I could use four to make a "RAID ... partitions and sizes for the installation of SQL Server 2005 ... I also have the opportunity to purchase the same machine with three 72GB ... I'd make one mirrored pair with a hot spare. ... (microsoft.public.sqlserver.setup)
Re: Spread table. ... You create a new filegroup with 3 files in it. ... the 3 drives.... it sql server will spread the data evenly across the 3 files. ... >> multiple files unless each file is on a separate drive array. ... (microsoft.public.sqlserver.clients)
