on 2014 Jun 18 9:50 AM
Hi All, |
I did some readings on IQ auditing , I followed below steps :
1. | SET OPTION PUBLIC.AUDITING = 'ON' |
2. | sa_enable_auditing_type('DDL') |
3. | dbtran -g mydb.log mydb.sql |
I am able to view the Audit details in mydb.sql But all the time I need to run the step 3 , is this a right approach for Sybase IQ auding , Or is there any log file when I can get details like we have for HANA .
Thanks,
Razal
The transaction log is the only location of the official audit information. Here's a snippet from the manuals on this (http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.sqlanywhere.12.0.1/dbadmin/auditi...😞
The transaction log stores all executed data definition statements, and the user ID that executed them. It also stores all updates, deletes, and inserts and which user executed those statements. However, this is insufficient for some auditing purposes. By default, the transaction log does not contain the time of the event, just the order in which events occurred. It also contains neither failed events, nor select statements.
Auditing is a way of keeping track of the activity performed on a database. When you use auditing, additional data is saved in the transaction log, including:
You cannot stop using a transaction log while auditing is enabled for a database. If you want to turn off the transaction log, you must first turn off auditing.
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, unfortunately, to see the audit trail it requires using the dbtran utility. The same information is also available via the SCC GUI.
You will also want to add the -d option to your dbtran command line. This orders the dbtran output by date.
"Specifies that transactions are written in order from earliest to latest. This feature is intended for auditing database activity: do not apply dbtran output against a database."
From a log file management perspective there isn't much to do. The log files generally stay small. What you will want to do, however, is make frequent passes at the tran log with dbtran so that you can extract and safeguard the audit information. This is typically hourly or daily. The frequency is up to you, however.
Once you have done that, you can then prune the transaction log with the dbbackup utility, per the docs. This is typically something that is done weekly or monthly depending on the size and growth rate. I prefer to keep the tran log rather small at just a few hundred MB.
Mark
Hi Mark,
Thanks a lot for your help and support here
But does backup transaction log really helps for Point in time recovery like an incremental backup if we keep it for longer time .
- I think i will schedule daily Audit log extraction.
- Daily dbbackup for log (to make sure that we free up resources)
- we already scheduled daily full data backup and incremental backup every 20 minutes , Because unlike other IQ used for bulk load in our case it is uniform loading of data is happening .
- So this backup of transnational log backup may not be really used by us.
Correct if you have any suggestion .
Also waiting for testing Point in time recovery from SP08
Thanks,
Razal
Hi Mark,
IQ and HANA are coming closer and closer.
Is there anything planned like integrated audit logging of HANA and IQ while using HANA Extended Storage / Smart Data Access?
The described procedure above, extracting and safeguarding the audit information, pruning the transaction log, etc. isn't there any functionality running out of the box? Where do I need to file such a feature request to get audit logs we get it in HANA?
Besides all this, are the proposals for audit policies - do's and don't's?
Regards,
Jens
User | Count |
---|---|
71 | |
11 | |
10 | |
10 | |
10 | |
8 | |
7 | |
7 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.