ASE 15.5 can we get bigdatetime in system table sysaudits_xx

[former_member89972]

Greetings all

In ASE 15.5 : is there a way to convert the datetime column "eventtime" into bigdatetime in sysaudits_xx tables ?

bigdatetime data type was introduced in ASE 15.5.   It needs the same 8-byte storage as a datetime data type.

System tables with datetime column are mostly using the normal date time with 1 to 3 ms accuracy.

I am doing login/logout connection monitoring with SAP/Sybase auditing.

And it will help to know connections pressure as precisely as possible.

Avinash

As note/feedback for SAP/Sybase documentation/manuals

In the reference manual for system tables,  systypes still does NOT show bigdatetime

SAP Adaptive Server Enterprise 16.0 > Reference Manual: Tables 16.0 > System Tables

[former_member89972 · Accepted solution]

Thanks Jeroen and Bret for your respective inputs.

I will close this thread as answered though  I do not see a near term solution.

Thanks again

Avinash

[jayrijnbergen]

Changing system tables is not a good idea, that's asking for trouble.

If 3ms accuracy is not good enough because of the amount of logins, then I guess auditing will be pretty overloaded and a huge bottleneck for just logging the login/logout activity

And just changing the datatype in the audit tables is probably not sufficient anyway, because the auditing system is most likely inserting the eventtime as datetime. The insert will go fine, but you just get an implicit converted value from datetime to bigdatetime

[former_member89972]

Fiddling with system tables is typically a last resort. 

I do NOT do that unless it is unavoidable for some solid reason.

I wanted to find if was possible at all in the at 15.5 in some way.

But even in ASE 16 that does not seem to be possible.

Not sure if SAP/Sybase folks are planing to introduce bigdatetime in

- any system tables at all

- audit tables in particular

Avinash

[former_member188958]

This would only be possible in a future version. 

In general we are reluctant to make such changes without a strong need for it as it breaks backward-compatibility (i.e. existing applications that expect the column to be a datetime may break if the column is changed to be a bigdatetime).  So this sort of change is only likely to be made as part of a major version upgrade.

-bret