Category
Product Version
Topic
Subtopic
Checklist for suspicious activity on SQL Server (4282447)
It seems something went awry with the SQL Server. ... It’s sluggish, behaves erratically, produces heavy network traffic, there is a significant increase in the server processor or memory utilization, and to top it all there are reports of or database objects and data being damaged or missing.
SQL Server true detective - Solving the case of the broken database (4282414)
In this series of articles, we’ll present various solutions for solving this “crime” by detecting the DDL change that broke a SQL Server database and even fixing the broken SQL Server database. ... The goal is to detect a bad change as quickly as possible (since there will be a lot of other changes) and to find a way to fix it.
How to automate adding SQL auditing triggers to a new, or changed database (4308647)
How to automate adding SQL auditing triggers to a new, or changed database "<p> Maintaining a before-and-after audit trail for sensitive tables can be time consuming, especially with a database that is under continuous development, and particularly in teams that use continuous integration.
How to activate ApexSQL software manually (4216052)
To activate an ApexSQL product online, a Hardware ID and a product activation key are needed. ... To manually activate an ApexSQL product online: ... Navigate to ‘ Product activation’ web page ... Select the ApexSQL product to be activated from the ‘Product’ pick list and the appropriate product version from the ‘Version’ pick list
Get an alert when a certain record changes in SQL Server (4307198)
Get an alert when a certain record changes in SQL Server "<p>Auditing a database is the first step towards staying updated about database changes. ... However, if specific, highly sensitive data needs reviewing, an immediate notification of any change is preferable.</p> <p>Sending email alerts to one or more recipients is one of the most common ways of immediate notification.
SQL Server database auditing techniques (4261616)
SQL Server database auditing is not used only to address auditing requirements for compliance. ... It has become necessary for the analysis of database actions, troubleshooting problems, investigating the suspicious and malicious activity.
Continuous auditing of SQL Server database using the transaction log (4287874)
Continuous auditing of SQL Server database using the transaction log "<h2>Challenge</h2> <p> Imagine if you could decrypt and pump all the wealth of transactional information and details contained in the SQL Server transaction log, in human readable format, and then store this as data directly in SQL Server tables, ensuring it wasn’t lost when the log was truncated, and such that data could be queried, reported on etc. using T-SQL.
Continuous SQL Server database auditing and reporting using the transaction log (4287743)
Continuous SQL Server database auditing and reporting using the transaction log "<p> SQL Server database transaction log files are continuously pumped with the transactional information and details on database changes by the SQL Server itself.
Load testing: Recording production transactions and replaying on a test server (4270430)
Load testing: Recording production transactions and replaying on a test server "<p> Load testing not always the same as stress testing. ... Stress testing seeks to maximize the load on a server to see when and where it breaks.
Auditing triggers in SQL Server databases (4239095)
One of the essential SQL Server security topics is finding out who did something, what and when. ... Being able to provide a history of data for various auditing purposes, some of which are enforced by US laws through compliance regulations, is a serious task for any DBA.
How to automate trigger-based SQL Server auditing (4284690)
How to automate trigger-based SQL Server auditing "<p> More often than not, a top level requirement for all SQL Server DBAs is to have mechanisms to capture who changed what and when and to have stored audit information available for further investigation.
How to version and audit schemas and rollback changes with schema snapshots (4316477)
This involves tracking changes over time, identifying differences between two versions and even rolling back changes to a previous baseline. ... </p> ... <p> ... Various native tools exist to version a database for purposes of auditing from simply taking periodic backups to examine SQL profiler results for schema change operations.
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.
Licensing and activation of centralized system products (4318747)
This article describes what you need to know about the licensing and activation of centralized ApexSQL products. ... Definitions ... Central instance – this is a computer where the main application and SQL Server instance that hosts the central repository database is installed.
Unable to install server-side components on the remote machine (4216265)
When adding the remote SQL Server instance in the server auditing list and process failes due to the required server-side components are not installed on the target machine (Windows service which allows auditing of SQL Server instances remotely via the ApexSQL Audit main application), and ultimately leading to the error:
ApexSQL Audit installation fails and changes are rolled back silently without any warning or dialog (4211508)
Applies to ApexSQL Audit Symptoms The ApexSQL Audit installation runs normally until the required SQL Server and credentials information are entered and after that installation fails and the changes are rolled back.
Some ApexSQL Audit Web Reports requirements are not detected (4211482)
The ApexSQL Audit installation cannot be completed successfully due to missing prerequisites. ... Symptoms ... During the ApexSQL Audit installation, the following dialog is shown indicating that some of the necessary prerequisites have not been installed.
ApexSQL Audit - An error occurred during local report processing (4296660)
This article explains how to resolve the issue when ApexSQL Audit’s Web console shows the following error: ... The definition of the report ” is invalid ... The value of the Width property for the tablix ‘ContentTablix’ is “X,X in”, which is not a valid size.
The “The server cannot handle directory requests” error is encountered during installation (4216318)
ApexSQL Audit installation on a computer that is the part of the Active Directory network, could result in the error: “The server cannot handle directory requests” after inserting the required credentials and installation will stop
Cannot configure auditing for SQL Servers with caps sensitive collation (4214896)
Applies to ApexSQL Audit Symptoms Auditing options cannot be configured for SQL Server with caps sensitive collation. ... Cause Due to a bug in ApexSQL Audit R1 and earlier, configuring a SQL Instance with case sensitive collation is not be possible in some cases.
ApexSQL Audit central repository database is becoming too large (4211502)
Applies to ApexSQL Audit Summary This article explains what to do when the ApexSQL Audit central repository database, where ApexSQL Audit stores all audit information, grows too quickly. ... Full database backups are becoming bigger every day.
ApexSQL Audit reports don’t show everything I’m expecting (4211403)
This article explains how to resolve the problem when the reports in ApexSQL Audit show no records for a specific event type or a specific SQL database object; what to check and how to fix it. ... Symptoms
Audited events in ApexSQL Audit (4216094)
The events audited by ApexSQL Audit are divided into 7 groups, by operation type. ... Schema changes, such as object renaming, using the sp_rename SQL stored procedure ... An event that requires attention has occurred.
ApexSQL Audit web reports show no records (4214895)
This article explains how to resolve the problem if ApexSQL Audit’s Web console shows no audited information, due to nothing being captured; what to check and how to fix any individual cause. ... Symptoms
Reports doesn’t display any data collected by ApexSQL Audit 2014 R1 version after updating to a newer version (4216286)
Reason Due to significant change of the application and repository database architecture, the ApexSQL Audit R1 repository database is no longer compatible and report will be archived when updating to a newer version Affected versions: ApexSQL Audit 2014 R2 and newer after upgrade from the R1 version Resolution
New Product Association
- Self Service Tools
- Knowledge Base
- Notifications & Alerts
- Product Support
- Software Downloads
- Technical Documentation
- User Forums
- Video Tutorials
- RSS Feed
- Contact Us
- Technical Support
- View All