[This is preliminary documentation and subject to change]
phrase 1, phrase 2, phrase 3
Metabase Scenarios
Metabase scenarios provide detailed information that extend the
information presented throughout the metabase topics. The scenarios
listed below are referenced from the metabase topics that they
support.
Metabase scenarios are grouped by feature as follows:
- Metabase History Scenarios
- Metabase Edit While Running Scenarios
- Metabase Rollback Scenarios
Metabase History Scenarios
The metabase history scenarios provide detailed information
about how metabase history works. For more information about
metabase history, see The Metabase History Feature.
What you will learn:
- How IIS writes the in-memory metabase to disk when all checks
pass.
- How history files are named when the in-memory metabase is
written to disk.
What you will learn:
- How IIS behaves when the metabase.xml file is write-locked and
the in-memory metabase is written to disk.
What you will learn:
- How IIS handles major version number rollover.
What you will learn:
- How IIS avoids overwriting files in the history folder that
have out of order version numbers.
Metabase Edit While Running Scenarios
You will learn
- How the major and minor version numbers are incremented when
metabase.xml is edited directly and saved.
- How the major and minor version numbers are used to name files
in the history folder.
- How IIS determines the changes that were made to metabase.xml
and writes the changes to the in-memory metabase through Admin Base
Objects (ABO).
Edit while running scenario 2
This scenario is not yet written
You will learn
- How edit while running gracefully handles the situation when
the in-memory metabase is written to disk and the metabase.xml file
is open for edits.
You will learn
- How edit while running gracefully handles the situation when
the in-memory metabase is written to disk and the metabase.xml file
(has pending changes) is newer than the temporary file.
- The last write always wins.
You will learn
- How edit while running does not gracefully handle the scenario
when a user programmatically deletes a site within the in-memory
metabase, and another user saves changes to the same site by
editing metabase.xml with notepad.
You will learn
- Why it is not recommended to allow multiple users to
simultaneously edit metabase.xml.
You will learn
- How IIS recovers when the metabase.xml file is changed and
saved, and the corresponding history file is not found.
- How IIS names error files in the history folder.
You will learn
- How IIS behaves when metabase.xml is saved and cannot be
parsed.
- How IIS names error files in the history folder.
- That IIS overwrites metabase.xml with the in-memory metabase
when parse errors occur.
Metabase Rollback
Metabase Rollback Scenario 1
You will learn
- How to roll back to a previous version of the MetaBase.XML
and/or MBSchema.XML files.
This scenario is not yet written
© 1997-2001 Microsoft Corporation. All rights reserved.