SQL Server ODBC error

[teccum]

All,

When I try to access the elements through the system Hierarchy, I get an ODBC error. My datawarehouse database is SQL Server 2000 and I have defined a ODBC DSN in my computer pointing to the datawarehouse database (datawarehouse DSN)in SQL Server and I have created a database instance (datawarehouse)pointing to the DSN which I created for the Datawarehouse and my metadata is MS Access (Tutorial metadata - I am using the mstr provided metadata in MS Access for this project). I am getting this error for all the tables I access.

"Query Engine encountered error; Execute Query failed, Error type: odbc error, odbc operation attempted;
SQLExecDirect.[s00002:208: on HSTMT][Microsoft][ODBC SQL Driver] [SQL Server]Invalid Object name 'DW_C_YEAR'."

I updated the schema after defining the project and while reading the warehouse catalog, I was able to read the no of rows by selecting the row count for each table. But I am getting the error when I access the elements for the attributes and also when I try to run the report.

Do anyone have idea where I am going wrong. Can someone
help me on this?

Thanks
teccum.

 

[teccum]

All,

I got it. I forgot to import the prefix for the table after reading the warehouse catalog.

Prefix can be imported by 'right clicking' on the table in the warehouse catalog window and then selecting 'import prefix' option. This makes warehouse catalog import the prefix along with the table structure from the database.

Thanks
teccum.

 

[andreadefranco]

Hi,
I'm a new user/developer of Microstrategy.
I've the same error on Teccum :
"Query Engine encountered error; Execute Query failed, Error type: odbc error, odbc operation attempted;
SQLExecDirect.[s00002:208: on HSTMT][Microsoft][ODBC SQL Driver] [SQL Server]Invalid Object name 'DSSMDSYPROP'.."

Do anyone have idea where I am going wrong.
Can someone help me on this?

Thanks
Andy

 

[jonhoward]

Does the table exist in the metadata? If no, then your metadata is broken, or you're trying to connect to the 'wrong' database.

If yes, check who the owner of the table is (no doubt the rest of the metadata tables will have the same owner).It's possible the owner of the tables isn't referenced during authentication, in which case:
Right-click on the project source;
Select "Modify Project Source" and go to the "Metadata Table Prefix" tab;
In the "Table Prefix" field, enter the user name in question followed by a period (.);
Select OK (which will close the connection to the project source);
Reconnect