Hi Vladimir,
what's the problem?
In that dimension you have 671.560 members (at the leaf level) and the Key
Column for every member is a field 2 byte long.

--
Francesco De Chirico

The proplem is that the diememension having key size 2 byte can not have
600K elements. At least this is not right.

"Francesco De Chirico" <f.dechirico (AT) forgroup (DOT) it> schrieb im Newsbeitrag
news:ebQkpc4UEHA.2944 (AT) tk2msftngp13 (DOT) phx.gbl...

Please, can you explain me why?

It's right easy 2^16 = 65k

"Francesco De Chirico" <f.dechirico (AT) forgroup (DOT) it> schrieb im Newsbeitrag
news:e1qNWF7UEHA.1652 (AT) TK2MSFTNGP09 (DOT) phx.gbl...

Sorry, but I don't understand.
You have 671.560 members, everyone need 2 byte for the member key,
so, if you want: 671.560 * 16 = 10744960 .
What's 2^16 for you??

Ok, sorry, I understand now!
Are you sure that Key Data Type is correct??
Because you can manually change it.
--
Francesco De Chirico

Hi!

If you create a table with primary key int(2) in the SQL Server, can you
place more then 2^16 records in it?
I would like to get error from dimension processing, as from insert into SQL
table.

Thanks,
Vladimir


"Francesco De Chirico" <f.dechirico (AT) forgroup (DOT) it> wrote

Ok, if you confirm that in the SQL Server your primary key is int(2), this
is very strange.
I also had a problem like this but in that case, in A.S. I saw Key Data Type
= 2 but in SQL Server the primary key was
int(4). Someone changed that value, but A.S. didn't show any message during
processing.

--
Francesco De Chirico

Hi Francesco


This is the my problem that A.S. didn't show any message.

I would like to see any comments from AS developers, but they are silent :-(

Thanks,
Vlkadimir

"Vladimir Chtepa" wrote:

I cound't see your picture, but do you have Unique Member Keys set to True?

-- J