Loading more than 1 million of Rows from Database Crashes

[#1]

With a small database the report works but going to production with millions of rows after reading more than 1 million it says:

OLEDB read failed

InputTable:

SQL SELECT etc.

[Anonymous]

Miguel

I'd suggest your first check :

Does your Dev & Production run on different servers ?

• Are the correct database clients installed on the Production Server ?

Using different AD Accounts ?

• Does the Production user have correct rights ?

Best Regards,     Bill

[#3]

Also take a look if there is no firewall in the middle that is kicking the connection out...

[#4]

Actually I'm running on local machine and just changed the connection string to use a remote database instead of my local test database, which is a small one.

[greg-anderson]

I agree with the others.  This appears to be a connection issue, rather than a matter of data size.  Make sure your ODBC drivers and connection parameters are identical, and check for firewall issues.

[#6]

So why does it only fail after reading 1 million of rows?

[#7]

The OBCD drivers are the same, I told you that I'm using my local machine.

[chiru_thota]

We also faced the same issue.Because after certain time your connection to data base will be time out.

That depends on your database settings and you can check with DBA.

work around we have used.

Let us say your table has two years data 2013,2014.load the data in two steps while creating a QVD.

connect connection string;

load * from table where year =2013

disconnect;

connect again

load * from table where year =2014;

[greg-anderson]

Mahesh, did Chranjeevi's suggestion work?  I ask because I will undoubtedly face this problem at some point in the future.

I do hope you get a successful data load!

[#10 · Accepted solution]

So just added a connection timeout of 30 seconds to the connection string on the client and it worked.

something like:

Initial Catalog=MY_DB;Connection Timeout=30;