Merging expected SQL for testNegativeMatching()  from change e7e1bd5.  This had been missed in the previous cherry pick.
The test now passes with aggregates turned off, but is failing with aggregates--the fact table and not agg table is used.
Ordering in expected values was inconsistent with the query and schema definition.  The ordering of the expected values was in order of customer_id, but the MDX specified the
primary ordering is by Customers.CurrentMember.OrderKey, which for [Name] is defined with orderByColumn='full_name'.
Expected results for an Order() expression were incorrect.  orderByColumn='full_name', but expected results were in customer_id order.
Merge pull request #149 from mkambol/unitTests

More unit test fixes.