Thank u very much for your reply MBB,

Ya, been assigned to load those 5 million records through e-sql program only.
Now i understood about Transaction logging disabling, since this program is a critical one from business perspective, at any cost risk would not be assumed so i dont think our DBA's would go for transaction logging being disabled, any how i will have a word with them.

Is it possible to stop the querying process? Is there a time during the 24hr period when the table is not used and can be loaded to?

No, MBB there is no chance of stopping the querying process, the querying process is a 24X7 continous run and at any cost it cannot be stopped and this is a fresh load for the very first time and consecutive days we have only minimal load of records and that is not a problem. Everything is concerned with the initial load only.

Ya great, in e-sql program that i had build already everything is going as a prepared statement only and not as a direct statement, thanks for that.

I had tried only with select cursors, hold cursors, update cursors
but can u explain about the insert cursors

this is how i do an insert preparing the statements
sprintf(dbstmt, "insert into <table> values (""....."")");

EXEC SQL prepare insStmt from :dbstmt;

EXEC SQL execute insStmt using :var1, :var2;
this is how i do usually do an insert programmatically,

but i donot know about cursor insert,
this program gets the input from ascii file, performs no of validations and insert into database,
does cursor insert mean sending bulk of insert together, but i am afraid that how would that affect at database level

i believe every insert statement would have a row-level locking and then an insert into actual physcial logs.

Can u please explain on the insert-cursors.

Well hopefully I have given you plenty to be getting on with!
Ya, you had given plenty of information, thanks for that again.