Cursor out of time

Hi,

First of all sorry about poor english.
I have the next problem:
I have a store procedure which declares a cursor which is a select from some tables. Im surprised because the sp takes over 10 seconds on working and if i execute the select of the cursor as separate ways, it takes no more one second. Ive changed the select with another easier select and it works 0 seconds, so it seems that the problem is in the select, but only if i use a cursor to save the regs, why????

Thanks a lot.Use the "show execution plan" option to see how the server is executing the three queries. Check to see what it different between them. My guess is that there is something causing the optimizer to make a radically different choice for one or more of the queries, and that is what is making them take longer.

-PatP|||Just don't use cursors. :) What are you trying to do with the cursor?|||Thank you for answer.
I think that I meant wrong.
If I execute the select in the cursor it takes me over ten seconds but if I copy the select and paste in the query analyzer, it takes me 0 seconds. Besides this, if i change the select by other easier one, the cursor takes 0 seconds. I know the first select could be wrong but it works 0 seconds in the analyzer!!!! and inside the cursor there is not any operations.

Thanks a lot...

Cube Processing Error - OLE DB error: OLE DB or ODBC error: Class not registered.

Problem

I get the above error when trying to process the cube.

Environment

Server OS - Windows 2003 64Bit

SQL Server 2005 64Bit

Database - Teradata

Connectivity - OLE DB for Teradata

Testing

- Have successfully tested OLE DB connectivity using Hyperion, connecting using an OLE DB Connection file.

- Get the same error when trying to process a sample MS Access database or Teradata

- Uninstalled and reinstalled SQL Server 2005

If anyone has any idea’s it would be greatly appreciated, thanks.

It might be that the provider (in the connection string of the datasource) is set to the 32bit version (if you used BI Development Studio or SQL Management Studio on a client 32bit machine). Then you deploy and, during processing, the AS2005 server tries to instantiate the provider and fails (because you have the 64bit version of the provider installed on the server machine).

Adrian

|||

Thanks,

I used Visual Studio 2005 to develop a Test Cube on the Server after the installation.

Back Ground

I originally installed SQL Server 2005 using a Local Account but it was then decided that it was best done under a Domain account (Up until this point I could process AS2005 cubes). So I uninstalled SQL Server 2005 and reinstalled using the domain account.

I think somewhere along the way a Registry File has become corrupt. Is there any way to test this?

Next Step

If I am unable to resolve this issue I will re-image the server and hopefully this will remove any corrupt Registry files.

Any other Idea's?

Thanks