![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I'm sorry but previously command ALTER TABLE tbl ACTIVATE NOT LOGGED INITIALLY on table created without NOT LOGGED INITIALLY option was impossible. Or not? IMHO, more better give error or warning on this statement for table created wihtout NOT LOGGED INITIALLY. You are correct that this used to be teh case. |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
I'm customer too and don't ignore any warnings :-) But I was very surprised when a some numbers of table was in inconsistence state after restore from online backup. And it was very important tables. Yes, it was a bug in my script - I made mistake in schema name. But no way to detect this sutiation. For example, I can detect tables with not logged property and can use this attribute to avoid sutiation with lost table/data after restore from online backup. Currently this property is not useful :-(. Another question - how detect inconsistence tables after restore? |
#5
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |