If the Warehouse Catalog Read Setting Ignore current table name space when reading from the database catalog and update using new table name space is checked then when the RDBMS's warehouse catalog is read, the table space name is ignored.
EXAMPLE:
The owner of warehouse tables is modified and the tables for which the Strategy Desktop Warehouse Catalog Browser is searching no longer seem to exist.
When the Warehouse Catalog is opens, an error message is displayed with the following message:
Table X is missing from the warehouse
and users are asked if they want to remove it from the project.
The table is not missing, but it appears that way because the
Table Name Space to which it belongs has changed.
EXPLANATION:
This checkbox is found in the Warehouse Catalog Browser Options dialog. If users check this setting, when reading the database Warehouse Catalog, Strategy Developer does not compare the current Table Name Space of the tables in the project. The two tables appear to have the same definition to Strategy Developer, and the table is no longer considered to be missing.
The new Table Name Space will now be stored in the table, so users can uncheck this setting to avoid ignoring it again.
The checkbox is also necessary when users wish to switch the project's warehouse, and the user or Table Space Name is different even though the tables' name and structures are the same.
Therefore, users can switch the project warehouse even though the current and new tables are found in different database name spaces. For more information on how to switch the warehouse used by a project refer to Knowledge Base document below:
KB41595: How to switch between warehouse databases for a 3-tier project in realtime without restarting Intelligence Server in MicroStrategy Developer 9.x or 10.x