• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

Reply to: "Microsoft" Time

Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on ""Microsoft" Time"

Collapse

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

    Leave a comment:


  • NickFitz
    replied
    Obligatory xkcd reference:

    Leave a comment:


  • fullyautomatix
    replied
    Originally posted by Spacecadet View Post
    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.

    Leave a comment:


  • Spacecadet
    replied
    Originally posted by SimonMac View Post
    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

    Leave a comment:


  • SimonMac
    replied
    Originally posted by Spacecadet View Post
    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

    Leave a comment:


  • Spacecadet
    replied
    Originally posted by SimonMac View Post
    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?

    Leave a comment:


  • SimonMac
    started a topic "Microsoft" Time

    "Microsoft" Time

    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.

Working...
X