Showing posts with label specified. Show all posts
Showing posts with label specified. Show all posts

Thursday, March 29, 2012

Default member behaviour

I was under the impression that the behaviour of an MDX query would be the same if I didn't specify anything in the where clause or if I specified the hierarchies default members explicitly. But I've found an example on the Adventure Works cube where this is not the case. Is this expected?

For example:

If I execute the following:

SELECT { [Account].[Account].MEMBERS } ON COLUMNS FROM [Adventure Works]

The first few members I get back are

All Accounts, Balance Sheet, Net Income, Assets, etc. etc.

The [Account].[Accounts] hierarchy has the default member [Account].[Accounts].&[47] so I would expect the following MDX to return me exactly the same members, but it doesn't.

SELECT { [Account].[Account].MEMBERS } ON COLUMNS FROM [Adventure Works] WHERE ( [Account].[Accounts].&[47] )

It misses out Balance Sheet, Assets and other members.

Your assertion is right about omitting default members as long as we are talking about hierarchies belonging to *other dimensions*. Meaning dimensions you do not have on columns or rows.

For hierarchies belonging to the same dimension your assertion does not apply. Other forum participants may be able to describe this in more detail.

Wednesday, March 21, 2012

Default access for a login

Hi guys,
I create a new login; let's say "aaa" with authentication "SQL Server
Authentication" and no database access specified.
Now... I'm able to connect to my SQL Server 2000 using Query Analyzer with
this "aaa" login and read data/execute stored procedure even I didn't specif
y
any level access. For me looks strange, I was expecting to access a database
after I define a user and permisions using this login. Is this normal?
Thanks!Yes they can connect. In terms of what they can execute
where, that depends.
If a login isn't assigned a database, they will access
databases under the guest account. If guest is in the
database, they have access to the database and whatever
public permissions have been set as well as whatever has
been explicitly granted to the guest user in that database.
Guest always exists in master and tempdb - you can't delete
the account from those databases.
-Sue
On Tue, 27 Sep 2005 14:19:01 -0700, "Radu"
<Radu@.discussions.microsoft.com> wrote:

>Hi guys,
>I create a new login; let's say "aaa" with authentication "SQL Server
>Authentication" and no database access specified.
>Now... I'm able to connect to my SQL Server 2000 using Query Analyzer with
>this "aaa" login and read data/execute stored procedure even I didn't speci
fy
>any level access. For me looks strange, I was expecting to access a databas
e
>after I define a user and permisions using this login. Is this normal?
>
>Thanks!