Restoring a SQL Server 2005 database without the log - revisited

[KeithWalton]

I know this has been discussed before, but my database is getting huge. Every night I restore backups of my databases to a report server. I don't need the logs, so after restore I detach the database and delete the logs. When I reattach, SQL Server creates new log files that are tiny. If I can do this, why do I need the log files in the first place? As it is, I have to stagger my database restores because I don't have room for the 400 GB of log files.

I know that if I backup my database with the no_log option, I will have to provide a log file for it to restore. This allows for online backups where the database is updated during the backup process. I don't do any updates to my database during the backup. Is there any way to flag the backup file as not needing a log file? There should be no uncommitted transactions in the backup. Would taking my database offline during the backup help?

Thanks

[ck9663]

You'd rather have and not need it, then not having it and you really really need it.

-- CK

[KeithWalton]

After restoring the database on the report server, I set it to be read-only. How could I need the log file?

You'd rather have and not need it, then not having it and you really really need it.

-- CK