fragmentation in a nonlogging database

We are going to use IDS 9.01 for a data warehousing project. The loading of data will be once-a-month. For efficiency purpose and to avoid any long transaction problem we will be turning logging off for the database. All data integrity will be controlled by our application logic. Basically we will be using timestamps to maintain integrity. We are planning to fragment the fact table and I found the following in the Informix Guide to Database design:- "With Dynamic Server, a fragmented table can belong to either a logging database or a nonlogging database. As with nonfragmented tables, if a fragmented table is part of a nonlogging database, a potential for data inconsistencies arises if a failure occurs." Can anyone elaborate what the above means and how serious is the data inconsistency? thanks.

If your database is not logged and the engine crashes midtransaction it will not be able to rollback the partial update. Mainly this results in index entries that point to rows that nolonger exist, secondary keys that point to rows that have been updated to contain a different value from that in the index node entry, etc. You will spend many of your nights rebuilding damaged indexes I can testify. Log the database. Just turn logging off during the the monthly load and turn it back on concurrent with the level zero archive that you will surely want to start immediately after the load completes. Art S. Kagel Trigger fish wrote: > > We are going to use IDS 9.01 for a data warehousing project. The loading of > data > will be once-a-month. For efficiency purpose and to avoid any long > transaction problem > we will be turning logging off for the database. All data integrity will be > controlled > by our application logic. Basically we will be using timestamps to maintain > integrity. > > We are planning to fragment the fact table and I found the following in the > Informix Guide to Database design:- > > "With Dynamic Server, a fragmented table can belong to either a logging > database or a nonlogging database. As with nonfragmented tables, if a > fragmented table is part of a nonlogging database, a potential for data > inconsistencies arises if a failure occurs." > > Can anyone elaborate what the above means and how serious is the data > inconsistency? > > thanks.