Your fact table should have a date column that will join with the date_id, the sql_date, or the integer_date column of the dates_dimension table.

After you create the join, create your time dimension(s) using...

You may also want to look at Refreshing the data vs. Incremental Update.

I don't know you specific situation, but I've found that sometimes refreshing the data is allot less cumbersome...

Here's how I do it...

I have a SQL table for my dates. It's updated every day with the current date. Schema as follows:

CREATE TABLE [FH_dates_deminsion] (

 [date_id] [int] IDENTITY (37530, 1)...

This article may answer your MDX question:

http://www.databasejournal.com/features/mssql/article.php/10894_3107081_1

Your client application will usually handle the viewing of Member Properties. I use ProClarity Desktop Pro and it works beautifully.

Thanks again Steve for all looking at this issue. Today I spent some time redesigning the cube and the datasource. I dumped the view into a table and did build...

Steve.... thanks for taking the time to look at this.

I am running Analysis Services 2000 SP3 (msmdsrv.exe 8.0.760)

Dimension: Ord Date (October 1 begins a new fiscal year  fiscal year -...

I've been able to recreate this error (on another dev machine with the pubs db) and have found that it only happens when the fact table is a view. hmmmmmmm.

Steps...

Interesting....

This is the first query sent to SQL Server from the drillthrough....

SET FMTONLY ON

select DatePart(day, "dbo"."FHIS_AR_period_end"."period_end_date",

 "dbo"."FHIS_AR_period_end"."financial_class"

from  "dbo"."FHIS_AR_period_end"

SET FMTONLY OFF

Now I see the syntax error....any ideas how to fix?...

Not sure if this will help, but I had a similar problem and restarting IIS cleared it up.

My problem was that I changed the name of an input parameter in...

Most likely the ASP app uses a connection string with a SQL Login (username and password) specified in it. This is the login used by the APP to login it SQL Server and...

My 2 cents worth....

He's asked how to go about doing it...not whether it's a good idea or not. The questions should be "Who asked you to do it?" and more importantly...

Depending on the situation using an IF or CASE maybe simpler.....

IF @p1 IS NULL PRINT 'PARAMETER_IS_NULL' -- No or NULL parameter passed

ELSE PRINT 'PARAMETER_VALUE = ' + @p1 --parameter has a value

Learn something new everyday....

Are you looking for more than just the computed number to be returned? Do you need the part number, etc. returned also? Can you give an example rowset of what...

I had to do the same thing....no problems yet....

UPDATE sysjobs

SET originating_server = convert(nvarchar(30), serverproperty(N'servername'))

WHERE originating_server != convert(nvarchar(30), serverproperty(N'servername'))

bb