Backing up SSAS2005 - failure when changes occur

#1

I've had backup jobs fail when the database being backed up has had changes
done to it (updates, new dimensions) while the backup is occuring.

Must the database remain in a static state (no changes) while being backed
up in order to avoid a failure?

#2

Pardon me, not new dimensions...new partitions.

"Jesse O." <jesperzz (AT) hotmail (DOT) com> wrote

Quote:

I've had backup jobs fail when the database being backed up has had
changes done to it (updates, new dimensions) while the backup is occuring.

Must the database remain in a static state (no changes) while being backed
up in order to avoid a failure?

#3

anyone?

"Jesse O." <jesperzz (AT) hotmail (DOT) com> wrote

Quote:

Pardon me, not new dimensions...new partitions.

"Jesse O." <jesperzz (AT) hotmail (DOT) com> wrote in message
news:eT$6ikbCHHA.468 (AT) TK2MSFTNGP06 (DOT) phx.gbl...
I've had backup jobs fail when the database being backed up has had
changes done to it (updates, new dimensions) while the backup is
occuring.

Must the database remain in a static state (no changes) while being
backed up in order to avoid a failure?

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Backing up SSAS2005 - failure when changes occur

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap

Backing up SSAS2005 - failure when changes occur - 11-16-2006 , 01:55 PM

Re: Backing up SSAS2005 - failure when changes occur - 11-16-2006 , 02:16 PM

Re: Backing up SSAS2005 - failure when changes occur - 11-21-2006 , 06:58 PM