Apexsql Log |LINK|


Apexsql Log

ApexSQL Log allows you to perform many actions on the database structure, structure of tables, characters in tables, and object level permissions in a real-time, without the need to restart the server, or reload data into the database.

Unlike ApexSQL Log, ApexSQL Audit does not fix data that was accidentally removed or corrupted. It is not a recovery tool, but an efficient way to audit data and permissions changes. It uses SQL Server triggers and database auditing features to log SQL permissions changes to the SQL Server system tables. Recovery or rollback of the log changes is not possible.

ApexSQL Log has two types of reports: log and undo reports. The log reports give you a clear view of database structure and changes. The undo reports are similar to the logs, but instead of user and role names, they list database objects and permissions changed by the user and role. Both of these reports are clickable and the pages open up in a new window so that you can drill down or widen the report if needed.

ApexSQL Log can be used in two different ways: quick and simple mode and deep mode. In quick mode, you can quickly view the contents of the log by entering a database name in the main window and clicking on the button “Go”. In deep mode, you can drill down through the object tree in the log, and drill down into structures that you are interested in. To start the log reader in deep mode, you must specify a search pattern from which you want to drill down into a specific object. For example, if you want to be able to drill down into a specific column value, you must first specify a pattern for that column, for example “W25.”

ApexSQL Log ApexSQL Log reads the transaction logs (online, detached and transaction log backups), searches for DELETE transactions, and creates an un-truncated version of the original table by referencing the checkpointed records. If the table is in the Full recovery model, ApexSQL Log can refer to its Audit file, which keeps backup information for the table, and seek to the audit ID of a lost row and restore it in an undelete operation. As long as the table supports row-level recovery, it can be recovered without any loss of data.
ApexSQL Log With ApexSQL Log, you can create a new (virtual) table by referencing the undelivered records. The audit file of the table is then used to look up the missing records, and the original records are loaded into the table.
ApexSQL Log With ApexSQL Log, you can create a new (virtual) table by referencing the undelivered records. The audit file of the table is then used to look up the missing records, and the original records are loaded into the table. Once the original records are inserted in the table, the data can be searched and audited.
ApexSQL Log ApexSQL Log can return a list of all undelivered records in a table. You can generate a list of a tables undelivered records in a live or backup database in a matter of minutes. You can generate this list for a database that only exists in an online log backup.
ApexSQL Log can also export the audit information stored in the grid to the user-created file. In the exported file, all auditing information about the transaction log file is listed in the order they occurred on the server or SQL Server, all columns are displayed by default. Additionally, the result export file has been greatly simplified and reduced in size. No longer are we able to see the details about Auditing operations, or to have access to all audited information within the file. This is a very good, but also a very poor feature.


Lascia un commento

Il tuo indirizzo email non sarà pubblicato.