thanks for the feedback sergio.

perhaps put the code into a never ending loop with a waitfor '00;00;10' in it, and the job kicks off on server start only?

As for getting that hour back, no...

Gawd, there's always one. I did say I had never had any problems, which is true :-), and also true for the vast majority

running every 10 seconds is unusual and...

I'd agree with tom here, I've never noticed a problem, clocks going back or forward, other than negative run times recorded in SQL2000. The doco I enclosed with my...

no takers so I will broaden it out a bit:

Has anyone had to update ODBC drivers on the client end when doing a SQL2000 to SQL 2008 upgrade.

anyone hit this...

the effects may be OS dependant, SQL seems to blithely carry on. I have a log shipping set up with jobs running every 15 mins and I enclose a doco...

the...

for what its worth, mine ran fine as scheduled. I have seen some weird negative run times reported, but only under SQL2000.

I'd use dbcc timewarp on that, especially as its already monday. 🙂

...er to explain, we had daylight savings weekend just gone.

patience! Its only been a couple of hours and it is sunday!

Have you looked at the installation log? Otherwise people can only guess.

Be aware that if you have it as a separate install in its own resource group and there is a chance those groups could be active on different nodes then...

Brandie, in case you haven't seen it Brian Kelleys article from this weeks database weekly touches on what you are looking at:

http://www.sqlservercentral.com/blogs/brian_kelley/archive/2010/10/26/why-control-server-doesn-t-cut-it.aspx

Looking at this it would seem if you scanned...

statistical values are held within the database and therefore within the backup so come across with the backup, therefore no need to rerun

EXCEPT

if you are restoring to a different server...

glad that fixed it.

Its the prescribed way to move agent log and yes should have been part of your migration plan. You would have had to time it to be...

presume the old agent log location no longer exists? Did you change the location for the agent errorlog?

USE msdb

GO

EXEC msdb.dbo.sp_set_sqlagent_properties @errorlog_file=N'<New_Errorlog_Location>\SQLAGENT.OUT'

GO