Advertisements

LawsonGuru Blog

Thought-Provoking Commentary for the Lawson Software Community

How Slow Is Your Upgrade?


It’s a complaint I hear often, although not as often as I used to hear it.   The upgrade programs/process was re-worked to take advantage of sqldbcopy, which solves some of the speed issues for copy jobs (i.e. tables which don’t require conversion).  For those, the copying is done directly on the database server.  However, some of the pre-jobs, loads, and post-jobs continue to be a bottleneck. The way I approach an upgrade is to work with the client to develop a baseline—using the Lawson-delivered programs, and then target the jobs which require tuning. For instance, a recent upgrade project looked like this:

  • Run 1st time, hundreds of hours.
  •  Changed ‘drop index’ parameter, reduced to 213 hours.
  • Re-wrote UG121 setup job, dropping that job ‘s run-time from 54 hours to 31 minutes
  • Re-wrote AR800 post job; went from 91 hours to 12 hours
  • Further address AR800 by replacing with SQL; down to 2 hours.

The final result is an upgrade process that runs in about 30 hours—compared to hundreds of hours—for a 210GB database.

Can your upgrade process be improved?

Advertisements

One response to “How Slow Is Your Upgrade?

  1. The Creeper October 19, 2007 at 11:55 pm

    I’ve heard this before, a conversion/migration can’t span across days for just 210GB!!!!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: