|
We are facing the following problem. Our sybase database log file gets exponentially big because of isolation level logging on every call to query a tables via JPA. Is there any switch available in Sybase which can be used as a part of connection parameters to suppress logging of isolation level. |
Please be aware that the content in SAP SQL Anywhere Forum will be migrated to the SAP Community in June and this forum will be retired.
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Question tags:
question asked: 25 Jan '13, 11:46
question was seen: 1,570 times
last updated: 28 Jan '13, 17:32
What version and build of SQL Anywhere are you using?
What exactly do you mean by "isolation level logging"? I've never seen that term before, and there are zero Google hits (well, one hit, your question).
Do you mean "request level logging" ?
If it is auditing you want to disable for a connection, have a look at the docs: http://dcx.sybase.com/index.html#1201/en/dbadmin/dboptions-s-4586690.html
I also think you should provide more details about your 'query through JPA' - is that 'Java Persistence API'? Are you using Hibernate or a similar framework?
Where are you currently seeing the logging of an 'isolation level' in your application?
...at least these comments all count as "high-level guessing":)
Five different people respond, are met with silence... that merits at least one down vote IMO.