Invalid object name 'OlapObjects'

Hi,

I installed the analysis server 2005 version.

When I'm trying to get the databases in an OLAP server using DSO it gave me the error, "Invalid object name 'OlapObjects' "

Following is my vb code.

dsoServer.Connect (sServer)
For i = 1 To dsoServer.MDStores.count
Set dsoTempDB = dsoServer.MDStores(i)
ComboboxName.AddItem dsoTempDB.name
Next

I tried installing Analysis server 2005 several times, and installed service pack 2 as well. But still I get this error.

Please help.

Thank you.

First. You should really take a look at using AMO object model to perform any tasks with Analysis Services 2005 . AS2005 is completely different from AS2000 and AMO is way better way to perform any tasks with it. You will be way better off investing your time and energy with looking into using AMO.

Having said that, if your application absolutely requres DSO here is set of instructions on how to get it working http://msdn2.microsoft.com/en-us/library/ms403370.aspx

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

|||

Hi,

Thank u very much for the information.

I was able to connect to my analysis server 2000 repository according to the steps given in the URL .

I have another question related to DSO. Is it possible to connect to analysis server 2005 using DSO as well ?

I also agree with you about using AMO. But for the moment I have to connect to the analysis server using DSO. But I would looking into using AMO later.

Thanks again for your help.

|||

It is possible to connect to AS2005 using DSO.

In fact DSO will under the covers invoke AMO, it will pass all the information to AMO and then AMO will make the conneciton.

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

|||

HI Again,

Do you know what's the provider I should use when giving the RepositoryConnectionString for DSO to get databases configured in Analysis server 2005.?

When I used OLE DB provider for Analysis service 9.0 , It gave the following error.

"Query (1, 10) Parser: The syntax for ',' is incorrect."

Thanks

Umanga.

|||

I think there is a little bit of misunderstanding. The paper on http://msdn2.microsoft.com/en-us/library/ms403370.aspx states you should use something like Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Program files\Microsoft SQL Server\MSSQL.n\OLAP\DSO\msmdrep.mdb;Persist Security Info=False

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

|||

Hi,

It worked for getting the databases configured in Analysis server 2000 from sql server 2005.

I want to get the newly created databases using SQL Server Business Intelligence Development Studio in sql server 2005 from DSO.

For example, now when I check from the sql server management studio, it shows food mart database (2000) and my new database created in 2005 ,

But using the "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Program files\Microsoft SQL Server\MSSQL.n\OLAP\DSO\msmdrep.mdb" it shows only database Food mart (configured in 2000)

Do you think it's possible to get databases added in 2005 using DSO as well, or should I use AMO?

Hope my question is clear now

Thanks

Umanga.

|||

As I mentioned earlier, support for DSO is very limited. It is there mainly for backward compartibility of existing applications and exisiting cubes.

The way DSO works with AS2005 is that it will not show you the server cube created using BI Dev studio. For that you will need to start using AMO object model.

If looks at functionality offered by AS2005 and new ideas it has, it is very different from AS2000. So many properties, objects and concepts are different. DSO simply not the way to manager AS2005.

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

|||Hi.

When you configure Analysis Service, you need to create the "OlapObjects" table.

Script:
CREATE TABLE [dbo].[OlapObjects](
[ID] [varchar](36) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[ParentID] [varchar](36) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[ObjectName] [nvarchar](150) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[ClassType] [int] NOT NULL,
[ObjectDefinition] [ntext] COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[LastUpdated] [datetime] NULL,
[Changed] [bit] NULL,
[Version] [int] NULL
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
GO

After you create it, you can build the cubes.

Cláudio Hidetoshi.
Rio de Janeiro.

Invalid character in a report

Hi!

Trying to generate a report (using WebForm ReportViewer, from dynamically created RDL report and SQL Server 2005 OLAP cube), if a database field contains control characters (code < 0x20), Reporting Services generate following message:

' ', hexadecimal value 0x02, is an invalid character. Line 1, position 2376.

Is it possible to ignore that? I don't care if browser shows an octopus, the report must work.

Thanks, Andrei.

Could you publish RDL (or e-mail it to me)?

thanks!

|||

Lev,

I've just emailed RDL and other details to you.

I could reproduce the problem using sample AdventureWorksDW and OLAP (standard edition).

Create an OLAP table report, put e.g. Model Name in one of columns. The report works fine. Now change e.g. ModelName for one of products, to include control character(s), e.g.:

update DimProduct
set ModelName = 'Mountain-100 ' + char(31) + char(2) + ' AB'
where ProductAlternateKey = 'BK-M82S-38'

Reprocess Product dimension.

Refresh the report. Once Montain-100 model is about to be displayed on the page you should get following message:

hexadecimal value 0x1F, is an invalid character. Line 1, position 2385.

I've just noticed that after the change applied even OLAP browser of SQL Server Management Studio generates the same error if only the ModelName is about to be displayed.

So it may be Analysis Service's problem indeed.

I've tried with non-OLAP reports in Reporting Services, and they work fine, displaying square placeholders.

|||That is known AS issue. Certain control characters cannot be transmitted from server to client.

Invalid character in a report

Hi!

Trying to generate a report (using WebForm ReportViewer, from dynamically created RDL report and SQL Server 2005 OLAP cube), if a database field contains control characters (code < 0x20), Reporting Services generate following message:

' ', hexadecimal value 0x02, is an invalid character. Line 1, position 2376.

Is it possible to ignore that? I don't care if browser shows an octopus, the report must work.

Thanks, Andrei.

Could you publish RDL (or e-mail it to me)?

thanks!

|||

Lev,

I've just emailed RDL and other details to you.

I could reproduce the problem using sample AdventureWorksDW and OLAP (standard edition).

Create an OLAP table report, put e.g. Model Name in one of columns. The report works fine. Now change e.g. ModelName for one of products, to include control character(s), e.g.:

update DimProduct
set ModelName = 'Mountain-100 ' + char(31) + char(2) + ' AB'
where ProductAlternateKey = 'BK-M82S-38'

Reprocess Product dimension.

Refresh the report. Once Montain-100 model is about to be displayed on the page you should get following message:

hexadecimal value 0x1F, is an invalid character. Line 1, position 2385.

I've just noticed that after the change applied even OLAP browser of SQL Server Management Studio generates the same error if only the ModelName is about to be displayed.

So it may be Analysis Service's problem indeed.

I've tried with non-OLAP reports in Reporting Services, and they work fine, displaying square placeholders.

|||That is known AS issue. Certain control characters cannot be transmitted from server to client.

Introduction to OLAP CUBES

Hi,

I was wondering if I could get some help in how to get started with designing OLAP CUBES. I have done many other reports using matrix also. I wanted to use this technology in one of my reports so that my users can drag and drop data the way they want it, just like a pivot table in excel. Thanks,

-Rohit

Hi rogupta,

What you need is Analysis Services. I suggest you get familiar with terms like fact tables and dimension tables. Building a cube isn't that hard to learn but you need to do some excercises. Also get familiar with denormalizing tables, the way you build the tables is important for drilling down in the cube.

The following provides some samples if you're using SQL Server 2005: http://www.microsoft.com/downloads/details.aspx?FamilyID=E719ECF7-9F46-4312-AF89-6AD8702E4E6E&displaylang=en

Also have a look at http://www.microsoft.com/sql/solutions/bi/bianalysis.mspx for SQL Server 2000

Good luck!

Worf