Entegra mines the transaction log at configured intervals to locate events that match your predefined notification criteria. When Entegra locates an alert condition, the software generates, logs, and sends notification to the person and device of your choosing. An administrator can then view the change that occurred and take corrective action, if necessary. Because Entegra monitors the transaction log and is always moving forward, you won't receive duplicate notifications. Also, Entegra won't be fooled by SQL Serversavvy intruders who aim to directly rewrite the SQL Server transaction log.
In addition to letting you configure notifications about crucial server-level actions, Entegra lets you track and receive notifications about changes to sensitive data. You can configure a notification based on changes to a table or even a column within a table. For example, you would want to know when someone is modifying a payroll table's salary column, to ensure that only authorized users are making changes.
Manage Source Code
Log Explorer and Entegra benefit administrators, but what about developers? A plethora of tools are available for administrators, but you'll find a cor-responding lack of tools for developers. However, this imbalance isn't much of a problem. SQL Query Analyzer provides nearly all the capabilities that a database developer needs to do his or her job. One glaring exception is in the area of source-code control.
The capability to manage multiple versions of source code, revert to previous versions, or compare multiple databases for differences is crucial to the management of applications that have a database back end. Unfortunately, tools that offer such functionality require formalized processes and strict adherence to those processes by developers.
Developers excel at using source-code control when they build applications because source-code control is embedded into every modern development environment. All professional developers use source-code control for their projects. However, in the case of database code, developers write directly against a SQL Server system and almost never manage the source code.
Because developers connect directly to a database server to develop code or modify the database structure, the ability to identify, extract, and archive changes is crucial to understanding the database portion of an application. Embarcadero's DBArtisan Change Manager and Red Gate's SQL Compare each offer a different level of source-code control functionality.
DBArtisan Change Manager lets you configure and schedule a job to extract and archive your database schema. You can then use these archives to view different versions of the database and restore code to a previous state. The solution isn't perfect: You generate archives either manually or through a scheduled job, so the archives won't pick up multiple changes to one object between jobs. In addition to viewing previous versions, you can compare one archive with the next to determine differences. You can also compare an archive with a live database or two live databases to each other. DBArtisan Change Manager can then generate a script that synchronizes objects.
SQL Compare, a competitor of DBArtisan Change Manager, also lets you compare two live databases. When you finish the comparison, the software can generate a script to synchronize the objects. Both products are useful for determining which code has changed on a development server so that you can move the code into production with the next production build.
Prev. page
1
[2]
3
next page 
