Should developers be given access to production?

Ideally developers should not have access to production database. They should have their dedicated QA/UAT/Test for all type of testing. On the DEV database they can either have DB owner access or DB_datareader and DB_datawriter. Depending on what they are doing permissions can be given.

Should it developers have access to the production environment and if they do to what extent?

Answer: Everyone agrees that developers should never have access to production… Unless they’re the developer, in which case it’s different. Problems in production can be fixed much faster if developers can see the logs, stack traces and core dumps and look at production data when something goes wrong.

Why is there a separate development and production environment?

If you have separate development and production environments, it prevents developers from accidentally messing with or deleting production data. It also prevents sensitive information (e.g. passwords and credit card information) from being made available to people who shouldn’t have access to it.

What is meant by code review?

Code Review, also known as Peer Code Review, is the act of consciously and systematically convening with one’s fellow programmers to check each other’s code for mistakes and has been repeatedly shown to accelerate and streamline the process of software development like few other practices can.

What is a production database?

A production database contains the data you are using for production tasks such as creating and updating features. A product library can also contain the data for production and be a production database. When this is the case, the geodatabase contains tables from the schema of a product library and production database.

What problems do separate environments solve?

Reasons for having separate environments To avoid the issues caused by software development and reducing the risks of blocking business. To reduce risks of unwanted downtime due to developers ad-hoc rigging. To improve the SLA of application and provide better user experience to your users.

Can development and production environments run on a common server?

It is possible, but definitely not recommended. Development involves debugging and testing. Incorrect program can spoil the server’s memory and “hang” it.

Why should code be reviewed?

Code review helps give a fresh set of eyes to identify bugs and simple coding errors before your product gets to the next step, making the process for getting the software to the customer more efficient. Simply reviewing someone’s code and identifying errors is great.

How do you create a production database?

Creating a production database

1. If necessary, open the Product Library window by clicking Customize > Production > Product Library on the main menu.
2. Add data from the production database if you don’t already have it loaded.
3. Expand Production Data.
4. Right-click the database and click Create Production Database.

What is an application DBA?

An Application DBA focuses on database design, development, and writing SQL functions to perform CRUD operations for database applications. They are responsible for change management and performance tuning of the database for the particular applications they’re working on.

What happens if a developer does not access production?

If your developers do not access production then your risk of production outage increases. Developers accessing production doesn’t have to be “playing” in production. I’ve seen my share of developers doing dumb shit in production.

What are the risks of being a software developer?

Developers may be responsible for rolling the changes into production and may have rights to production in those activities. The risks are when developers have access to production and make changes without appropriate review, testing, and approval.

What are the risks of debugging in production?

Debugging in production opens up security problems (exposing private data in memory) and run-time risks that developers and Ops both need to be aware of. Question: Should developers have access to production?

What are the risks of ad hoc changes in software development?

The risks are when developers have access to production and make changes without appropriate review, testing, and approval. Given the examples listed by others one can see ad hoc changes can have real negative business impacts.

https://www.youtube.com/watch?v=84RsYvBJEUA