Go-Live Best Practice

[snowsingh]

Hi guys,

For my project we just have two environments, ie. Dev and Production (NO QA environment!!) .

It is time for go-Live, I can go ahead with any of the following two approaches :-

1. Move update sets one by one from Dev to Prod.

2. Clone the envirionment directly from Dev to Prod, and clean the test data.

(If we are going for approach number 2, what should I keep in mind inorder to avoid existence of any orphan records ?).

Guys! I am in a fix! please help me and tell me what's the best practice!

Thanks in advance.

[Tom Alday]

I would personally move everything via update set, testing after each commit. If you clone Dev over Prod and something is severely messed up you now have 2 broken instances and will need to request a zboot.

[snowsingh]

Hi Tom,

I totally agree with your point. Presently my Prod Instance is Raw Instance(same as demo).

This will be the first time we will move any changes to Prod. So considering this, i thought to clone my prod from dev.

And then, I can delete my all the test tickets from Prod. Presently, i implemented only ESS, Incident and change module.

Please Suggest!!

Thanks,

Varun Singh

[snowsingh]

Hi Tom,

I totally agree with your point. Presently my Prod Instance is Raw Instance(same as demo).

This will be the first time we will move any changes to Prod. So considering this, i thought to clone my prod from dev.

And then, I can delete my all the test tickets from Prod. Presently, i implemented only ESS, Incident and change module.

Please Suggest!!

Thanks,

Varun Singh