ERROR: Subreport: storage

Showing posts with label storage. Show all posts

Thursday, March 29, 2012

Estimating growth

h
how can i find the below from database
Average Record Size (KB)
Total Master Table Storage (GB
Index Storage for 1 Record
Regard
RahLook up the chapter "Estimating the size of a database" in SQL Server 2000
Books Online.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Rah" <anonymous@.discussions.microsoft.com> wrote in message
news:811C9279-BEE1-43FA-9085-B3BD63A8FC61@.microsoft.com...
hi
how can i find the below from database.
Average Record Size (KB)
Total Master Table Storage (GB)
Index Storage for 1 Record
Regards
Rah

Estimating growth

hi
how can i find the below from database.
Average Record Size (KB)
Total Master Table Storage (GB)
Index Storage for 1 Record
Regards
RahLook up the chapter "Estimating the size of a database" in SQL Server 2000
Books Online.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Rah" <anonymous@.discussions.microsoft.com> wrote in message
news:811C9279-BEE1-43FA-9085-B3BD63A8FC61@.microsoft.com...
hi
how can i find the below from database.
Average Record Size (KB)
Total Master Table Storage (GB)
Index Storage for 1 Record
Regards
Rah

Tuesday, March 27, 2012

Estimate storage saving of varDecimal

For an existing database is there an automated method of calculating
the storage saving of using varDecimal storage type?
There is a whitepaper that was just released answering this very question:
http://msdn2.microsoft.com/en-us/library/bb508963.aspx
"Robin9876" <robin9876@.hotmail.com> wrote in message
news:1180623179.357966.223520@.h2g2000hsg.googlegro ups.com...
> For an existing database is there an automated method of calculating
> the storage saving of using varDecimal storage type?
>
|||I had already seen this but after reading it again I noticed that the
stored procedures mentioned could use the existing tables and not just
the best and worst cases as in the whitepaper.
On 31 May, 15:58, "Mike Walsh" <[mwalsh9815][at][gmail][dot][com]>
wrote:[vbcol=seagreen]
> There is a whitepaper that was just released answering this very question:
> http://msdn2.microsoft.com/en-us/library/bb508963.aspx
> "Robin9876" <robin9...@.hotmail.com> wrote in message
> news:1180623179.357966.223520@.h2g2000hsg.googlegro ups.com...

Estimate storage saving of varDecimal

For an existing database is there an automated method of calculating
the storage saving of using varDecimal storage type?There is a whitepaper that was just released answering this very question:
http://msdn2.microsoft.com/en-us/library/bb508963.aspx
"Robin9876" <robin9876@.hotmail.com> wrote in message
news:1180623179.357966.223520@.h2g2000hsg.googlegroups.com...
> For an existing database is there an automated method of calculating
> the storage saving of using varDecimal storage type?
>|||I had already seen this but after reading it again I noticed that the
stored procedures mentioned could use the existing tables and not just
the best and worst cases as in the whitepaper.
On 31 May, 15:58, "Mike Walsh" <[mwalsh9815][at][gmail][dot]
[com]>
wrote:[vbcol=seagreen]
> There is a whitepaper that was just released answering this very question:
> http://msdn2.microsoft.com/en-us/library/bb508963.aspx
> "Robin9876" <robin9...@.hotmail.com> wrote in message
> news:1180623179.357966.223520@.h2g2000hsg.googlegroups.com...
>

Estimate storage saving of varDecimal

For an existing database is there an automated method of calculating
the storage saving of using varDecimal storage type?There is a whitepaper that was just released answering this very question:
http://msdn2.microsoft.com/en-us/library/bb508963.aspx
"Robin9876" <robin9876@.hotmail.com> wrote in message
news:1180623179.357966.223520@.h2g2000hsg.googlegroups.com...
> For an existing database is there an automated method of calculating
> the storage saving of using varDecimal storage type?
>|||I had already seen this but after reading it again I noticed that the
stored procedures mentioned could use the existing tables and not just
the best and worst cases as in the whitepaper.
On 31 May, 15:58, "Mike Walsh" <[mwalsh9815][at][gmail][dot][com]>
wrote:
> There is a whitepaper that was just released answering this very question:
> http://msdn2.microsoft.com/en-us/library/bb508963.aspx
> "Robin9876" <robin9...@.hotmail.com> wrote in message
> news:1180623179.357966.223520@.h2g2000hsg.googlegroups.com...
> > For an existing database is there an automated method of calculating
> > the storage saving of using varDecimal storage type?sql

Monday, March 19, 2012

Errors in the OLAP storage engine: The attribute key cannot be found

I'm somewhat new to using SQL server analaysis services so bear with me on this post.

I am getting the following error when trying ot process a simple cube I built:

Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_vwInvoice, Column: Invoice_x0020_Date, Value: 3/7/2004 10:00:00 AM.

This cube use an Invoice table as the fact table and then a "geography" table as a dimensions table. I am using the server built time dimension which seems to be the problem. It seems to not like the "Invoice Date" field which is a datetime field. This appears to happen on imported data from a legacy application where that application didn't store time so we defaulted the time to 10:00 AM. My guess is that the Invoice Date field has to be unique? If that is the case, any idea on how to get aroudn that?

Thanks for your time,

Marc

Hi,

The error means that the '3/7/2004 10:00:00 AM' value from the 'dbo_vwInvoice' fact table cannot be found in the time dimension table. You mentioned that the time dimension is the server generated one. The server time dimensions only go down to the day level (not hour, minute and second), thus the value will indeed not be found.

If you do not need to do analysis on the hour/minute/second level (in other words, if you do not use the time part of the 'Invoice Date' from from the 'dbo_vwInvoice' fact table), then you can do this:

- create a calculated column (in the DataSourceView, you don't need to alter the actual relational table) in the 'dbo_vwInvoice' fact table to only keep the date part of the 'Invoice Date' column

- then join the fact table (in the 'Dimension Usage' tab of the cube editor) with the time dimension table by that calculated column

Adrian Dumitrascu

|||

You know, I was kind of thinking that but I couldn't find any documentation stating that. Thanks for the response. I would have thought it would inheritly figure out that the field is a datetime field and to just extract the date portion. Easy enough to fix though.

Thanks again,

Marc

|||

Well I spoke too soon. I'm still getting the error. I did a convert(varchar(10),invoice date,101) as the calculated field and still came up with this errror:

Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_vwInvoice, Column: InvoiceDateOnly, Value: 3/29/1998. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Date of Dimension: TimeDimension from Database: WinSTIS Analysis Services Project, Cube: Winstis, Measure Group: Vw Invoice, Partition: Vw Invoice, Record: 11.

Any ideas?

Thanks,

Marc

|||

Sorry for the confusion. I figured it out. It was because I didn't have a large enough date range on the time dimension...

Marc

Errors in the OLAP storage engine:

Errors in the OLAP storage engine: I am new to Analysis Services. I created a cube using Analysis Services 2005 with 3 fact tables and five dimensions. All the dimensions processed successfully apart from one dimension table which gave the following error. The attribute key cannot be found: Table:
dbo_Severity, Column:
SeverityCode, Value: 6

When i try to deploy the cube, I also fail. Is it because of this dimension table in which the attribute key can not be found.

Please help me out.

Regards,

Ronaldlee

Looks like the problem is in the relational database.

Looks like you have a record in the Allergy table with a value in the SeverirtyCode column that does not exist in the Severity table.

Try first sending a SQL query AS sends for the Severity attribute

Then send a SQL query for the Allergy attribute and see which value appears in the SeverityCode column and does not appear in the Severity table.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Thanx a Lot.

You are the man.

Ronald

|||

I have made all the necassary changes,

I have three fact tables in Cube, two of them process successfully, but one doesnot execute successfully.

SELECT 1 AS [dbo_MedicationAllergy0_0],[MedicineCode] AS [dbo_MedicationAllergyMedicineCode0_1]
FROM [dbo].[MedicationAllergy]
)
AS [dbo_MedicationAllergy]
Processing Measure Group 'Prescription' failed.
Start time: 6/15/2006 12:31:24 PM; End time: 6/15/2006 12:31:25 PM; Duration: 0:00:01
Processing Partition 'Prescription' failed.
Start time: 6/15/2006 12:31:25 PM; End time: 6/15/2006 12:31:25 PM; Duration: 0:00:00
SQL queries 1
SELECT [dbo_Prescription].[Quantity] AS [dbo_PrescriptionQuantity0_0],[dbo_Prescription].[Price] AS [dbo_PrescriptionPrice0_1],[dbo_Prescription].[MedicineCode] AS [dbo_PrescriptionMedicineCode0_2],[dbo_Prescription].[PatientId] AS [dbo_PrescriptionPatientId0_3],[dbo_Prescription].[Date] AS [dbo_PrescriptionDate0_4]
FROM [dbo].[Prescription] AS [dbo_Prescription]
Error Messages 2
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_Prescription, Column: PatientId, Value: 10001; Table: dbo_Prescription, Column: Date, Value: 2/9/2000. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: PatientId - Date of Dimension: Return Visit from Database: AnalysisServices, Cube: MSCPROJECTDVS, Measure Group: Prescription, Partition: Prescription, Record: 1.
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_Prescription, Column: PatientId, Value: 10001; Table: dbo_Prescription, Column: Date, Value: 2/9/2000. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: PatientId - Date of Dimension: Return Visit from Database: AnalysisServices, Cube: MSCPROJECTDVS, Measure Group: Prescription, Partition: Prescription, Record: 1. Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation. Errors in the OLAP storage engine: An error occurred while processing the 'Prescription' partition of the 'Prescription' measure group for the 'MSCPROJECTDVS' cube from the AnalysisServices database.
Processing Measure Group 'Patient Diagnosis' completed successfully.
Start time: 6/15/2006 12:31:24 PM; End time: 6/15/2006 12:31:25 PM; Duration: 0:00:01
Processing Partition 'Patient Diagnosis' completed successfully.
Start time: 6/15/2006 12:31:25 PM; End time: 6/15/2006 12:31:25 PM; Duration: 0:00:00
SQL queries 1
SELECT [dbo_PatientDiagnosis].[dbo_PatientDiagnosis0_0] AS [dbo_PatientDiagnosis0_0],[dbo_PatientDiagnosis].[dbo_PatientDiagnosisDiagnosisCode0_1] AS [dbo_PatientDiagnosisDiagnosisCode0_1],[dbo_PatientDiagnosis].[dbo_PatientDiagnosisPatientId0_2] AS [dbo_PatientDiagnosisPatientId0_2],[dbo_Diagnosis_3].[MedicineCode] AS [dbo_DiagnosisMedicineCode2_0]
FROM
(

SELECT 1 AS [dbo_PatientDiagnosis0_0],[DiagnosisCode] AS [dbo_PatientDiagnosisDiagnosisCode0_1],[PatientId] AS [dbo_PatientDiagnosisPatientId0_2]
FROM [dbo].[PatientDiagnosis]
)
AS [dbo_PatientDiagnosis],[dbo].[Diagnosis] AS [dbo_Diagnosis_3]
WHERE
(

(
[dbo_PatientDiagnosis].[dbo_PatientDiagnosisDiagnosisCode0_1] = [dbo_Diagnosis_3].[DiagnosisCode]
)
)
Errors and Warnings from Response
Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation.
Errors in the OLAP storage engine: An error occurred while processing the 'Prescription' partition of the 'Prescription' measure group for the 'MSCPROJECTDVS' cube from the AnalysisServices database.
Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation.
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_Prescription, Column: PatientId, Value: 10001; Table: dbo_Prescription, Column: Date, Value: 2/9/2000.
Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: PatientId - Date of Dimension: Return Visit from Database: AnalysisServices, Cube: MSCPROJECTDVS, Measure Group: Prescription, Partition: Prescription, Record: 1.

Is there any connected to my attributes in the relational data base tables

|||

I have solved the problem though i am still getting some error.

Now it is the MedicationAllergy Fact Table giving me errors.

SELECT 1 AS [dbo_MedicationAllergy0_0],[MedicineCode] AS [dbo_MedicationAllergyMedicineCode0_1]
FROM [dbo].[MedicationAllergy]
)
AS [dbo_MedicationAllergy]
Error Messages 2
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_MedicationAllergy, Column: MedicineCode, Value: 7. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Allergy of Dimension: Allergy from Database: AnalysisServices, Cube: MSCPROJECTDVS, Measure Group: Medication Allergy, Partition: Medication Allergy, Record: 6.
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_MedicationAllergy, Column: MedicineCode, Value: 7. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Allergy of Dimension: Allergy from Database: AnalysisServices, Cube: MSCPROJECTDVS, Measure Group: Medication Allergy, Partition: Medication Allergy, Record: 6. Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation. Errors in the OLAP storage engine: An error occurred while processing the 'Medication Allergy' partition of the 'Medication Allergy' measure group for the 'MSCPROJECTDVS' cube from the AnalysisServices database.
Processing Measure Group 'Patient Diagnosis' completed successfully.
Start time: 6/15/2006 12:51:08 PM; End time: 6/15/2006 12:51:18 PM; Duration: 0:00:10
Processing Partition 'Patient Diagnosis' completed successfully.
Start time: 6/15/2006 12:51:08 PM; End time: 6/15/2006 12:51:18 PM; Duration: 0:00:10
Errors and Warnings from Response
Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation.
Errors in the OLAP storage engine: An error occurred while processing the 'Medication Allergy' partition of the 'Medication Allergy' measure group for the 'MSCPROJECTDVS' cube from the AnalysisServices database.
Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation.
Errors in the high-level relational engine. The database operation was cancelled because of an earlier failure.
Errors in the OLAP storage engine: An error occurred while processing the 'Patient Diagnosis' partition of the 'Patient Diagnosis' measure group for the 'MSCPROJECTDVS' cube from the AnalysisServices database.
Errors in the OLAP storage engine: An error occurred while processing the 'Prescription' partition of the 'Prescription' measure group for the 'MSCPROJECTDVS' cube from the AnalysisServices database.
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_MedicationAllergy, Column: MedicineCode, Value: 7.
Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Allergy of Dimension: Allergy from Database: AnalysisServices, Cube: MSCPROJECTDVS, Measure Group: Medication Allergy, Partition: Medication Allergy, Record: 6.

Ronald

|||

In your fact table you have keys that dont appear in the dimension table.

I think in the dbo_MedicationAllergy fact table, MedicineCode column in has more keys than the Allergy dimension.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Errors in the OLAP storage engine (first deployment using AdventureWorksDW)

Here are a few of the 24 errors. I looked for missing foreign keys but didn't find any. Any help would be appreciated.
Error 2 OLE DB error: OLE DB or ODBC error: Query (5, 25) Parser: The syntax for 'AS' is incorrect.. 0 0
Error 3 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Time', Name of 'Time' was being processed. 0 0
Error 4 Errors in the OLAP storage engine: An error occurred while the 'English Month Name' attribute of the 'Time' dimension from the 'Analysis Services Tutorial' database was being processed. 0 0

Try copy failing query from the processing log and sending it directly to the relational database.

Looks like it is the first one :

T_0].[CalendarYear] AS [mTime0_0]
FROM [dbo].[DimTime] AS [T_0]

See if you get the same error. It is possible you are not connecting to the same data source, or some of the tables have changed since you've created a project.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Errors in the OLAP storage engine

Dear all

I have one table 'Sales' as dimension in a cube for an analysis. In that table one column exist ' DateofOrder'. I want to generate the analysis as Year, Quarter, Month like that using the column DateOfOrder....

What I have to do

Please help ...

Hi,

You can ceate an attribute as DateOfOrder with composite columns Year, Quater, Month, and define the key attribute columns for this attribute as well. (in this case, you could define the key columns as year, quater, month).

Regards,

|||

Thank a lot Helen..

But please help me how to can I create an attrrbute in a dimension 'Sales' for orderdate

|||

Go to the dimension in the data source view, if you are using Analysis Services 2005, and add new named calculation(right click on the dimension table). You use TSQL time functions like YEAR(MyDateColumn), QUARTER(MyDateColumn) and DATEPART(mm,MyDateColumn) to create these levels.

HTH

Thomas Ivarsson

|||

The name of the table 'Sales' does not sound like a "dimension table". Did you mean "Sales" is your Fact table, which is the source of the measure group? What other columns in Sales table would be the source of attributes in the dimension?

Suppose my suspecion is right and Sales is your fact table, then...

The easiest way is to use Server Time generated dimension. Start creating new dimension. The dimension wizard will show up. Select "Build the dimension without data source", navigate to the next page of the wizard. Select "Server time dimension". After that follow the wizard to specify which attributes your dimension will have. Once you have your time dimension you need to relate it to your measure group. Go to Dimension Usage panel of the Cube Designer and click the cell at the intersection of your generated Time dimension and Sales measure group. In the dialog box, which will show up, select Regular relationship and select DateOfOrder column as a measure group column.

If my guess is not right and you indeed need to have a dimension out of Sales table then you need to follow the suggestions you already got.

|||

Sir,

Many Thanks to u sir.... Many thanks ... ..

With regards

Polachan

|||

Error 4

When I am deploying the project I got the following error. Please help me sir

Errors in the OLAP storage engine: An error occurred while processing the 'Product Tran Header' partition of the 'Product Tran Header' measure group for the 'Test' cube from the productreport database. 0 0

I did the following steps

1. added new measure selecting new source table

2. selected one column dateoforder

3. Add new dimension as without using data source

4. selected server time dimension

5. Selected Year/Month/Quarter/date

6 Selected fiscal year

7.Selected dimension usage in cube desgn

8. selected time dimension and selected regular relation, Granulary attribute as Date

9. Measure group table 'Product tran header' new measure group

10 selected measure group column as dateoforder.

after that while deploying the above mentioned error will come

Please help

|||

There are 2 things. Did i understand right that on the step 2 you selected [dateoforder] column as a source of measure? What is your measure? Is it count of transactions? If you measure something like [Order Amount] then you nees to drag [Order Amount] column onto measure group tree view and not [dateoforder]. This column will just be used later in Dimension Usage step, which you made right in step 10.

If you open your server generated dimension in the designer and select tree node related to the dimension itself you can browse the properties of that dimension. There is one of the properties (forgot its exact name), which describes the time range of the dimension like 1/1/2000 - 12/31/2005. Please make sure that this range covers all the instances of [dateoforder] from your fact table.

|||

Dear Sir,

I wil explain what I need

I have one table 'Transactioheader' with the following column

1. id

2. DateofTransaction

Another table with the following column

1. headerid

2. qty

3. productcode

4. areacode

I wanto get the report with sqlanalyis with following format

Quarter1 Quarter2 Quarter3

Qty Qty Qty

Area

Omagh 200 10 100

Belfast 10 05 04

The Quarter 1, Quarter2, Quarter 3 have to be derived from the basis of DateofTransaction column with mapping of Servertime dimension..Please help me sir in this situation what I have to do to use servertime dimension

Thanks a lot for ur caring my queries...

Errors in the OLAP storage engine

Error 4

When I am deploying the project I got the following error. Please help me sir

I did the following steps

1. added new measure selecting new source table

2. selected one column dateoforder

3. Add new dimension as without using data source

4. selected server time dimension

5. Selected Year/Month/Quarter/date

6 Selected fiscal year

7.Selected dimension usage in cube desgn

8. selected time dimension and selected regular relation, Granulary attribute as Date

9. Measure group table 'Product tran header' new measure group

10 selected measure group column as dateoforder.

after that while deploying the above mentioned error will come

Please help

Polachan,

How many partitions do you have in that measure group? Is it possible that you changed measure group structure, but some partitions have specific query that does not match new structure? If this is the case, review each partition query.

Vidas Matelis

|||

Hi All,

I am also facing the same problem when i process some dimensions with in a Cube Database.

Can Anyone please help me in resolving it .

Thanks,

Prashant

|||run a profiler and check the query that is fired to the DB. That will give you some clues.

Errors in the OLAP storage engine

One of the dimension in my cube is Region. When I try to browse this cube with Region deimension, I get the following error:

"Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation"

When I browse Region dimension alone it displays data without any error, also when I browse the cube with other dimensions there are no errors.

Does anybody has any idea for this.

Thanks,
Nasir

It turned out to be data issue. Some of the rows in the Fact table had NULL value in the RegionID. Even though Fact table RegionID has referential integrity with Region lookup table, but still NULL was allowed to be accepted value. Once I replaced the NULL values with some dummy value in both Fact table and Region lookup table, I no more got this error.
Nasir

Sunday, March 11, 2012

Errors in OLAP storage Engine: The attribute Key cannot be found: URGENT

Hi,

Okay, I am stuck here with this error and other related errors. before anything I will describe the scenario. Please do tell me What is wrong, How it happened and how to correct it.

Initially I had 3 relational tables in SQL server.
1. Dim_A (col1a, col2a, col3a)
2. Dim_B (col1b, col2b)
3. Fact_data (col1a,Col1b)

There are no Primary keys, foreign keys and relationships defined in the SQL relational database between these tables.

I created a OLAP database by:
1. creating the datasource
2. creating the datasource view and setting the logical primary keys and relationships as follows:
a. Fact_data.col1a references -> Dim_A.col1a
b. Fact_data.col1b references -> Dim_B.col1b
3. Next, I created a Cube, without automatically creating attributes or hierarchies (no auto build)
4. A Measure Group was automatically created, with a measure called Fact_data count (which i think is the count of the number of rows and was equal to 145). I checked the relational table "Fact_data" to find that the fact table had indeed 145 rows.
5. Next I built the project with not errors, then deployed and processed it.
6. I had no errors and I was able to browse the cube in the SQL BI studio.

After all this, I had created a asp.net page to issue the "Process" command to the complete OLAP database. (I had used the Process Script XMLA from the BI studio). This was also running perfectly.

Now the problem, suddeny next day when i ran the Process from my Asp.Net page, it gave me errors saying that there are Errors in the OLAP Storage engine. The attribute Key cannot be found, with the Table name, Column name and the value. It also gave other errors saying: The record was skipped because the attribute key was not found. it gave the info of the attribure, Dimension, database, cube, measure group and Partition.

I checked the SQL relational tables to find a change in the "Fact_data" table structure. Here is the changed structure of the Fact_data table:

Fact_data (col1a,Col1b,colNewC)

A new column "colNewC" was added to the table. Actually this was a new table with the same name as the old one with a new column. the old table was renamed and probably changed by some other person.
so i thought that the change in structure was the problem.

I created a new Analysis services project in the SQL BI studio, repeated the steps stated above to create a OLAP database. Then I built the project with no erros.
Next while trying to deploy and process the project. It is giving me the same errors. Attribute Key not found. I am neither able to deploy only or deploy and process.

Next I changed the error handling settings and set it to convert the not found keys to unknown. now it gave me esactly 145 errors, with the No attribute keys found. but with deployment and processing complete.
Now trying to browse the cube gives no records at all.

I analyzed the tables and its records, I felt that this was because the records present in the Fact_data table had no matching records in the Dim_A table. or specifically there were no matching "col1a" columns between them. thus all the 145 rows of the Fact_data table were shown as errors.

My question is:
1. So is this only a data in-consistency issue?
2. When somebody changed the Fact_data table structure, they also changed the data which had no matching columns with the dim_A table? is this correct? and hence the errors.
3. The only possible way to correct this is to populate the correct records, is this right?

Sorry for the lengthy post, but i thought it would describe the scenario better. Please do give a detailed answer for this and also how to correct it.

Thanks and regards

Try defining primary key-foreign key relationships in your SQL database.

This should help you to deal with referential integrity errors you are seeing.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

When running the XMLA Script run the default refresh of the dimesions first then process the cube for a full refresh..

The Error means that the Fact tables foriegn key doest match with the Primary key of the Dim Table AKA the lookup table (DIM) doest have a value to match with the DIM Table.Hope this Explains.

If there are lotsa invalidated data in the fact table change the Error procession configuration to notify and continue.

|||

I got exactly the same error message as your post here when I tried to process and deploy the cube in BIDS, did the answer posted here help you solve the problem above?

I want to knwo if that helped solve the problem then I may try this solution.

With best regards,

Yours sincerely,

Errors in OLAP storage Engine: The attribute Key cannot be found: URGENT

Hi,

Okay, I am stuck here with this error and other related errors. before anything I will describe the scenario. Please do tell me What is wrong, How it happened and how to correct it.

Initially I had 3 relational tables in SQL server.
1. Dim_A (col1a, col2a, col3a)
2. Dim_B (col1b, col2b)
3. Fact_data (col1a,Col1b)

There are no Primary keys, foreign keys and relationships defined in the SQL relational database between these tables.

After all this, I had created a asp.net page to issue the "Process" command to the complete OLAP database. (I had used the Process Script XMLA from the BI studio). This was also running perfectly.

I checked the SQL relational tables to find a change in the "Fact_data" table structure. Here is the changed structure of the Fact_data table:

Fact_data (col1a,Col1b,colNewC)

Sorry for the lengthy post, but i thought it would describe the scenario better. Please do give a detailed answer for this and also how to correct it.

Thanks and regards

Try defining primary key-foreign key relationships in your SQL database.

This should help you to deal with referential integrity errors you are seeing.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

When running the XMLA Script run the default refresh of the dimesions first then process the cube for a full refresh..

The Error means that the Fact tables foriegn key doest match with the Primary key of the Dim Table AKA the lookup table (DIM) doest have a value to match with the DIM Table.Hope this Explains.

If there are lotsa invalidated data in the fact table change the Error procession configuration to notify and continue.

|||

I got exactly the same error message as your post here when I tried to process and deploy the cube in BIDS, did the answer posted here help you solve the problem above?

I want to knwo if that helped solve the problem then I may try this solution.

With best regards,

Yours sincerely,

Errors in High-level Relational Engine and OLAP storage Engine

Hi all,,

Could someone help me out and explain to me why my two fact tables process successfully but the process still fails when i try to process the cube.

This is the detailed error message.

Ronald

Check your DSV - data source view.
Looks like your DSV is missing 'dbo_Prescription' table.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi Edward,

It looks like as if I have dbo_Prescription table in my data source View.

I will check it out tomorrow morning and i will get back to you.

Thank you for your time.

Ronald

|||

Hi Edward, In my data source view i have the dbo.Prescription table not dbo_Prescription.

Do these namings really matter.

Ronald

|||

The naming is really important. Without you specifying names correctly Analysis Server has no idea how to construct a valid SQL query.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Edward,

In My data source view, I have the dbo.Prescription table. You know dbo.Prescription and dbo.PatientDiagnosis are my fact tables. I have failed to understand this since i have these two tables in my data source view.

Please help out.

Is this connected with SQL SERVER 2005 service pack1.

Ronald

Below is the same error i get when i process the cube.

<Batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<Parallel>
<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Object>
<DatabaseID>Analysis Services Project1</DatabaseID>
<CubeID>MSCPROJECT</CubeID>
</Object>
<Type>ProcessFull</Type>
<WriteBackTableCreation>UseExisting</WriteBackTableCreation>
</Process>
</Parallel>
</Batch>
Processing Dimension 'Initial Visit' completed successfully.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:20 AM; Duration: 0:00:00
Processing Dimension Attribute 'Physician Id' completed successfully. 8 rows have been read.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:20 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_InitialVisit].[PhysicianId] AS [dbo_InitialVisitPhysicianId0_0]
FROM [dbo].[InitialVisit] AS [dbo_InitialVisit]
Processing Dimension Attribute 'Nurse ID' completed successfully. 7 rows have been read.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:20 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_InitialVisit].[NurseID] AS [dbo_InitialVisitNurseID0_0]
FROM [dbo].[InitialVisit] AS [dbo_InitialVisit]
Processing Dimension Attribute 'Initial Visit' completed successfully. 51 rows have been read.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:20 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_InitialVisit].[PatientId] AS [dbo_InitialVisitPatientId0_0],[dbo_InitialVisit].[Date] AS [dbo_InitialVisitDate0_1],[dbo_InitialVisit].[PhysicianId] AS [dbo_InitialVisitPhysicianId0_2],[dbo_InitialVisit].[NurseID] AS [dbo_InitialVisitNurseID0_3]
FROM [dbo].[InitialVisit] AS [dbo_InitialVisit]
Processing Dimension 'Project' completed successfully.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:20 AM; Duration: 0:00:00
Processing Dimension Attribute 'Project Name' completed successfully. 4 rows have been read.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:20 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Project].[ProjectName] AS [dbo_ProjectProjectName0_0]
FROM [dbo].[Project] AS [dbo_Project]
Processing Dimension Attribute 'Project' completed successfully. 4 rows have been read.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:20 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Project].[ProjectId] AS [dbo_ProjectProjectId0_0],[dbo_Project].[ProjectName] AS [dbo_ProjectProjectName0_1]
FROM [dbo].[Project] AS [dbo_Project]
Processing Dimension 'Medicine Type' completed successfully.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:20 AM; Duration: 0:00:00
Processing Dimension Attribute 'Name' completed successfully. 4 rows have been read.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_MedicineType].[Name] AS [dbo_MedicineTypeName0_0]
FROM [dbo].[MedicineType] AS [dbo_MedicineType]
Processing Dimension Attribute 'Medicine Type' completed successfully. 4 rows have been read.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_MedicineType].[MedicineTypeCode] AS [dbo_MedicineTypeMedicineTypeCode0_0],[dbo_MedicineType].[Name] AS [dbo_MedicineTypeName0_1]
FROM [dbo].[MedicineType] AS [dbo_MedicineType]
Processing Dimension 'Patient' completed successfully.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:20 AM; End time: 6/21/2006 11:59:20 AM; Duration: 0:00:00
Processing Dimension Attribute 'DateOfBirth' completed successfully. 49 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Patient].[DateOfBirth] AS [dbo_PatientDateOfBirth0_0]
FROM [dbo].[Patient] AS [dbo_Patient]
Processing Dimension Attribute 'Gender' completed successfully. 3 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Patient].[Gender] AS [dbo_PatientGender0_0]
FROM [dbo].[Patient] AS [dbo_Patient]
Processing Dimension Attribute 'PatientId' completed successfully. 50 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Patient].[PatientId] AS [dbo_PatientPatientId0_0],[dbo_Patient].[DateOfBirth] AS [dbo_PatientDateOfBirth0_1],[dbo_Patient].[Gender] AS [dbo_PatientGender0_2]
FROM [dbo].[Patient] AS [dbo_Patient]
Processing Hierarchy 'PatientId - DateOfBirth - Gender' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
Processing Dimension 'Diagnosis' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
Processing Dimension Attribute 'Diagnosis Name' completed successfully. 5 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Diagnosis].[Diagnosis name] AS [dbo_DiagnosisDiagnosis_x0020_name0_0]
FROM [dbo].[Diagnosis] AS [dbo_Diagnosis]
Processing Dimension Attribute 'Description' completed successfully. 4 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Diagnosis].[Description] AS [dbo_DiagnosisDescription0_0]
FROM [dbo].[Diagnosis] AS [dbo_Diagnosis]
Processing Dimension Attribute 'Diagnosis' completed successfully. 5 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Diagnosis].[DiagnosisCode] AS [dbo_DiagnosisDiagnosisCode0_0],[dbo_Diagnosis].[Diagnosis name] AS [dbo_DiagnosisDiagnosis_x0020_name0_1],[dbo_Diagnosis].[Description] AS [dbo_DiagnosisDescription0_2]
FROM [dbo].[Diagnosis] AS [dbo_Diagnosis]
Processing Dimension 'Medical Provider' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
Processing Dimension Attribute 'Name' completed successfully. 15 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_MedicalProvider].[Name] AS [dbo_MedicalProviderName0_0]
FROM [dbo].[MedicalProvider] AS [dbo_MedicalProvider]
Processing Dimension Attribute 'Gender' completed successfully. 3 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_MedicalProvider].[Gender] AS [dbo_MedicalProviderGender0_0]
FROM [dbo].[MedicalProvider] AS [dbo_MedicalProvider]
Processing Dimension Attribute 'Indicator Nurseor Physician' completed successfully. 4 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_MedicalProvider].[IndicatorNurseorPhysician] AS [dbo_MedicalProviderIndicatorNurseorPhysician0_0]
FROM [dbo].[MedicalProvider] AS [dbo_MedicalProvider]
Processing Dimension Attribute 'Physician Id' completed successfully. 9 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_MedicalProvider].[PhysicianId] AS [dbo_MedicalProviderPhysicianId0_0]
FROM [dbo].[MedicalProvider] AS [dbo_MedicalProvider]
Processing Dimension Attribute 'Nurse Id' completed successfully. 9 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_MedicalProvider].[NurseId] AS [dbo_MedicalProviderNurseId0_0]
FROM [dbo].[MedicalProvider] AS [dbo_MedicalProvider]
Processing Dimension Attribute 'Medical Provider' completed successfully. 15 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_MedicalProvider].[MedicalProviderId] AS [dbo_MedicalProviderMedicalProviderId0_0],[dbo_MedicalProvider].[Name] AS [dbo_MedicalProviderName0_1],[dbo_MedicalProvider].[Gender] AS [dbo_MedicalProviderGender0_2],[dbo_MedicalProvider].[IndicatorNurseorPhysician] AS [dbo_MedicalProviderIndicatorNurseorPhysician0_3],[dbo_MedicalProvider].[PhysicianId] AS [dbo_MedicalProviderPhysicianId0_4],[dbo_MedicalProvider].[NurseId] AS [dbo_MedicalProviderNurseId0_5]
FROM [dbo].[MedicalProvider] AS [dbo_MedicalProvider]
Processing Dimension 'Allergy' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
Processing Dimension Attribute 'Allergy Name' completed successfully. 6 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_Allergy].[AllergyName] AS [dbo_AllergyAllergyName0_0]
FROM [dbo].[Allergy] AS [dbo_Allergy]
Processing Dimension Attribute 'Allergy' completed successfully. 6 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_Allergy].[AllergyCode] AS [dbo_AllergyAllergyCode0_0],[dbo_Allergy].[AllergyName] AS [dbo_AllergyAllergyName0_1]
FROM [dbo].[Allergy] AS [dbo_Allergy]
Processing Dimension 'Medicine' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:21 AM; Duration: 0:00:00
Processing Dimension Attribute 'Name' completed successfully. 19 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_Medicine].[Name] AS [dbo_MedicineName0_0]
FROM [dbo].[Medicine] AS [dbo_Medicine]
Processing Dimension Attribute 'Medicine' completed successfully. 20 rows have been read.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_Medicine].[MedicineCode] AS [dbo_MedicineMedicineCode0_0],[dbo_Medicine].[Name] AS [dbo_MedicineName0_1]
FROM [dbo].[Medicine] AS [dbo_Medicine]
Processing Dimension 'Services' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:21 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:01
Processing Dimension Attribute 'Service Title' completed successfully. 36 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Services].[Service_Title] AS [dbo_ServicesService_Title0_0]
FROM [dbo].[Services] AS [dbo_Services]
Processing Dimension Attribute 'Service Order' completed successfully. 18 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Services].[Service_Order] AS [dbo_ServicesService_Order0_0]
FROM [dbo].[Services] AS [dbo_Services]
Processing Dimension Attribute 'Services' completed successfully. 36 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_Services].[ServiceId] AS [dbo_ServicesServiceId0_0],[dbo_Services].[Service_Title] AS [dbo_ServicesService_Title0_1],[dbo_Services].[Service_Order] AS [dbo_ServicesService_Order0_2]
FROM [dbo].[Services] AS [dbo_Services]
Processing Dimension 'Return Visit' completed successfully.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:23 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
Processing Dimension Attribute 'Physician Id' completed successfully. 8 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_ReturnVisit].[PhysicianId] AS [dbo_ReturnVisitPhysicianId0_0]
FROM [dbo].[ReturnVisit] AS [dbo_ReturnVisit]
Processing Dimension Attribute 'Nurse Id' completed successfully. 9 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_ReturnVisit].[NurseId] AS [dbo_ReturnVisitNurseId0_0]
FROM [dbo].[ReturnVisit] AS [dbo_ReturnVisit]
Processing Dimension Attribute 'Time Start' completed successfully. 11 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_ReturnVisit].[TimeStart] AS [dbo_ReturnVisitTimeStart0_0]
FROM [dbo].[ReturnVisit] AS [dbo_ReturnVisit]
Processing Dimension Attribute 'Time End' completed successfully. 22 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_ReturnVisit].[TimeEnd] AS [dbo_ReturnVisitTimeEnd0_0]
FROM [dbo].[ReturnVisit] AS [dbo_ReturnVisit]
Processing Dimension Attribute 'Return Visit' completed successfully. 50 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
SQL queries 1
SELECT
DISTINCT
[dbo_ReturnVisit].[PatientId] AS [dbo_ReturnVisitPatientId0_0],[dbo_ReturnVisit].[Date] AS [dbo_ReturnVisitDate0_1],[dbo_ReturnVisit].[PhysicianId] AS [dbo_ReturnVisitPhysicianId0_2],[dbo_ReturnVisit].[NurseId] AS [dbo_ReturnVisitNurseId0_3],[dbo_ReturnVisit].[TimeStart] AS [dbo_ReturnVisitTimeStart0_4],[dbo_ReturnVisit].[TimeEnd] AS [dbo_ReturnVisitTimeEnd0_5]
FROM [dbo].[ReturnVisit] AS [dbo_ReturnVisit]
Processing Dimension 'Severity' completed successfully.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:23 AM; Duration: 0:00:01
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:22 AM; Duration: 0:00:00
Processing Dimension Attribute 'Severity Name' completed successfully. 6 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:23 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_Severity].[SeverityName] AS [dbo_SeveritySeverityName0_0]
FROM [dbo].[Severity] AS [dbo_Severity]
Processing Dimension Attribute 'Severity' completed successfully. 6 rows have been read.
Start time: 6/21/2006 11:59:22 AM; End time: 6/21/2006 11:59:23 AM; Duration: 0:00:01
SQL queries 1
SELECT
DISTINCT
[dbo_Severity].[SeverityCode] AS [dbo_SeveritySeverityCode0_0],[dbo_Severity].[SeverityName] AS [dbo_SeveritySeverityName0_1]
FROM [dbo].[Severity] AS [dbo_Severity]
Processing Cube 'MSCPROJECT' completed successfully.
Start time: 6/21/2006 11:59:23 AM; End time: 6/21/2006 11:59:24 AM; Duration: 0:00:01
Processing Measure Group 'Patient Diagnosis' completed successfully.
Start time: 6/21/2006 11:59:23 AM; End time: 6/21/2006 11:59:24 AM; Duration: 0:00:01
Processing Partition 'Patient Diagnosis' completed successfully.
Start time: 6/21/2006 11:59:23 AM; End time: 6/21/2006 11:59:24 AM; Duration: 0:00:01
Processing Measure Group 'Prescription' completed successfully.
Start time: 6/21/2006 11:59:23 AM; End time: 6/21/2006 11:59:24 AM; Duration: 0:00:01
Processing Partition 'Prescription' completed successfully.
Start time: 6/21/2006 11:59:23 AM; End time: 6/21/2006 11:59:24 AM; Duration: 0:00:01
Errors and Warnings from Response
Errors in the high-level relational engine. The data source view does not contain a definition for the 'dbo_Prescription' table or view. The Source property may not have been set.
Errors in the OLAP storage engine: An error occurred while processing the 'Prescription' partition of the 'Prescription' measure group for the 'MSCPROJECT' cube from the Analysis Services Project1 database.
Errors in the high-level relational engine. The database operation was cancelled because of an earlier failure.
Errors in the OLAP storage engine: An error occurred while processing the 'Patient Diagnosis' partition of the 'Patient Diagnosis' measure group for the 'MSCPROJECT' cube from the Analysis Services Project1 database.

Errors in High Level Relational and OLAP Storage Engine

Hi Edward,

I have tried to go to the Partition tab of BI Development Studio. When i click the partition tab of the Development Studio, it discards an error that " An error prevented the view from loading".

Could you please outline me the steps of how to go about this.

I am really stack.

Ronald

Please, could someone bail me out on this.

Ronald

|||

Looks to me something gone wrong with your project. It is also possbile BI Dev Studio installation got corrupted.

I would suggest:

First, try re-create your cube. See if you can create more partitions for you cube and BI Dev Studio allows you to add new partitions.

Second. If you still getting an error trying to navigate to the partitions tab, try re-installing SQL Server on your machine.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||I also found this error last week. My data source is ORACLE database. This raised when I used "OracleClient Data Provider" for provider in Data Source. When I changed the provider to "Native OLEDB\Oracle Provider for OLE DB", this problem was solved.

Hopefully, this post can help you.

Ashari Imamuddin

Errors in High Level Relational and OLAP Storage Engine

Hi Edward,

I have tried to go to the Partition tab of BI Development Studio. When i click the partition tab of the Development Studio, it discards an error that " An error prevented the view from loading".

Could you please outline me the steps of how to go about this.

I am really stack.

Ronald

Please, could someone bail me out on this.

Ronald

|||

Looks to me something gone wrong with your project. It is also possbile BI Dev Studio installation got corrupted.

I would suggest:

First, try re-create your cube. See if you can create more partitions for you cube and BI Dev Studio allows you to add new partitions.

Second. If you still getting an error trying to navigate to the partitions tab, try re-installing SQL Server on your machine.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Hopefully, this post can help you.

Ashari Imamuddin

Thursday, March 29, 2012

Estimating growth

Estimating growth

Tuesday, March 27, 2012

Estimate storage saving of varDecimal

Estimate storage saving of varDecimal

Estimate storage saving of varDecimal

Monday, March 19, 2012

Errors in the OLAP storage engine: The attribute key cannot be found

Errors in the OLAP storage engine:

Errors in the OLAP storage engine (first deployment using AdventureWorksDW)

Errors in the OLAP storage engine

Errors in the OLAP storage engine

Errors in the OLAP storage engine

Sunday, March 11, 2012

Errors in OLAP storage Engine: The attribute Key cannot be found: URGENT

Errors in OLAP storage Engine: The attribute Key cannot be found: URGENT

Errors in High-level Relational Engine and OLAP storage Engine

Errors in High Level Relational and OLAP Storage Engine

Errors in High Level Relational and OLAP Storage Engine

ERROR: Subreport

Blog Archive

About Me