Showing posts with label informix. Show all posts
Showing posts with label informix. Show all posts

Friday, March 23, 2012

Problems Creating a Cube using Informix IDS 10.0 as Data Source

Greetings:

I am a n00b trying to create a new SQL Server 2000 Analysis Services Cube using Informix IDS 10.0 as the data source. The trick is that the raw data needs to stay in IDS -- no ETL to get the data into SQL Server.

I have installed the Informix client stuff on my SQL Server computer, but when I try to use the "normal" way to create a cube, I am having problems. Here is what I am doing:

1. Right-click "Data Sources" folder under the new AS database I just created -- select "New Data Source".
2. Select "Informix OLE DB Provider".
3. Type in connection info, and click "Test Connection". The test succeeds!!!!!
4. Save it.
5. Right-click "Cubes" folder under the new AS database -- select "New Cube", then "Wizard".
6. When I am supposed to see a list of tables from my newly created data source, I see just an error that says AS cannot connect to IDS.

I am confused by the fact that AS is apparently either using different info or a different method to connect to IDS than what it used when I clicked "Test Connection" when I created the data source.

Hopefully, someone has some past experience getting these 2 products to "play nice".

Any assistance would be greatly appreciated.

-Joe

Joe, did you have any luck resolving this? I'm attempting to do the same and just getting started. Thanks!

Problems Creating a Cube using Informix IDS 10.0 as Data Source

Greetings:

I am a n00b trying to create a new SQL Server 2000 Analysis Services Cube using Informix IDS 10.0 as the data source. The trick is that the raw data needs to stay in IDS -- no ETL to get the data into SQL Server.

I have installed the Informix client stuff on my SQL Server computer, but when I try to use the "normal" way to create a cube, I am having problems. Here is what I am doing:

1. Right-click "Data Sources" folder under the new AS database I just created -- select "New Data Source".
2. Select "Informix OLE DB Provider".
3. Type in connection info, and click "Test Connection". The test succeeds!!!!!
4. Save it.
5. Right-click "Cubes" folder under the new AS database -- select "New Cube", then "Wizard".
6. When I am supposed to see a list of tables from my newly created data source, I see just an error that says AS cannot connect to IDS.

I am confused by the fact that AS is apparently either using different info or a different method to connect to IDS than what it used when I clicked "Test Connection" when I created the data source.

Hopefully, someone has some past experience getting these 2 products to "play nice".

Any assistance would be greatly appreciated.

-Joe

Joe, did you have any luck resolving this? I'm attempting to do the same and just getting started. Thanks!sql

problems connection to Informix database

Hi,

I have a MS SQL 7 running on one machine and want to connect to a Informix database on another machine.

But I always get the error
Server: Msg 7319, Level 16, State 1, Line 1
OLE DB provider 'MSDASQL' returned a 'NON-CLUSTERED and NOT INTEGRATED' index 'ind_new_id' with incorrect bookmark ordinal 0.

I have installed the newest version of "Microsoft Data Access Components" and I have the latest Informix odbc driver

When I try to test the connection in the ODBC Data Source Administrator the test returns fine.

Anyone knows what my problem might be?One of the post in this forum refers
The problem is caused because most providers including SQL Server OLE DB provider do
not support index seek.

The 'index as access path' should not be checked when creating a linked server using
the SQL OLEDB. There is a provider level option which is read by the SQL Server from
the following registry.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Providers\SQLOLEDB\IndexAs
Accesspath. Please check whether the value of the above registry key is 0. If it
isn't , please change it to 0 and try the remote query again.

If it doesn't work, I suggest you rebuild a linked server using the SQL OLEDB without
checking 'index as access path'.