Categoria
Argomento
Argomento secondario
Lingua
How to activate ApexSQL Log on remote SQL Server instances (4214767)
It must be activated on each SQL Server instance after the trial period of 14 days expires. ... Otherwise, ApexSQL Log cannot be used on these SQL Server instances, whether they are hosted on a local or remote server machine.
How to create and maintain a full chain of transaction log backups (4211105)
A tutorial on how to use transaction log “chains” to provide sufficient data sources for successful disaster recovery, transaction rollback or database auditing, effectively avoiding a large singular log file.
How to audit operations for dropped or re-created tables with Old Table ID mapping (4216175)
Summary This article describes how to retrieve schemas and objects for the records that are shown as UNKNOWN in the Main grid. ... This happens when the table with the specific ID doesn't exist in the database anymore, and the transactions for that object ID exist in the transaction logs used.
How to execute large SQL scripts (4213449)
This article shows how to execute large scripts created by ApexSQL tools which are too big to be opened or executed by SQL Server Management Studio Query Editor ... Description ... Synchronization scripts, undo and redo scripts, and recovery scripts generated by ApexSQL tools can be so big that SQL Server Management Studio Query Editor can't open and execute them
How to setup an e-mail alert system for ApexSQL tools (4214934)
Summary This article describes how to create e-mail alert system for ApexSQL tools using PowerShell in order to send e-mails upon executed ApexSQL tool providing the necessary information. ... Summary This article describes how to create e-mail alert system for ApexSQL tools using PowerShell in order to send e-mails upon executed ApexSQL tool providing the necessary information.
How to configure continuous auditing in ApexSQL Log (4213573)
Continuous auditing is ApexSQL Log feature which allows seamless auditing of SQL Server database for data and structure changes which affect the audited database. ... This feature also ensures that no duplicate auditing results are audited, regardless of the fact if the auditing output is auditing report of any supported type or a replication (redo) script.
How to automate daily reports with ApexSQL Log (4214753)
We will address two scenarios in this article: ... Everyday documenting of all transactions that occurred (incremental approach) ... To employ the incremental approach for a single database please:
Four ways of handling database/login credentials during automated execution via the CLI (4292458)
Summary ... This article explains how to automate the execution of ApexSQL tools via the CLI while handling the passing of database credentials or using Windows authentication. ... Applies to ... Summary
How to create an undo/redo script in ApexSQL Log (4211340)
This article explains how to use ApexSQL Log to create an undo or redo script. ... ApexSQL Log is a SQL Server auditing and recovery tool which reads SQL Server database transaction logs. ... Along with its auditing capabilities, it provides undo/redo T-SQL script creation which allows you to rollback or reconstruct transactions recorded in the transaction log.
How to use a project file in the CLI (4211094)
This article explains how to use a project file in the CLI. ... This article explains how to use a project file in the CLI. ... Description ... Instead of setting the value of switches directly in the CLI, setting up a project file through the GUI with the desired options pre-set, saves time, because it requires only one switch to be used in the CLI.
Save project as automation script (4213614)
Most ApexSQL tools have a CLI switch to consume a project file. ... This allows for the simplicity and ease of using a project file but also for unattended automation of a batch file or a PowerShell script.
Restore a database to a point in time - part 1 (4218988)
In various scenarios, a SQL Server restore a database to a point in time might be required. ... Typically, the following situations require this type of recovery: ... A data corruption occurred by a user malicious action.
Recover a SQL Server database using only a transaction log file (.ldf) and old backup files (4295743)
Nevertheless, creating regular full database backups doesn’t provide full point-in-time recovery, since restoring the latest full backup will restore a database to a proper state at the time a backup was created, but all changes, both schema and data, which have occurred after the last full backup will be practically lost.
SQL Server transaction log reader use cases (4214391)
One of the most common tasks for ApexSQL Log is to be used as part of a post-incident investigation, usually involving inadvertently or maliciously changed or damaged data to determine who made the changes, what exactly was changed, when and how.
Audit SQL Server database security changes (4300632)
The saying "An ounce of prevention is worth a pound of cure" is ever so true when it comes to SQL Server security. ... <h2>The out-of-the box auditing solution</h2> ... Provided that you use the Enterprise edition of SQL Server 2008 or above you can configure the auditing functionalities which come built in with the SQL Server itself.
Audit SQL Server permission changes to improve overall security (4212981)
One of the most important tasks for a DBA aiming to keep database and the data in it secure and away from unauthorized access or, heaven forbid, malicious changes is to always stay on top of the effective SQL Server permissions his users have over the SQL instances as well as the databases, database objects and data stored in them.
Read a SQL Server transaction log (4213337)
SQL Server transaction logs contain records describing changes made to a database. ... They store enough information to recover the database to a specific point in time, to replay or undo a change.
How to recover views, stored procedures, functions, and triggers (4213390)
Regardless of precautions taken to protect your SQL Server, accidents may still occur, causing serious consequences, such as data and objects loss. ... We will now analyze two possible ways to recover SQL objects - views, stored procedures, functions, and triggers, lost to accidental DROP statement use.
Open LDF file and view LDF file content (4214638)
Every SQL Server database is mapped over a set of operating-system files. ... These files store data and log information. ... Individual files are used only by one database, and data and log information are never mixed in the same file.
How to recover from a SQL Server database data-file corruption disaster (4213387)
The worst-case scenario a DBA can encounter is a SQL Server database data-file corruption (due to physical or some other occurrence, the data files can be damaged and inaccessible) ... Most SQL DBAs have recovery plans for this scenario – creating regular backups and using them later to restore the database to the nearest available point in time, prior the disaster.
Using a SQL log analyzer to audit, replicate and recover data (4214695)
ApexSQL Log is a SQL log analyzer tool which can be used to read different transaction log files in order to perform SQL Server database auditing, transactional replication and data/schema recovery tasks.
Recover a SQL Server database using an old backup and the current transaction log file (4210853)
How to recover a SQL Server database using an old backup and the current transaction log file DBAs have various disaster recovery plans. ... One of the questions they have to answer before setting up a right plan is how much data can they afford to lose.
Tracking DDL changes in SQL Server - the ‘Trouble with Triggers’ (4215984)
Tracking changes is an essential SQL Server security task. ... In this regard, various techniques can be used as a schema change auditing solution. ... One of the most common method are DDL Triggers
SQL Server database Forensic auditing including row history and before-and-after auditing (4215680)
Prevention is one of the most powerful approaches against any inadvertent or malicious events. ... But it is not always possible to prepare for all different calamities which may take place in SQL Server environments.
How to continuously pump transaction log file audit data directly to a SQL Server database (4214684)
In Automating daily transaction log reading, we’ve shown how to automate the process of pumping transaction log data into SQL Server tables with ApexSQL Log. ... The proposed solution revolved around the creation of a batch file which runs ApexSQL Log CLI commands.
Associazione di nuovi prodotti
- Strumenti self-service
- Knowledge Base
- Notifiche e avvisi
- Supporto prodotti
- Download di software
- Documentazione tecnica
- Forum utente
- Esercitazioni video
- Feed RSS
- Contatti
- Supporto tecnico
- Visualizza tutto