move datafiles to SAN

Is there a way to move data files to SAN without causing downtime to sql server
Apparently not .. Sorry
"sivan" <sivan@.discussions.microsoft.com> wrote in message
news:958C0429-77A1-44F8-B38E-F7DED1BC6766@.microsoft.com...
> Is there a way to move data files to SAN without causing downtime to sql
server
|||Hi,
You have to detach the database and then copy the files to SAN drive and then
attach it back. As soon as you detach the database , the database will not
be available till you attach it back.
FYI, ALL the other databases in the same instance will be available during
this time.
Thanks
Hari
MCDBA
"Hassan" wrote:

> Apparently not .. Sorry
> "sivan" <sivan@.discussions.microsoft.com> wrote in message
> news:958C0429-77A1-44F8-B38E-F7DED1BC6766@.microsoft.com...
> server
>
>
|||"Hari Prasad" <HariPrasad@.discussions.microsoft.com> wrote in message
news:BF369363-8765-48E0-9C2C-27857A2312ED@.microsoft.com...
> Hi,
> You have to detach the database and then copy the files to SAN drive and
then
> attach it back. As soon as you detach the database , the database will not
> be available till you attach it back.
>
There's one way that may minimize downtime.
Backup your databases and restore them with a new name (this time located on
the SAN).
Then stop activity to the DB Server, perform a transaction log backup of the
databases, restore those to the new databases, drop the old databases,
rename the new ones and you SHOULD be good to go.
If you script it, your downtime can be measured in minutes.
But I would practice this a LOT.
[vbcol=seagreen]
> FYI, ALL the other databases in the same instance will be available during
> this time.
> Thanks
> Hari
> MCDBA
>
>
> "Hassan" wrote:
sql[vbcol=seagreen]