SPAM Upgrade

[Former Member]

Is patch upgrade done directly in Production environment or it is done in Development, then imported to testing and production.  And is this process followed every time?  do we never upgarde patch in production environment?

[Former Member]

Never!  That is absolute.

Think of it this way.  The patch changes the code in Production.  You can't really say what it changed.  It changed a lot of stuff.  Now you go back and apply a note in development.  That note is applied based on code that is no longer in production.  When you transport it to production, it puts older code into production.  For instance parameters may no longer match.  The whole system can then crash.

So, should you have done the first (patch in production), you could never use any transport ever again without first copying all of production back over development (and your q box).  It would have been easier to have done it right the first time.

Neal

[Former Member]

Que 1)so you  mean to say that we cant perform  transport back to Development  or testing environment from Production environment ?

Regards

Kondal

[Former Member]

You can. You could transport to development.  And then you could transport to Q.  But what did you gain by doing so?

So let me tell you what you lost.  Going direct to Production means that if something goes wrong, Production is dead!  Your company can't use it until you rebuild it.  If you restore from backup, you will probably loose data.  Stuff happened between the last backup and your package import into Production.  Restore from backup can take a while.  And then sometimes the DB won't come up.  Then you have to roll in logs.  But some of them may leave the DB inconsistent.

Lots of bad.  Nothing good.

Neal