I have a local database that is refreshed overnight. A DTS batch grab several views from another database and makes local copy locally. This process creates a hige amount of unnecessary lines in the log file and sometimes so much that the entire available disk space is used, thus crashing the DTS batch. This database is mainly static and non transactional. I wonder if its possible to disable alltogether the logging process for that particular db but I know its part of SQL server so it can't be that simple.
If I limit the size of the log file it gets cluttered and the same problem that if disk space was all used occurs... what should I do ???
Simple-recovery model logs each transaction and clears the log at each CHECKPOINT that's why during ur DTS it gets too big. Try the Bulk-Log recovery model, for it just skips BCPs and SELECT INTO etc. During ur DTS the log may fill-up less than the Simple-Recovery Model. Bulk-Log requires Transaction-Log backups to clear older records.