yep, I am going to do that and if it still fails, I will have the AD account recreated

"Now back to the question. The nolock is not 100% guaranteed, if there are inserts updates affecting that exact row, or other memory resource issues, and sometimes a clustered index...

Thank you for pointing it out! I was too excited to post and did not understand the lock used here:w00t:

I still don't have a clue of why the blocking...

I think I found out the real cause and hopefully, what I found out will make sense to you..

The SSIS package dose the following things

1) select from table A, which...

OK.. I run a trace when the SSIS runs and here is what I see.. Is that the CAUSE?

SET FMTONLY ON select * from the Table where 1=2 SET FMTONLY...

The blocking session ID is 215 ( from the select statement). Session 142 was blocked and wait type is (LCK_M_IX). There are other processes running that has command 'SET TRANSACTION...

wow.. thank you for all the repies! I learned a lot today!

Here are some facts

1) The select statement is pretty simple. Straight forward 'SELECT * FROM theTable (NOLOCK)' and that...

Thank you for the reply! I see the blocking from Activity Monitor, it says, the select session is 'Blocking' and the 'Insert/update/detelet' session is blocked by the session Id from...

Dost it work? I need to do the same thing: schedule a job to export the reports to a folder.

Make sense and thank you again!

Wow.. I can't believe I got all the attentions from SQL Gurus! This is a great learning experience for me!

Here are the references I have been using. Please let...

Sorry.. another question. What kind of cause you can think of? I heard the sector of the hard drive on that server may have problem...

Thanks a again! One more qustion, Is this logged in msdb..suspect_pages?

select * from msdb..suspect_pages

database_id file_id page_id ...

You are right. I can't change that option. It complain the same thing.. log is full!

Thank you so much for the advice! Could you please let me know how to find out the header of the log is bad?