Installation of SQL Server 2005 on the partition disk drive

Trying to install SQL Server 2005 beta version on partition disk drive say
F:\ (Other than local disk drive c:\),

Does anyone know how can I do this? During the installation, it never asks
me on which drive it install to nor browse button is there to browse the
disk drive for installation...

Any help?

Thanks
J.Joriveek (nojunk@.please.com) writes:
> Trying to install SQL Server 2005 beta version on partition disk drive say
> F:\ (Other than local disk drive c:\),
> Does anyone know how can I do this? During the installation, it never asks
> me on which drive it install to nor browse button is there to browse the
> disk drive for installation...

As I recall, you need to go to the Advanced section to do this.

But part of the installations will always be in your ProgramFilesDir,
that is normally C:\Program Files.

Also, you should post your SQL 2005 to the SQL 2005 newsgroups, as these
are monitored by the SQL Server folks. See here for access:
http://go.microsoft.com/fwlink/?linkid=31765.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Installation of SQL Server - Security Question

Dear All,
We have recently had an audit of our Server and have been told to move the
installation as it cannot be on the same partition or drive as the OS.
Can anyone tell me why ?
We are running 2000 on a 2003 box.
Thanks
P
Hi
Ideally, the installation should be on another drive so that the OS has the
C drive to itself. This helps to keep applications from the OS, enhancing
security.
Data, Logs and Backups should never be on the OS drive, each should be on
seperate drives for recoverability and performance.
Regards
Mike
"Patricia" wrote:

> Dear All,
> We have recently had an audit of our Server and have been told to move the
> installation as it cannot be on the same partition or drive as the OS.
> Can anyone tell me why ?
> We are running 2000 on a 2003 box.
> Thanks
> P
|||Thanks Mike,
Our log and data files are on different drives.
What I can't understand is if they are on a different drive, then why do we
need to move our SQL Server program files ?
thanks
P
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> Ideally, the installation should be on another drive so that the OS has the
> C drive to itself. This helps to keep applications from the OS, enhancing
> security.
> Data, Logs and Backups should never be on the OS drive, each should be on
> seperate drives for recoverability and performance.
> Regards
> Mike
> "Patricia" wrote:
|||Actually I'd think that most people would the happy with the OS and SQL
installation on the same drive. The important thing is to keep your Data,
Log and Backup on seperate drives. The only thing I can think of with
regards to the installation files, is if you have your swapfile and tempdb
files on the same drive as your OS and SQL installation. In that case I'd
think about moving these to another drive, but personally I wouldn't be
concerned about having my OS and SQL files on the same drive.
Regards
Steen
Patricia wrote:[vbcol=seagreen]
> Thanks Mike,
> Our log and data files are on different drives.
> What I can't understand is if they are on a different drive, then why
> do we need to move our SQL Server program files ?
> thanks
> P
> "Mike Epprecht (SQL MVP)" wrote:

Installation of SQL Server - Security Question

Dear All,
We have recently had an audit of our Server and have been told to move the
installation as it cannot be on the same partition or drive as the OS.
Can anyone tell me why ?
We are running 2000 on a 2003 box.
Thanks
PHi
Ideally, the installation should be on another drive so that the OS has the
C drive to itself. This helps to keep applications from the OS, enhancing
security.
Data, Logs and Backups should never be on the OS drive, each should be on
seperate drives for recoverability and performance.
Regards
Mike
"Patricia" wrote:

> Dear All,
> We have recently had an audit of our Server and have been told to move the
> installation as it cannot be on the same partition or drive as the OS.
> Can anyone tell me why ?
> We are running 2000 on a 2003 box.
> Thanks
> P|||Thanks Mike,
Our log and data files are on different drives.
What I can't understand is if they are on a different drive, then why do we
need to move our SQL Server program files ?
thanks
P
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> Ideally, the installation should be on another drive so that the OS has th
e
> C drive to itself. This helps to keep applications from the OS, enhancing
> security.
> Data, Logs and Backups should never be on the OS drive, each should be on
> seperate drives for recoverability and performance.
> Regards
> Mike
> "Patricia" wrote:
>|||Actually I'd think that most people would the happy with the OS and SQL
installation on the same drive. The important thing is to keep your Data,
Log and Backup on seperate drives. The only thing I can think of with
regards to the installation files, is if you have your swapfile and tempdb
files on the same drive as your OS and SQL installation. In that case I'd
think about moving these to another drive, but personally I wouldn't be
concerned about having my OS and SQL files on the same drive.
Regards
Steen
Patricia wrote:[vbcol=seagreen]
> Thanks Mike,
> Our log and data files are on different drives.
> What I can't understand is if they are on a different drive, then why
> do we need to move our SQL Server program files ?
> thanks
> P
> "Mike Epprecht (SQL MVP)" wrote:
>

Installation of SQL Server - Security Question

Dear All,
We have recently had an audit of our Server and have been told to move the
installation as it cannot be on the same partition or drive as the OS.
Can anyone tell me why ?
We are running 2000 on a 2003 box.
Thanks
PHi
Ideally, the installation should be on another drive so that the OS has the
C drive to itself. This helps to keep applications from the OS, enhancing
security.
Data, Logs and Backups should never be on the OS drive, each should be on
seperate drives for recoverability and performance.
Regards
Mike
"Patricia" wrote:
> Dear All,
> We have recently had an audit of our Server and have been told to move the
> installation as it cannot be on the same partition or drive as the OS.
> Can anyone tell me why ?
> We are running 2000 on a 2003 box.
> Thanks
> P|||Thanks Mike,
Our log and data files are on different drives.
What I can't understand is if they are on a different drive, then why do we
need to move our SQL Server program files ?
thanks
P
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Ideally, the installation should be on another drive so that the OS has the
> C drive to itself. This helps to keep applications from the OS, enhancing
> security.
> Data, Logs and Backups should never be on the OS drive, each should be on
> seperate drives for recoverability and performance.
> Regards
> Mike
> "Patricia" wrote:
> > Dear All,
> > We have recently had an audit of our Server and have been told to move the
> > installation as it cannot be on the same partition or drive as the OS.
> >
> > Can anyone tell me why ?
> >
> > We are running 2000 on a 2003 box.
> >
> > Thanks
> > P|||Actually I'd think that most people would the happy with the OS and SQL
installation on the same drive. The important thing is to keep your Data,
Log and Backup on seperate drives. The only thing I can think of with
regards to the installation files, is if you have your swapfile and tempdb
files on the same drive as your OS and SQL installation. In that case I'd
think about moving these to another drive, but personally I wouldn't be
concerned about having my OS and SQL files on the same drive.
Regards
Steen
Patricia wrote:
> Thanks Mike,
> Our log and data files are on different drives.
> What I can't understand is if they are on a different drive, then why
> do we need to move our SQL Server program files ?
> thanks
> P
> "Mike Epprecht (SQL MVP)" wrote:
>> Hi
>> Ideally, the installation should be on another drive so that the OS
>> has the C drive to itself. This helps to keep applications from the
>> OS, enhancing security.
>> Data, Logs and Backups should never be on the OS drive, each should
>> be on seperate drives for recoverability and performance.
>> Regards
>> Mike
>> "Patricia" wrote:
>> Dear All,
>> We have recently had an audit of our Server and have been told to
>> move the installation as it cannot be on the same partition or
>> drive as the OS.
>> Can anyone tell me why ?
>> We are running 2000 on a 2003 box.
>> Thanks
>> P

Installation of SQL Server

I have SQL Server 7 installed onto a partition (not C:) on a Win NT4 Server.
I shortly intend upgrading the server to Windows 2000 (to join a new AD
domain). This process will format the C: drive before installing a new Win
2000 installation. I realise I have to back up and detach the databases
before doing this.
However, my question is, does anyone know whether Enterprise Manager will
still run correctly if C: drive is overwritten (even though it is installed
to E:)?
(I'm concerned about losing DLLs etc..)A lot of information is stored in the registry, and that will be on the C:
drive. Among the information that is stored in the registry are the start up
parameters for SQL Server, and that includes the location of the master
database. In other words, if you format the C: drive and wipe the registry,
SQL Server won't start, never mind Enterprise Manager. If you are intend on
formatting the C: drive, I would uninstall SQL Server, and then reinstall it
after you have installed the new OS. That is the safest way to do it.
--
Jacco Schalkwijk
SQL Server MVP
"gmickelsen" <gmickelsen@.discussions.microsoft.com> wrote in message
news:5CBBFAC6-4D12-4A21-B70F-B794C54B4428@.microsoft.com...
>I have SQL Server 7 installed onto a partition (not C:) on a Win NT4
>Server.
> I shortly intend upgrading the server to Windows 2000 (to join a new AD
> domain). This process will format the C: drive before installing a new Win
> 2000 installation. I realise I have to back up and detach the databases
> before doing this.
> However, my question is, does anyone know whether Enterprise Manager will
> still run correctly if C: drive is overwritten (even though it is
> installed
> to E:)?
> (I'm concerned about losing DLLs etc..)
>

Installation of SQL Server

I have SQL Server 7 installed onto a partition (not C on a Win NT4 Server.
I shortly intend upgrading the server to Windows 2000 (to join a new AD
domain). This process will format the C: drive before installing a new Win
2000 installation. I realise I have to back up and detach the databases
before doing this.
However, my question is, does anyone know whether Enterprise Manager will
still run correctly if C: drive is overwritten (even though it is installed
to E?
(I'm concerned about losing DLLs etc..)
A lot of information is stored in the registry, and that will be on the C:
drive. Among the information that is stored in the registry are the start up
parameters for SQL Server, and that includes the location of the master
database. In other words, if you format the C: drive and wipe the registry,
SQL Server won't start, never mind Enterprise Manager. If you are intend on
formatting the C: drive, I would uninstall SQL Server, and then reinstall it
after you have installed the new OS. That is the safest way to do it.
Jacco Schalkwijk
SQL Server MVP
"gmickelsen" <gmickelsen@.discussions.microsoft.com> wrote in message
news:5CBBFAC6-4D12-4A21-B70F-B794C54B4428@.microsoft.com...
>I have SQL Server 7 installed onto a partition (not C on a Win NT4
>Server.
> I shortly intend upgrading the server to Windows 2000 (to join a new AD
> domain). This process will format the C: drive before installing a new Win
> 2000 installation. I realise I have to back up and detach the databases
> before doing this.
> However, my question is, does anyone know whether Enterprise Manager will
> still run correctly if C: drive is overwritten (even though it is
> installed
> to E?
> (I'm concerned about losing DLLs etc..)
>