Saving Analytic Workspace Changes

When should you save your analytic workspace changes?

Typically, you want to save an analytic workspace at the end of your OLAP Services session to save analytic workspace changes that were made during the session. You can also save an analytic workspace periodically during an OLAP Services session to save changes as you go along.

If you have read/write access to the analytic workspace, then you will get a warning message if you try to switch analytic workspaces, detach a changed analytic workspace, or exit without updating the analytic workspace. If you have read-only access to the analytic workspace, then you can make changes to the analytic workspace, but you cannot save these changes by updating it.

Using the UPDATE command

If you have changed an analytic workspace and want to save those changes, then execute the UPDATE command. The UPDATE command saves analytic workspace changes to disk.

For the complete syntax for the UPDATE command, see the OLAP DML Reference. The simplified syntax for the UPDATE command is show below.

UPDATE [dbname1 [dbname2 . . .]]

A dbname argument specifies the name of a read/write analytic workspace that is attached to your OLAP Services session. If you do not specify any analytic workspace names, then all the attached read/write analytic workspaces, including express.db, are updated.

For example, you can issue the following command to save all analytic workspace changes made so far in a session, including changes to express.db if it is attached as a read/write analytic workspace.

update

Updating shared analytic workspaces

If you have attached a shared analytic workspace and another user has read/write access, then that user's UPDATE command does not affect your view of the analytic workspace. Your view of the data remains the same as when you attached the analytic workspace. If you want access to the changes, then you must detach the analytic workspace and reattach it.