Looks fine? what is the question about?

Why are you using the Native Client driver?

np pleasure.

You are running SQL Server 2005?

If possible, add about 3 runs of IO stats as well...the more info you provide, the quicker and better assistance we can give.

I would suggest you look into it, as you are queries ID rows, which I would assume is Unique, and I would assume the ID column has a primary key?

Adding...

I see what you mean.

do you have indexes on those 2 tables?

downloads a "test.zip" and contains xml's?

Np, pleasure.

Yes, but DONT recreate the jobs, simply modify the existing schedules, by changing the time, and changing it back...

These might help...

http://www.sql-server-performance.com/articles/dba/object_permission_scripts_p1.aspx

and a quick one for per-instance-check:

USE master;

SELECT *

FROM fn_my_permissions(NULL, 'SERVER');

GO

and another for per DB check:

USE master;

SELECT *

FROM fn_my_permissions('master', 'DATABASE');

GO

create a new simple job with a quick t-sql query, schedule it for 5 minutes ahead of now, check if it runs at the exact time.

If it does, I'd say,...

before starting the job, run the following:

DBCC sqlperf(logspace)

after starting the SSIS job, execute it again, every 10 seconds, and see if there is a significant change in the size of...

run

select GETDATE() and confirm you're SQL server returns the exact same date and time as you're Windows Server.

I meant you're system TEMPDB, not the custom temp table..

interesting...

by how much does you tempdb and log grow during this process?