Since we can not run the QODBC in unattended mode, we are forced to leave the QB session open in a console session. It works for our Customer, Item and several SP_Reports downloads thru several SSIS packages after midnight.

However, we now have a need to download the whole Invoice and Credit Memo tables that contain more than 70K records every night. The only way to do it is using Optimizer with NOSYNC mode.

To make a long story short, after different problems/issues, we finally use the NT scheduler to run odbcupd.exe around midnight before the downloads.

Problem is, we don't think our SSIS package run under SQL Server agent is USING the optimizer. It takes more than 3 hours to finish the Credit Memo table along, but only a few minutes in Visual Studio running the same SSIS package.

So, what is the difference between running under SQL agent versus running directly in Visual Studio? Our SQL server agent logon account is the local account  "System"

Thanks.

Select * from SalesOrderLine Calldirect where timemodified >= {fn TIMESTAMPADD(SQL_TSI_MINUTE, -15, {fn NOW()})}

Calldirect is used to grab the new and any modified rows from QuickBooks directly bypassing any optimizer updates (or issues).