>
> What about using the Transfer feature of SQL Enterprise Manager? We have
a
> scheduled transfer from our primary to backup SQL each night. Are there
> problems with this that you ran into that made you use a dump/copy/restore
> method?
Thats acceptable, just really slow. I can do a dump/copy/restore in
a couple of minutes for a 500mb database. It usually takes 30+ minutes
to do that with SQL Transfer.
I will note SQL Tranfers copies the data and structure only. This
can be a good thing if your source SQL Server has a page problem,
as the page problem will be included in the dump/restore.
> -----Original Message-----
> From: emerald-request@iea-software.com
> [mailto:emerald-request@iea-software.com]On Behalf Of Patrick Briggs
> Sent: Wednesday, May 05, 1999 5:40 PM
> To: emerald@iea-software.com
> Subject: [Emerald] Backing up Emerald
>
>
> Is there a fully documented proceedure I could get my hands on for
> backing up the Emerald's SQL Database? I'd like to know if replication
> is preferred, or just having a timed event set to push the data onto
> another machine. Depending on which is recommended, I need details as
> to exactly how its done.. step by step. Its important to us that we
> don't have Emerald fail and not have some means of recovering, or at
> least, turning up a new machine for failover.
>
> Patrick Briggs
> System Administrator BOSS IG, Inc.
> postmaster@televar.com
>
>