カテゴリ
トピック
サブトピック
Fatal action guard: guarding against inadvertent execution of code that may damage or destroy data in SQL Server (4282375)
Fatal action guard: guarding against inadvertent execution of code that may damage or destroy data in SQL Server "<p> There are many opportunities, before, during and even after to guard against potentially fatal actions that may damage or destroy data, like executing an Update or Delete statement without a Where clause.
Before and after auditing in SQL Server (4288509)
Simply archiving information to audit a database is one thing, but successfully reconstructing an audit history to provide meaningful forensic data is another. ... It is important to be able to see a full history of user changes, as well as to be able to reverse changes that may have been accidental or malicious.
How to manually install and uninstall ApexSQL Log 2014 server side-components (4214913)
Summary ... This article explains how to manually install and uninstall the server side components when it is not possible to utilize ApexSQL Log installer or when server side components need to be (un)installed on the passive cluster node.
Top ApexSQL Log issues and resolutions – an index to often used TS articles (4304655)
ApexSQL Log can become slow or non-responsive when loading data from large data sources into the main grid. ... This happens if there isn’t sufficient memory to show a large number of transactions in the grid.
ApexSQL Log shows the “Unknown recovery model” message and cannot connect to the database (4211428)
Summary This article explains what to do when ApexSQL Log cannot connect to the database and reports that the database recovery model is unknown. ... Symptoms After selecting a database to connect to in the Database connection dialog, ApexSQL Log shows the “Unknown recovery model” message instead of “Full”, “Simple”, or “Pseudo full”.
Indexes rebuild operations are not properly replicated (4213626)
Create phantom insert statement in transaction log auditing results and apply them to replica ... Report job failure when tables with no primary keys are affected ... Summary: ... When ApexSQL Log is used for transactional replication of a SQL Server database to another “Subscriber” database, 1:1 Replication cannot be achieved and “phantom” insert statements are shown and replicated to a Subscriber database which can make imperfect replication of a transaction log database.
What should I do when I encounter a problem in ApexSQL Log? (4214944)
Symptoms ... ApexSQL Log may encounter an error when processing and analyzing the data sources for various reasons. ... If there isn’t a suggested solution after consulting the Troubleshooting section on the web site, please consider sending the application log files for analysis.
ApexSQL Log and ApexSQL Log API show no transactions on Windows 8.1 or Windows Server 2012 R2 (4214947)
ApexSQL Log API 2011.03.1062 and earlier ... Summary ... This article describes how to resolve the problem when ApexSQL Log and ApexSQL Log API show no transactions when running on Windows 8.1 or Windows Server 2012 R2
ApexSQL Log doesn’t recover non-index column updates in a clustered table (4216268)
Summary ... When reconstructing updates using ApexSQL Log in a table with a clustered index on multiple columns, update reconstruction fails for the non-index columns. ... Symptoms ... The error is encountered in a specific situation.
I restored a database backup and get no results in ApexSQL Log (4211462)
Symptoms ... The original database is in full recovery mode. ... The restored database is restored from a database backup and there are no results in the Main Grid ... Cause ... The cause for this problem is that the restored database has its own online transaction log, and it doesn’t hold information on the transactions that have occurred prior to restoring it.
An "Insufficient credentials" error is displayed when attempting to install the server-side components (4216269)
This article explains what to do when the "Insufficient credentials" error is displayed ... An error is displayed during the installation of the server-side components ... Insufficient user permissions to install the server-side components
How to determine whether ApexSQL Log CLI has stopped working (4216290)
The application running is undetermined. ... There are no new output lines in the console ... Analyzing huge transaction logs can cause ApexSQL Log to become non-responsive ... To check if the ApexSQL Log is still running, do the following:
Performance problems in ApexSQL Log – the main grid is unresponsive (4214931)
Cause ... Reading large data sources – online transaction logs, transaction log backups and detached transaction logs, and showing a large number of transactions in the ApexSQL Log GUI requires a lot of free system memory, causing the GUI to become slow or unresponsive when OS manages available system memory
What should I do if ApexSQL Log returns fewer transactions than I expected? (4213633)
ApexSQL Log displays fewer transactions in the main grid, or scripts fewer transactions in the output script than expected ... Background ... This is caused by insufficient information in the data sources (online transaction logs, detached transaction logs, and transaction log backups) or wrong filter options used
The ALM files are bulking up and using too much space (4216334)
Applies to ApexSQL Log Summary This article explains what to do when ApexSQL Log temporary files (.ALM type files) take too much space or when the number of .ALM files is too great Symptoms The following folder size grows too large %AppData%\Local\ApexSQL\ApexSQLLog2014\LOG\ Cause The ApexSQL Log creates two types of temporary files that are used during the auditing process: ApexSQL Log log-files and Metadata files.
ApexSQL Log CLI support (4216172)
This article explains how to use ApexSQL Log command line interface (CLI) and create output files. ... To start the ApexSQL application GUI via the command line interface enter the product name. ... For example apexsqllog.exe
How to improve ApexSQL Log performance over a network? (4214874)
Description ... If the transaction log audited by ApexSQL Log is located on a remote server, it’s possible to experience a noticeable increase in the time needed to retrieve the database log information.
ApexSQL Log – Permissions and requirements (4214848)
Summary This article provides information about required permissions and software requirements for ApexSQL Log. ... Description ... Required permissions for application installation ... The Windows user account used to install ApexSQL Log must have Windows administrator permissions.
Using ApexSQL Log when local installation and remote installation of server-side components isn’t possible (4304025)
Summary This article explains how to use ApexSQL Log even when installation of ApexSQL Log and/or server-side components is not possible/allowed on the server machine due to performance, security, or any other reasons.
SQL transaction details in ApexSQL Log (4211701)
Summary This article explains where and how to find specific information about SQL transactions in ApexSQL Log. ... There are several methods in ApexSQL Log for providing information about transactions from SQL Server database transaction logs.
ApexSQL Log – tips 'n tricks (4211294)
Applies to ApexSQL Log Summary This article offers ApexSQL Log tips and tricks that will help users to increase the productivity and enhance overall experience when working with ApexSQL Log. ... Tip #1 When evaluating ApexSQL Log, it is recommended to use databases that will demonstrate the main ApexSQL Log features: undo script creation, redo script creation, auditing results to a grid, exporting results to various formats by utilizing all available SQL server features etc.
A script for creating a great test database to evaluate the full functionality of ApexSQL Log (4214866)
This article describes the ApexSQLLogDEMO script created specifically for the purpose of a full and comprehensive evaluation that will showcase the full range of ApexSQL Log’s features Description
What information do I need to send to get help with a SQL recovery? (4213608)
The following information can facilitate a successful support/recovery outcome: ... Brief description on what you are trying to recover from. ... Do you have a full database backup available? ... Has the online transaction log file been truncated after/before the disaster has occurred?
Top ApexSQL Log FAQs with detailed answers (4218225)
No. ApexSQL Log relies on SQL Server transaction logs: the online transaction log, native or natively compressed transaction log backups, and detached transaction log files. ... A transaction log is an integral part of a SQL Server database.
How to save and reuse the ApexSQL Log grid data via SQL BULK (4214878)
Summary Since retrieving the SQL transactions in the ApexSQL Log grid might be time-consuming, sometimes it’s better to have the results saved for later analysis. ... There are several ways to save the results.
製品の新しい関連付け
- セルフ・サービス・ツール
- ナレッジベース
- 通知および警告
- 製品別サポート
- ソフトウェアのダウンロード
- 技術文書
- ユーザーフォーラム
- ビデオチュートリアル
- RSSフィード
- お問い合わせ
- Technical Support
- すべて表示