data from MSDE

How I can copy a database from MSDE to another computer with MSDE?
Thanks
Damiano
Damiano,
A good place to start is to have a look at the stored procedures called
sp_detach and sp_attach_db. After you detach the database, just
move the MDF and LDF files to the other computer and attach them
to the other server.
Dan
"YAMNE" <damiano_callegari@.libero.it> wrote in message
news:u7g#XHuWEHA.2176@.TK2MSFTNGP11.phx.gbl...

> How I can copy a database from MSDE to another computer with MSDE?
> Thanks
> Damiano
>
|||If you've committed all pending transactions before detaching then there's
no need to move the transaction log also. sp_attachdb will create a new
transaction log for you.
Jim
"Dan Deward" <ddeward@.msn.com> wrote in message
news:40dc85a9@.news.mcleodusa.net...
> Damiano,
> A good place to start is to have a look at the stored procedures called
> sp_detach and sp_attach_db. After you detach the database, just
> move the MDF and LDF files to the other computer and attach them
> to the other server.
> Dan
> "YAMNE" <damiano_callegari@.libero.it> wrote in message
> news:u7g#XHuWEHA.2176@.TK2MSFTNGP11.phx.gbl...
>
>
|||Hi,
Detach and Attach require some down time in actual server.
If you do a Backup in source server , copy the backup file to destination
and do a Restore - This require Zero down time.
Steps:-
OSQL -Usa -Ppassword -Sserver (enter)
1> Backup database <dbname> to disk='c:\dbname.bak' with init
2>go
copy the dbname.bak to destination server
Now restore the file in Destination
OSQL -Usa -Ppassword -Sserver (enter)
1> restore database <dbname> from disk='c:\dbname.bak'
2>go
Now it destination use the procedure sp_changeuserslogin (Refer books
online)
procedure to sync the logins after restore.
Thanks
Hari
MCDBA
"Jim Young" <thorium48@.hotmail.com> wrote in message
news:e9hlLivWEHA.1356@.TK2MSFTNGP09.phx.gbl...
> If you've committed all pending transactions before detaching then there's
> no need to move the transaction log also. sp_attachdb will create a new
> transaction log for you.
> Jim
> "Dan Deward" <ddeward@.msn.com> wrote in message
> news:40dc85a9@.news.mcleodusa.net...
>
>
|||Huh? The server does not have to be down to do an sp_detach--it can't be
down. Yes, you do "shutdown" the target database, but only that database is
affected. The sp_detach/file copy process can take a few seconds to a few
minutes.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:uKCB%23yyWEHA.1908@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Hi,
> Detach and Attach require some down time in actual server.
> If you do a Backup in source server , copy the backup file to destination
> and do a Restore - This require Zero down time.
> Steps:-
> OSQL -Usa -Ppassword -Sserver (enter)
> 1> Backup database <dbname> to disk='c:\dbname.bak' with init
> 2>go
> copy the dbname.bak to destination server
> Now restore the file in Destination
> OSQL -Usa -Ppassword -Sserver (enter)
> 1> restore database <dbname> from disk='c:\dbname.bak'
> 2>go
> Now it destination use the procedure sp_changeuserslogin (Refer books
> online)
> procedure to sync the logins after restore.
> Thanks
> Hari
> MCDBA
>
>
> "Jim Young" <thorium48@.hotmail.com> wrote in message
> news:e9hlLivWEHA.1356@.TK2MSFTNGP09.phx.gbl...
there's[vbcol=seagreen]
called
>