Attach remote DB file

Hi,
is there a way to attach a DB's file locate on a remote path ?
why SQL Server allows attach only from local drives ?
Thanks
AdrianoAdry
There is a TRACE ( don't remember a number) which allows you to create a
database to be stored on remote machine
But it is strongly not recommended , I hope you know why.
Copy the file to the local disk an attach them
"Adry" <adry@.ij_nospam.it> wrote in message
news:%23Q01VRFOGHA.3924@.TK2MSFTNGP14.phx.gbl...
> Hi,
> is there a way to attach a DB's file locate on a remote path ?
> why SQL Server allows attach only from local drives ?
>
> Thanks
> Adriano
>|||Hi,
what do you mean by "there is a TRACE" ? what is "a TRACE" ?
Please, can you explain me better ?
Thanks
Adriano
"Uri Dimant" <urid@.iscar.co.il> ha scritto nel messaggio
news:uW22DhFOGHA.3264@.TK2MSFTNGP11.phx.gbl...
> Adry
> There is a TRACE ( don't remember a number) which allows you to create a
> database to be stored on remote machine
> But it is strongly not recommended , I hope you know why.
> Copy the file to the local disk an attach them
>
>
>
> "Adry" <adry@.ij_nospam.it> wrote in message
> news:%23Q01VRFOGHA.3924@.TK2MSFTNGP14.phx.gbl...
>|||Sorry
By default, you cannot create a database file on a mapped or UNC network
location under SQL Server 2000. You can get around this by turning on trace
flag 1807
DBCC TRACEON (1807)
I dont think it is documented as well as supported but I know for sure it is
not recommended
"Adry" <adry@.ij_nospam.it> wrote in message
news:eYQsayFOGHA.3732@.TK2MSFTNGP10.phx.gbl...
> Hi,
> what do you mean by "there is a TRACE" ? what is "a TRACE" ?
> Please, can you explain me better ?
> Thanks
> Adriano
> "Uri Dimant" <urid@.iscar.co.il> ha scritto nel messaggio
> news:uW22DhFOGHA.3264@.TK2MSFTNGP11.phx.gbl...
>|||Adry wrote:
> Hi,
> what do you mean by "there is a TRACE" ? what is "a TRACE" ?
> Please, can you explain me better ?
> Thanks
> Adriano
> "Uri Dimant" <urid@.iscar.co.il> ha scritto nel messaggio
> news:uW22DhFOGHA.3264@.TK2MSFTNGP11.phx.gbl...
>
As Uri already pointed out, it's not recommended/supported to have a
database file on a remote location. If you still decide to do it, you
should be aware of the consequences in terms of performance and
database integrity.
You can read more about it here -
http://support.microsoft.com/defaul...kb;en-us;304261
Regards
Steen|||Adry wrote:
> why SQL Server allows attach only from local drives ?
>
Because a database located across a network will suffer poor
performance and poor resilience/availability. For that reason,
attaching on a remote drive isn't supported.
Why would you want to attach a database on a remote drive?
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--