2008

I believe this is the crux of the issue although I cannot figure out why. I've tried all duplex modes and transfer rates w/o success

Resource ...

For me this was an incorrectly configured AD OU

I wouldn't mess with the in place upgrade if I were you...

Not sure if it makes sense or not, perhaps a guru could comment...

Possibly delete the indexes, do the inserts, then recreate the index.

I know it's an old post but there's some info here if you're still looking

http://blogs.msdn.com/psssql/archive/2009/11/03/the-sql-server-wait-type-repository.aspx#10004848

FYI, https://connect.microsoft.com/SQLServer/feedback/details/552707/job-disabled-and-schedule-enabled?wa=wsignin1.0#tabs

Sounds like the lesson for the day is to use sp_update_job to enable / disable and to avoid the GUI

I just tried to reproduce the issue as well and couldn't do it.

This DID occur on my production box this morning though.

GUI

Try restarting sql server agent service after disabling the job...seems to work for me.

I'm having the same issue, job disabled, schedule enabled, job runs.

(I'm running sql 2008 sp1)

My jobs were created via a maintenance plan, were yours too?

100 should work just fine, it's really SQL 2000 (80) that's the issue.

I use the script all the time on SQL 2005, SQL 2008 servers. If even 1 db...

The script is written such that the compatibility level all databases must be 90.

To check run

select compatibility_level from sys.databases

interesting....

TCP Offloading again?!