I am planning to use profiler to find if Auto_stats is an issue or not, is there a better way?

thanks everyone. I will get back here with some updates. Thanks

I tested this out today , running a trace all i saw is shared locked. Are you sure this will lock the table , like keep an X lock? Mentioned...

alright let me try that. Thanks

That might work, but might also break the access of others.Thanks

?

Sandhya:

I recently used this article as reference and works perfect. You should be able to see the message in the sql log if configured correctly. Thanks

Unfortunately we do not have power shell running.Thanks

Thanks. I ran trace with event "Peformace Statistics" and that was shown throughout the trace. Is that an indication of bad statistics?

Thanks and will do so.

update..from the previous post which i mentioned step ii is also part of step i. My question is same now, what is the difference between GUI and running through...

OK if i follow this correctly you mean to say the...

i ran the trace now after disabling the job through GUI and the below following procs are being executed:

EXEC msdb.dbo.sp_update_job @job_id=N'5bd63372-c981-4cef-b18f-2db4b464ee43',

@enabled=0

EXECUTE @retval = sp_verify_job_identifiers '@job_name',

...

Is there a MSFT article which points to this? Thanks

sql 2005 stnd edition 64 bit with SP3...