analysis serices, cubes and access

How to get data from cubes in analyses manager to MS access using for
example ODBC ? Does existe any other posibilities to get data from cubes
directly to the accees ?
thanks
KrisHow did you get them in cube format to begin with? If you mean transfer
the data from the underlying warehouse in SQL to Access you can use DTS.
The example that ships with AS (foodmart) is actually in Access, so you
can build cubes from data within Access. If this doesn't answer your
question, please elaborate.

HTH

Ray Higdon MCSE, MCDBA, CCNA

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!sql

An internal consistency error occured (SQL-DMO(ODBC SQLState: 42000)

Hello!

I am trying to restore a dataset and I receive this error message
SQL-DMO(ODBC SQLState: 42000)
An internal consistency error occured.

Does anyone know what this means?
Could it be a different sort order? (But ususally then you receive an error saying something about the sort order.)

Thank you for any help!

marjoOriginally posted by marjo
Hello!

I am trying to restore a dataset and I receive this error message
SQL-DMO(ODBC SQLState: 42000)
An internal consistency error occured.

Does anyone know what this means?
Could it be a different sort order? (But ususally then you receive an error saying something about the sort order.)

Thank you for any help!

marjo

Hallo Marjo,Regarding this call did you receive a solution to this problem?I am experiencing the same issue with a user I am supporting

I would be very glad if you coukd assist|||Hallo Rutger,

I cannot remember what the solution was. But later I was able to restore it without errors. It was something I did wrong - the data/log file selection, size of the db or something like that-, but I am not sure anymore because this happened already months ago.

Groeten,
Marjo|||Check the SQL error logs to find out the error ... that is the best place to find out why this is happening|||Originally posted by marjo
Hallo Rutger,

I cannot remember what the solution was. But later I was able to restore it without errors. It was something I did wrong - the data/log file selection, size of the db or something like that-, but I am not sure anymore because this happened already months ago.

Groeten,
Marjo

thanks,for your assistance|||Originally posted by Enigma
Check the SQL error logs to find out the error ... that is the best place to find out why this is happening

Enigma,where would I find the error logs because I looked in the events.log but nothing is showing

Brgs
Rutger|||SQL server logs would be in the [Installation Directory]\MSSQL\LOG folder. Check the latest one i.e ERRORLOG|||What is the level of Service pack on SQL?|||Originally posted by Satya
What is the level of Service pack on SQL?

Good Day,I do not have any service pack loaded yet,I hope this is a solution

Regards|||Did you find anything in the error logs ??|||Originally posted by Enigma
Did you find anything in the error logs ??
Nothing which points out the error,the problem arose when the user crashed his hard disk and recovered the data,all backups from that disk give the same error time and time again

I tried to restore this disk on various other sql servers but the same thing,it looks like the data integrity is hindered

an interesting bug for SSIS

I have a very simple SSIS package that imports data from ODBC source. There are two "Time" columns in source, but When this table is created in SQL2005, it give me "bigint"!!!

How can this happen?

I tried to import data to SQL2000, those two columns are created as "smalldatetime" properply.

Thanks.

Please provide more details about the package and the ODBCsource. When you say 'Time' does that mean the date is no part it?|||Thanks.
Right. "Time" means date is not part of it.

My package detail:
ODBC source: it is D3 data base. I am using .NET Providers\Odbc Data Provider to connect to the data source.

destination: SQL2005.

Actually, all "Time" field is imported as "bigint"

Cheers.|||I have no idea what a D3 database is; in my case I had to deal with an old PErvasive DB that had a similar case. It had separate columns/data type for the date and the time. I solved it by within the SQL query I use to extract the data. There was a native sql function that allowed me to 'concatenate' the date and time columns into a single column; then the data reader component could see it as a dateTime data type. Conclussion: try to resolve it right on the query.|||

Thanks.

I don't want to "concatenate" the date and time column and that table doesn't has date column at all!

The problem is table created by that package is with wrong data type. But DTS package in SQL 2000 created table properly. This is not about setting the query to select the data.

Can you show me how the query looks like, please?

|||

Qiuwei wrote:

Thanks.
Right. "Time" means date is not part of it.

My package detail:
ODBC source: it is D3 data base. I am using .NET Providers\Odbc Data Provider to connect to the data source.

destination: SQL2005.

Actually, all "Time" field is imported as "bigint"

Cheers.

This is most likely the provider stack. Are you using a different provider to what you used in DTS?

-Jamie

|||In my SQL2000 DTS package, I use "Other(ODBC Data Source)"

Thanks.|||

Which ODBC provider?

It could be that the dotnet provider for ODBC doesn't play very well with whatever ODBC provider you have. You may want to look into getting a different ODBC driver.

-Jamie

|||

Thanks.

Sorry for the late response (toob busy these days).

To get around this problem, we make the source data (time) as varchar type and imported as nvarchar.

Question is that why SQL server doesn't have "Time" data type which is quite useful?

Cheers.

|||

Qiuwei wrote:

Question is that why SQL server doesn't have "Time" data type which is quite useful?

many many people ask the same question. Which is why it (plus some other new things around dates and times) will be coming to a version of SQL Server near you very soon.

-Jamie

|||

That will be great!

Thanks.

Alternatives to ODBC in Access 2000

Hello All,

Have a bit of a problem that I hope someone will be able to clarify. I have an Access 2000 mdb that connects to two SQL Servers by way of ODBC. Now due to several failures with OBDC (Would get ODBC errors when the connection to SQL was proven not to be down), my boss wants me to eliminate ODBC from the equation and directly connect to the SQL Servers. Now he has suggested I use SQLOLEDB as an alternative, but thus far I seem to only be able to implement this on the VB side of it, which would mean I'd have to send all my SELECTS UPDATES DELETES etc manually, which would turn a minor update into a complete overhaul. I know there is a way to link tables directly with SQL in Access 2002, is there a similar option in 2000, and how would I go about it?

Thanks!Did a little research and it seems possible to use ADP files with SQLOLEDB, but I don't know how or even what ADP files are.