Category
Versión del producto
Tema
Subtema
Idioma
Técnicas de auditoría de bases de datos SQL Server (4298975)
La auditoría de bases de datos SQL Server no es usada solamente para cumplir con requerimientos de conformidad. ... Se ha vuelto necesaria para el análisis de acciones de bases de datos, soluciones de problemas y la investigación de actividades sospechosas y maliciosas.
Antes y después de auditar en SQL Server (4298495)
Simplemente archivar información para auditar una base de datos es una cosa, pero reconstruir un historial de auditoría exitosamente para proveer datos forenses significativos es otra. ... Es importante poder ver un historial completo de los cambios del usuario, así como poder revertir los cambios que pueden haber sido accidentales o maliciosos.
Auditar cambios del esquema de una base de datos SQL Server (4298286)
Realizar un seguimiento de los cambios hechos a los objetos de su base de datos es una parte clave de una estrategia de seguridad de bases de datos SQL o una política de cumplimiento de normas, incluyendo, entre otras, Health Insurance Portability and Accountability Act, Sarbanes-Oxley, Payment Card Industry Data Security Standard o European Union Data Protection Directive.
Cómo asegurar una auditoría continua de SQL Server con cero pérdidas de datos (4213560)
Cómo asegurar una auditoría continua de SQL Server con cero pérdidas de datos <p>Un enfoque de auditoría continua de SQL Server debe incluir:</p> ... es una <a href="https://www.apexsql.com/sql_tools_audit.aspx" target="_blank">herramienta de auditoría y cumplimiento de normas para SQL Server, </a> la cual audita más de 200 eventos SQL Server y almacena los datos recolectados en una base de datos repositorio central a prueba de modificaciones.
Auditoría y reportes de bases de datos SQL Server continuos usando el registro de transacciones (4214861)
Los archivos de registros de transacciones de la base de datos en SQL Server son continuamente inyectados con información transaccional y detalles acerca de los cambios de la base de datos por SQL Server mismo.
Auditando sentencias SELECT en SQL Server (4210523)
Aunque las sentencias SELECT no son destructivas por naturaleza ni tampoco pueden cambiar datos o esquemas, hay muchos cases que requieren su auditoría en SQL Server. ... Las sentencias SELECT ejecutadas pueden indicar varios problemas actuales o potenciales, y esta es la razón por la cual es importante saber quién vio qué y cuándo.
What authentication method does ApexSQL use? (4377107)
When including ApexSQL tools on you environment, it is important to understand the authentication types available. ... <p><img alt="1" src="https://prod-support-images-cfm.s3.amazonaws.com/KB_kA0RP0000002TcD0AU_authenticationapexsql.png"></img></p>
ApexSQL Audit Does Not Support CIFS (Network Share Path) for Archiving Repositories (4378620)
The archiving repositories must maintain a constant connection with the central server instance, requiring them to be located on the same machine as the central server. ... ApexSQL Audit is designed to ensure secure and reliable archiving of audit data.
How to safely move the auditing SQL Server database to a different instance in ApexSQL Audit? (4378607)
How to safely move the auditing SQL Server database to a different instance in ApexSQL Audit? ... Moving an SQL database to a different instance involves several steps. ... Here’s a general guide to help you through the process:
How to determine which monitored SQL Server database is causing the biggest amount of logs in my ApexSQL Audit CRD? (4378521)
How to determine which monitored SQL Server database is causing the biggest amount of logs in my ApexSQL Audit CRD? ... Several new ApexSQL Audit CRDs have been created recently, as each repo was 20GB already
'Auditing filter change monitor' alert information is not displayed in full due to character limitation for the [UserSummary] column in [ApexSQL].[AlertReports] table (4378480)
ApexSQL Audit has a character limitation of 32 000 characters for the text in the UserSummary column from the ApexSQL.AlertReports table. ... When the limit is reached, the text is cut off and ellipsis (...) is placed at the end of the entry both in the UI ( Summary pane of the alert in Alert History) and the UserSummary column in ApexSQL.AlertReports tables (and views).
MaxDegreeOfParallelism error in ApexSQL Audit Logs (4374729)
When adding a server in ApexSQL Audit, after some minutes, the server auditing stops automatically without apparent errors. ... One or more errors occurred. ... Type: System.AggregateException ... Stack trace
ApexSQL Audit - Received Packages building up (4378237)
Events reaching the ApexSQL Audit central repository, thus reports show that there is recent information being captured correctly. ... There is a bug in ApexSQL Audit's mechanism for loading and deleting the packages in this scenario.
Does ApexSQL Audit have the capability to generate reports that monitor and log, when tables are added to, or removed from Before-After configurations? (4378116)
Does the functionality exist in ApexSQL Audit, to create reports that provide visibility into changes made to Before-After configurations? ... Specifically tracking when tables are added or removed?
ApexSQL Audit Server Migration Best Practices (4377701)
This will cause many issue since the database includes embeded encrypted data related to the original server that cannot be changed. ... Creating a new central database on the new server without importing the previous configuration.
Numerous #temp table updates appear in the reports, which haven’t been knowingly created. How can they be excluded? (4377797)
Numerous #temp table updates appear in the reports, which haven’t been knowingly created. ... How can they be excluded? ... If there is a consistent naming convention, a.k.a #temp in this case, please use advanced filters option to exclude it from reports.
The message "Connection to the central instance failed" appears when opening the ApexSQL Audit GUI. (4377497)
When opening ApexSQL Audit the “Connection to the central instance failed” message will appear. ... There can be various reasons why this message appears: ... - The connection between Central and the Domain controller is interrupted
"Error encountered and application needs to be closed" message is encountered when old archives are deleted (4377119)
When trying to delete an accumulated number of archives in the ApexSQL Audit GUI the "Error encountered and application needs to be closed" message is encountered and application crashes WORKAROUND<br>None<br><br>BUG ID<br>234987<br><br>STATUS<br>Waiting for fix in future release of ApexSQL Audit 234987
SQL Parser throws a syntax error for a T-SQL query that contains 'ENSP' HTML space notation (4377058)
The SQL Parser throws a syntax error for any T-SQL query containing the 'ENSP' HTML space notation, resulting in the file being sent to the quarantine folder. ... where(21,1)<br>2024-09-19 14:36:51.852 ERROR [SERVER_NAME\SQL19]: An exception occurred<br>Cannot parse SQL text data<br>Type: ApexSQL.Audit.Processor.Distributed.Trace.TraceException<br>Stack trace<br> at ApexSQL.Audit.Processor.Distributed.Parser.SqlParserHelper.GetParsedObject(String sql, Boolean parseColumns)<br> WORKAROUND:<br>Use SQL Audit technology for auditing instead of Extend events technology or exclude the application/login (ENSP) from the auditing process<br> <br>STATUS:<br>The
ApexSQL Audit main features overview (4216141)
In this article, we are going to quickly look into three main ApexSQL Audit features: ... In order to ensure data safety, easy reporting and being timely and properly alerted on critical events, ApexSQL Audit includes following main features:
"Connecting to central repository. Please wait..." message is showing indefinitely when ApexSQL Audit GUI is launched (4369856)
3) Wait for a half a minute, then launch the ApexSQL Audit again and the connection to the central repository should now be established
ApexSQL Audit performance optimization (4369125)
To ensure ApexSQL Audit Central performance there are some best practices that should be followed. ... Failure to follow these best practices may result in underperformance. ... Ensure that Repository integrity checks not occur during peak hours.
"RESTORE VERIFYONLY" and "RESTORE LABELONLY" are captured as DDL operations (CREATE DATABASE) when using SQL Audit and Extended event data collection (4369285)
RESTORE statements are collected for auditing even when Backup/Restore filter is not selected<br> Expected result: The mentioned RESTORE statements should not be collected for auditing if the Backup/Restore filter is not selected.<br><br>WORKAROUND:<br><br>1.
ApexSQL Audit performance usage - Testing case using Extended Events auditing technology (4369129)
ApexSQL Audit performance usage when using Extended Events auditing technology DISCLAIMER: The following sample represents an insight of resource utilization during overload cases, insinuated with a huge auditing data processing using ApexSQL Audit.
How to activate ApexSQL Audit? (4369441)
ApexSQL Audit is a DBA tool and is licensed per SQL Server instance.<br>This means that each instance requires a license. ... If there are 3 instances, 3 licenses are needed.<br>It's irrelevant whether these 3 instances are on a single physical machine or on three machines.<br>The number of licenses also doesn't depend on virtualization or the number of users.
Asociación de nuevos productos
- Herramientas de autoservicio
- Base de conocimientos
- Notificaciones y alertas
- Soporte de productos
- Descargas de software
- Documentación técnica
- Foros de usuarios
- Tutoriales en video
- Aviso de actualizaciones de páginas web (RSS)
- Comuníquese con nosotros
- Soporte Técnico
- Ver todos