Well, this is quite disappointing

I created the tables and asked for the execution plan. This is what I got:

StmtText                                                                                                                                                                         

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

select myOrd.Order_No, myiT.Item_No,...

Totally agree!

The statements should return identical recordsets.

I set up the simple trace session I described in my previous post, then ran this batch within QA:

SET QUERY_GOVERNOR_COST_LIMIT 1

select o.orderid,p.productid

from orders o

cross join [order details] p

This is the...

You could set up a trace with SQL Profiler (or sp_tracecreate/sp_trace_setevent) for the Errors and Warning:Exception class, selecting at least Error, SPID, LoginName, NTUserName, DBUserName columns and maybe filtering for Error 8649. That...

Is your table a heap?

Could you post the extimated execution plan?

Have you monitored Sql Server activity, including the Freespace scans/sec counter from the SQL Server:Access Methods?

ThomasH,

I had already thought of using DMO or a JOB, but I decided to use them as a last resort, mainly becouse I think they would be an inelegant solution...

Maybe I haven't made myself clear enough.

The problem is not about the data: using the first format file example in my initial post I can load the flat file without...

Unfortunately increasing MAXERRORS doesn't help at all, because when the format file is wrong the error occurs before loading.

Also, I'm strictly bound to using sp's, no DTS.

Well, I think we'll...

As you can see from my example format file, the field PKCheck is not supposed to be loaded from the flat file. In this case tha flat file would only...

There are a few possibilities:

1) use SET STATISTICS TIME ON;

2) watch how long the COMPILE lock is held on the sp;

3) using the Profiler, trace the time between the event...

There are a few possibilities:

1) use SET STATISTICS TIME ON;

2) watch how long the COMPILE lock is held on the sp;

3) using the Profiler, trace the time between the event...

One of my customers had a similar problem, though they were already using a stored procedure: during analisys of their system and stored procedures, I noticed that one sp was...

Steve,

I totally agree with you.

Maybe the error message is different when it comes from Sql Agent? Anyone knows?

Salvor

You're right.

I picked up the correct answer by choosing the one with less errors 😉

Anyway, the only error I found in the 'correct' answer was the use of 'Driver=SQL Server'...