Moving a SQL DB to New Drive

I'm not a DBA, so if this question seems basic, I appologize. I am capable
of opening a command window and typing commands, without totally
understanding them, so I guess you could say I'm a DB Operator of sorts.
We recently had a SQL database installed on a new server. No other apps live
there. The Server has two logical drive arrays. C: is a mirrored pair and D:
is a RAID 5 three disk array.
The database was installed on the C: drive along with the SQL app itself.
The D: drive has 130 Gb free space with less than 5% already in use while
the primary drive is at 60% useage, and growing, with a max size of 20 Gb.
What we'd like to do is move the SQL database only to the D: drive.
1) How is this best accomplished?
2) Will the SQL app itself need to be reinstalled? (I don't think so, but
I'm not a DBA)
3) Will our clients' ODBC connection need to be redone to "map" to the new
home or will the
ODBC object autoupdate if the name is kept the same?
Thanks for the help!1) http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224071
2) No
3) The actual location of the database files is irrelevant to ODBC, so you
don't have to change anything.
--
Jacco Schalkwijk
SQL Server MVP
"emanon" <NoSpam@.NoSpam.org> wrote in message
news:eV0XcLN9EHA.824@.TK2MSFTNGP11.phx.gbl...
> I'm not a DBA, so if this question seems basic, I appologize. I am capable
> of opening a command window and typing commands, without totally
> understanding them, so I guess you could say I'm a DB Operator of sorts.
> We recently had a SQL database installed on a new server. No other apps
> live
> there. The Server has two logical drive arrays. C: is a mirrored pair and
> D:
> is a RAID 5 three disk array.
> The database was installed on the C: drive along with the SQL app itself.
> The D: drive has 130 Gb free space with less than 5% already in use while
> the primary drive is at 60% useage, and growing, with a max size of 20
> Gb.
> What we'd like to do is move the SQL database only to the D: drive.
> 1) How is this best accomplished?
> 2) Will the SQL app itself need to be reinstalled? (I don't think so, but
> I'm not a DBA)
> 3) Will our clients' ODBC connection need to be redone to "map" to the
> new
> home or will the
> ODBC object autoupdate if the name is kept the same?
> Thanks for the help!
>|||Thank you!
"Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid> wrote
in message news:eAQZdPN9EHA.3828@.TK2MSFTNGP09.phx.gbl...
> 1) http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224071
> 2) No
> 3) The actual location of the database files is irrelevant to ODBC, so you
> don't have to change anything.
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "emanon" <NoSpam@.NoSpam.org> wrote in message
> news:eV0XcLN9EHA.824@.TK2MSFTNGP11.phx.gbl...
> > I'm not a DBA, so if this question seems basic, I appologize. I am
capable
> > of opening a command window and typing commands, without totally
> > understanding them, so I guess you could say I'm a DB Operator of sorts.
> >
> > We recently had a SQL database installed on a new server. No other apps
> > live
> > there. The Server has two logical drive arrays. C: is a mirrored pair
and
> > D:
> > is a RAID 5 three disk array.
> >
> > The database was installed on the C: drive along with the SQL app
itself.
> > The D: drive has 130 Gb free space with less than 5% already in use
while
> > the primary drive is at 60% useage, and growing, with a max size of 20
> > Gb.
> >
> > What we'd like to do is move the SQL database only to the D: drive.
> >
> > 1) How is this best accomplished?
> >
> > 2) Will the SQL app itself need to be reinstalled? (I don't think so,
but
> > I'm not a DBA)
> >
> > 3) Will our clients' ODBC connection need to be redone to "map" to the
> > new
> > home or will the
> > ODBC object autoupdate if the name is kept the same?
> >
> > Thanks for the help!
> >
> >
>