I use optimize schema on a cube and there is no join for the processing. I had seen processing errors when the fact table had foreign keys not in a dimension table. However, I happened to find today that the processing did not show any error even though there were foreign keys in the fact table but not in dimension tables. I verified the data and reprocessed the cube, still saw no error in the processing. Anyone has idea about this kind of behavior?

Thanks!

Forgot to mention: I copy the cube to another server and
it won't process because a member key is not found in the
dimension table. So the problem is with a specific server.
Don't know what's wrong with that server.

Go in with Analysis Manager and try to process the partition. At the bottom
of the dialog box is an "Advanced" button. It allows you to specify how many
errors you are willing to accept. The default is 0 -- meaning that it will
always fail on 1 error. Someone might have increased or disabled the error
all together.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Hui" <anonymous (AT) discussions (DOT) microsoft.com> wrote

Very strange. If you haven't turned on the system-wide processing log file,
please do so. Bring up Analysis Manager, right-click on the server name and
select "Properties..." then in the "Logging" tab, check on the processing
log file and specify something simple, like C:\ProcessingLog.txt

Process your partition. Then go to the processing log file and look at the
SQL statement which the service will use.
Execute it interactively. Is it returning fact rows which contain FK to
dimension members which don't exist?

What will sometimes happen is that a DBA will run the optimize schema wizard
and things will work as expected. . . then at a future time there will be
some kind of structural change, e.g. remove and readd the dimension to the
cube. This removes the optimization step.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Hui" <Hui (AT) discussions (DOT) microsoft.com> wrote

I just found out that the problem was not with Analysis
Server. A member was deleted from a dimension table and
the dimension had not been fully processed since then.
Then new facts with that member ID were added and the cube
processed successfully.