Q: In our development environment, everyone has a system administrator (sa) password, and five groups use one database. After a developer accidentally deletes the data, I cannot determine which data to delete. When a developer updates data in a database, how does one review the workstation or login ID? A: Because you are working in the development environment, you can use the SQL event probe and the system administrator.
Q: In our development environment, everyone has a system administrator (sa) password, and five groups use one database. After a developer accidentally deletes the data, I cannot determine which data to delete. When a developer updates data in a database, how does one review the workstation or login ID?
A: Because you are working in a development environment, performance loss caused by SQL event probe and server tracking does not affect the production environment, you can set a server trace, record the information in the background in a table. Then, you can search for the table to determine who deleted the data.
Obviously, assigning sa accounts to multiple users at a time poses many problems. The following are some measures you should take:
Create a copy of the database for each development team and provide each team with an account that only has access to the database owner. In this way, they will not affect each other.
If every Developer needs sa access (for example, running SQL event probe tracing) and you are running SQL Server 2000 Enterprise or Developer Edition, you can provide each team with an SQL Server instance and its dedicated sa password.
You need to set up a development environment for each project and manage the conflicts among all projects in an integrated environment by a version database administrator. In this case, because the architecture change script has been tested before entering the integration environment, the quality of the production version will be improved.
-The Microsoft SQL Server Development team