word for create a dev server

Question

word for create a dev server

sqlfriend

SSC Guru

Points: 52781
More actions
February 15, 2018 at 4:07 pm

#333598

I have a question about a correct term or word I should use;
When we have a production server, and later somebody request to have a dev server install, with the almost same functionality as production server
what verb should I use,
Duplicate production server to dev,
copy the server,
replicate a server (which easy to confuse with replication, so I don't like)
Clone the server,
Mimic the production,
Thanks,

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1004356 More actions · Answer 1

"Clone" would be the term that I would use but, no matter which term is used, it usually requires some clarification as to what you want to do.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Alexander Zhang Default port Points: 1497 More actions · Answer 2

sqlfriends - Thursday, February 15, 2018 4:07 PM
I have a question about a correct term or word I should use;
When we have a production server, and later somebody request to have a dev server install, with the almost same functionality as production server
what verb should I use,
Duplicate production server to dev,
copy the server,
replicate a server (which easy to confuse with replication, so I don't like)
Clone the server,
Mimic the production,
Thanks,

I think you can put clone in your list. But, you probably need different solutions for different cases. Two tips,
1. Is it necessary that Dev has as much data as PROD? For some cases on VLDBs, a data subset might be enough for DEV.
2. Is there any sensitive data? If so, it might be risky to copy them to lower ENV.

GASQL.com - Focus on Database and Cloud

DesNorton SSC-Insane Points: 24387 More actions · Answer 3

You may also need to scrub the production data before making it available to dev/qa.
Do your devs REALLY need to see real PI data? GDPR could really bite you in the @$$ on this one

How to post data/code on a forum to get the best help.

Sue_H SSC Guru Points: 90860 More actions · Answer 4

sqlfriends - Thursday, February 15, 2018 4:07 PM
I have a question about a correct term or word I should use;
When we have a production server, and later somebody request to have a dev server install, with the almost same functionality as production server
what verb should I use,
Duplicate production server to dev,
copy the server,
replicate a server (which easy to confuse with replication, so I don't like)
Clone the server,
Mimic the production,
Thanks,

I would probably not use replicate either. I'd skip clone as that can be seen as a way to implement (cloning a server is a specific method) and may not work in your case or not something the company does. I would probably ask for a dev server like <production server name> and just explain you need it to be like the production server.
Considerations for handling of the data would likely come after you actually(hopefully) get a dev server.

Sue

HappyGeek SSCoach Points: 18729 More actions · Answer 5

DesNorton - Monday, February 19, 2018 1:00 AM
You may also need to scrub the production data before making it available to dev/qa.
Do your devs REALLY need to see real PI data? GDPR could really bite you in the @$$ on this one

+1 and +100 on the GDPR front if sensitive data is involved!

...