Showing posts with label statements. Show all posts
Showing posts with label statements. Show all posts

Tuesday, March 20, 2012

NONEMPTYCROSSJOIN : how does it work with linked measure groups ?

Hi,

I am experiencing a strange behaviour with both NONEMPTYCROSSJOIN() and NON(CROSSJOIN()) Mdx statements when working with linked measure groups.

Bascially, I have created a very simple "regular" MOLAP cube on SSAS2005 with one fact table and 3 dimensions. I have one single Measure Group for this cube.

Now, if I create an empty cube (no data source view) and add the measure group of my first cube as a Linked Measure Group, it seems like the Mdx function NonEmptyCrossJoin() never returns anything whereas it does on the underlying cube.

Same problem occurs when using NonEmpty(CrossJoin()).

Is there anything I need to parameter to have the NonEmpty baheviour work correclty on the linked measure group ? I've read there's a "NonEmpty behaviour" parameter for calculated members, but I'm not even using calculated measures.

Is such a behaviour a known issue ?

Do you need a more detailed example? if so, on which database ?

To give some backgroung, I have first noticed this problem after migrating a virtual cube from SSAS 2000.

Many thanks in advance

Rgds,

Francois

I eventually found an answer to this.

There was obviously some type of confusion in the migration of the virtual cube (which is based in SSAS2000 on 3 physical cubes) because not all of the sub cubes' dimensions where used.

I have recreated by linked measure groups manually, removed the unused dimension and the nonemptycrossjoin works fine now.

Hope that helps anyone having the same type of problem.

- F.

Friday, March 9, 2012

Non ANSI Transact-SQL statements

Do you know what Transact-SQL statements are not ANSI compliant?Check out SET FIPS_FLAGGER in BOL ...
"Marc" <anonymous@.discussions.microsoft.com> wrote in message
news:4B1C6A92-2524-4697-AD71-816326DF58B2@.microsoft.com...
> Do you know what Transact-SQL statements are not ANSI compliant?|||However, there are a lot of non ANSI SQL statements for witch the FIPS_FLAGG
ER doesn't warn, as it should.
Mimer (www.mimer.se) has a SQL validator on the web (and also as a web servi
ce!). Also, SQL Reskit (I believe
it is) comes with a word doc which shots the BNF (grammar) for the TSQL lang
uage and colour coding shows
whether a statement is ANSI SQL compliant or not.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Adam Machanic" <amachanic@.air-worldwide.nospamallowed.com> wrote in message
news:%235GuRo2EEHA.4016@.TK2MSFTNGP09.phx.gbl...
> Check out SET FIPS_FLAGGER in BOL ...
>
> "Marc" <anonymous@.discussions.microsoft.com> wrote in message
> news:4B1C6A92-2524-4697-AD71-816326DF58B2@.microsoft.com...
>|||Thanks for the clarification, Tibor. I'll check those out links out.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:euXuflWFEHA.3456@.tk2msftngp13.phx.gbl...
> However, there are a lot of non ANSI SQL statements for witch the
FIPS_FLAGGER doesn't warn, as it should.
> Mimer (www.mimer.se) has a SQL validator on the web (and also as a web
service!). Also, SQL Reskit (I believe
> it is) comes with a word doc which shots the BNF (grammar) for the TSQL
language and colour coding shows
> whether a statement is ANSI SQL compliant or not.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
>
> "Adam Machanic" <amachanic@.air-worldwide.nospamallowed.com> wrote in
message
> news:%235GuRo2EEHA.4016@.TK2MSFTNGP09.phx.gbl...
>