Client Refresh Standard Practice

[Former Member]

Hello Everyone,

I am wondering if anyone can help me out with the following questions:

How often is a client refresh necessary?

What profile is typically used for a client refresh?

My problem is that we have limited space on our servers but the functionals want all the data from PRD copied to our DEV system so we're trying to figure out the best way to achieve this. Any best practices documents based on this would be appreciated also. Thank you!

[Former Member]

Hi Connie,

As per your query all the activity depend on the company, if company wants to change DEV data as per PRD then you can change. If your development & IMG setting changed is very high then you can refresh data accrodingly. There is not fix timing to referesh the data. I will suggest you first you referest your QAC and give it to your team for checking. I thing your purpose will be solved. After refreshing you have to configure STMS and activate licence in the QAC.

Regards,

Anil

[Former Member]

I think one of the main concerns that we have is that we're running low on disk space. I believe that the functionals want the most data similar as possible but we're not sure which profile is best used to bring over as much data without using a lot of disk space. Has anyone else ran into this issue?

[Former Member]

Hi,

If the objective is to copy producation data to development,then Database Refresh is the best option,but again- if you are refreshing the Development system with a database refresh you will loose all your developments(which was not moved to production) .

The best parctice is to do a database refresh from Production to the qualilty system not to development so that you will have all the functionalities in the quality system for the testing.

The frequency of client refresh depends on the requirements

Regards,

Sam