I have a table for time, it already contained year, month, quarter, etc...
However, the wizard doesn't use these fields and always generated
datepart(year, ...), ... etc.

However much performance impact (of processing, drill through, cube data
display, etc.) it can be for a very big database? Should the Member Key
column be changed to the column instead of the function datepart?

Hi Nick,
Yes go ahead and use the fields that you have created for Year, month and so
on. It shouldn't be a big performance gain, but every little bit helps.

David

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