Hi
In one of my databases I FORCE LOGGING at the database level. The logic being is that the database is not super busy and we can handle the subsequent archive logs.
However, I want to disable logging for on particular table. This has become troublesome given that there are millions of transactions written / delete from this table on a daily basis. I was informed that the table data would never be required for recovery either (I am trying to get the developer to change the way the process works ).
So, if I have FORCE LOGGING at database ALL tablesapces are logged, over riding what we have at a tablespace level
If I have it at a tablespace level, then ALL objects in that tablespace are logged, over riding what we have at an object level
- Above just for clairty.
What I plan to do is
1. disable force logging at the database level
2. enable logging at the table space level
3. create the offending table in its very own tablespace and disable logging at this tablespace level.
That would allow me to have ALL obhjects, other than my offending object, to continue to have LOGGING enabled.
Can someone please veryfy that this is correct please?
Thanks