Viewing 15 posts - 31 through 45 (of 52 total)
This error is caused by the Data Source connection not having access into the OTLP database. Connect to your SSAS instance and verify the connection string of your data...
October 16, 2012 at 1:22 pm
Try to make data filters be applied on the SQL side instead of through the report filters.
If a data set is using a stored procedure with parameters, make...
October 16, 2012 at 12:43 pm
Is there one cost_amount per product key?
I see two options.
1. Add cost_amount to the dim_product table. Create a calculated measure SUM([Measures].[Revenue Amount]/[Dim Product].[Cost Amount].MemberValue)
...
August 29, 2012 at 1:44 pm
From what I can remember, Dynamics AX is not made to support type 2 dimensional data. For a proper SCD Type 2 dimensions, you need to maintain something like...
August 29, 2012 at 1:26 pm
Using date might be risky depending on how active your OLTP system is. What's going to happen to records that are entered into the system the same day after...
August 29, 2012 at 1:05 pm
You should leave your dataset unfiltered and do the field!graph filter on the 'Tablix Properties' > 'Filter'.
Each object (table, tablix, chart) you tie a dataset to allows you to filter...
August 29, 2012 at 12:44 pm
PaulB-TheOneAndOnly (8/22/2012)
1- The OLTP source system(s) <= The systems that support the operation of the business.
2- The Staging area <= Where you put whatever you Extract from OLTP and...
August 22, 2012 at 3:02 pm
You can use SSIS to run the XMLA script through the Analysis Services Execute DDL Task component.
August 15, 2012 at 11:55 am
The answer really depends on how that data is going to be used.
A. If you are planning on doing analysis based on price, you would need it in...
August 14, 2012 at 1:05 pm
I think MSDN can do a lot better job of explaining exactly what the OUTPUT clause does then I can.
http://msdn.microsoft.com/en-us/library/ms177564.aspx
In the system I worked with, Fact data had to sometimes...
July 21, 2012 at 5:27 pm
Hope this helps.
CREATE TABLEdbo.TargetTable
([SurrogateKey]INTIDENTITY(1,1)NOT NULL PRIMARY KEY
,[JoinKey]INTNOTNULL
,[Detail1]VARCHAR(128)NOT NULL
,[Detail2]VARCHAR(128)NOT NULL)
CREATE TABLEdbo.StageTable
([JoinKey]INTNOTNULL
,[Detail1]VARCHAR(128)NOT NULL
,[Detail2]VARCHAR(128)NOT NULL)
INSERT INTO dbo.TargetTable
(JoinKey,[Detail1], [Detail2])
SELECT1,'Test 1', 'blahblahblah'
UNION ALL SELECT 2,'Test 2', 'blahblahblah'
UNION ALL SELECT 3,'Test 3', 'blahblahblah'
UNION ALL SELECT 4,'Test...
July 20, 2012 at 3:15 pm
Depends on your ETL process to load from staging to target, but you should be able to capture INSERT/UPDATE/DELETE records from the ETL process. I used the MERGE statement...
July 20, 2012 at 5:59 am
On the copied package, can you open up the DDL task and make sure that the XMLA script you're using is pointing to the right database.
If you're using one of...
July 20, 2012 at 5:40 am
Anything you want to aggregate on should be in the Fact table and anything you want to perform groupings on should be in your dimension table.
The design of...
July 19, 2012 at 11:01 pm
Viewing 15 posts - 31 through 45 (of 52 total)