"Microsoft" Time

[SimonMac]

Does anyone understand "Microsoft" time?

Exactly 24 hours ago I had a script which estimated to finish in 21 hours time, its now still showing 16 hours remaining.

[Spacecadet]

Does anyone understand "Microsoft" time?

Exactly 24 hours ago I had a script which estimated to finish in 21 hours time, its now still showing 16 hours remaining.

It's always an estimate based on current disk read/write speeds and processor performance. If anything else comes along and starts consuming those resources then the estimate will need to be changed!

What is it you're trying to do exactly?

[SimonMac]

It's always an estimate based on current disk read/write speeds and processor performance. If anything else comes along and starts consuming those resources then the estimate will need to be changed!

What is it you're trying to do exactly?

Running a data migration script, it is a chuffing great big database on a tulip test machine. In production it took 3.5 hours, so far its on 39 hours

[Spacecadet]

Running a data migration script, it is a chuffing great big database on a tulip test machine. In production it took 3.5 hours, so far its on 39 hours

define chuffing big... I've seen scripts that take a long time before, once I get hold of them they learn to behave and load in minutes not hours

[fullyautomatix]

define chuffing big... I've seen scripts that take a long time before, once I get hold of them they learn to behave and load in minutes not hours

WHS. Better look through the script and perform a surgery on the unnecessary for loops and cursors etc.

[NickFitz]

Obligatory xkcd reference:

[VectraMan]

Acronis TruImage always estimates the backup as taking 49,170 days. Microsoft aren't the worst.