Log file size

What's the easiest way to truncate the log file size? After some test
operations it was increased to 420 mbytes, keeping in mind that I don't need
this log file and the real database size is only 20-30 mbytes it's nonsense.
Should I disable a full recovery mode or what?
Just D.How about just create a job that runs once a w or so that truncates the
log for you?
Have the job execute something like this:
BACKUP LOG [Your_Database_Name] WITH TRUNCATE_ONLY
DBCC SHRINKFILE ([Your_Database_Name]_log,50)
--Jason
"Just D." <no@.spam.please> wrote in message
news:CIC0e.420$k57.401@.fed1read07...
> What's the easiest way to truncate the log file size? After some test
> operations it was increased to 420 mbytes, keeping in mind that I don't
need
> this log file and the real database size is only 20-30 mbytes it's
nonsense.
> Should I disable a full recovery mode or what?
> Just D.
>|||http://msdn.microsoft.com/library/d... />
t_6rqr.asp
Describes the usage of recovery models in your database.
If you choose Simple Recovery, then your backup, restore, and recovery
models should be adjusted to accomodate the data you have.
Pick the recovery model that best enables you to maintain the level of
support and down time in case of emergency.
"Just D." wrote:

> What's the easiest way to truncate the log file size? After some test
> operations it was increased to 420 mbytes, keeping in mind that I don't ne
ed
> this log file and the real database size is only 20-30 mbytes it's nonsens
e.
> Should I disable a full recovery mode or what?
> Just D.
>
>|||Jason,
It's easy to do that, I actually created a scheduled job that works once per
day. But it doesn't help and this built-in shrink doesn't truncate the log
file. That's why I asked about any official method to truncate the log file.
One of the possible ideas was to disable the full database recovery, maybe
it stores all my steps one by one to roll back any time if I need that.
Just D.
"Jason Mauss gmail.com>" <jason.mauss@.<nospam> wrote in message
news:%23XCJFcJMFHA.3320@.TK2MSFTNGP15.phx.gbl...
> How about just create a job that runs once a w or so that truncates the
> log for you?
> Have the job execute something like this:
> BACKUP LOG [Your_Database_Name] WITH TRUNCATE_ONLY
> DBCC SHRINKFILE ([Your_Database_Name]_log,50)
> --Jason
> "Just D." <no@.spam.please> wrote in message
> news:CIC0e.420$k57.401@.fed1read07...
> need
> nonsense.
>|||Yes, the idea was correct - to switch from FULL recovery mode to Simple,
then shrink. I got a 1 mbyte file size only, that's all I wanted.

> "Jason Mauss gmail.com>" <jason.mauss@.<nospam> wrote in message
> news:%23XCJFcJMFHA.3320@.TK2MSFTNGP15.phx.gbl...
>|||Yeah, I was going to suggest going from FULL to SIMPLE for the recovery
model...sounds like you figured it out. I made my suggestion based on what
we do for our CRM database...which needs FULL recovery.
-Jason
"Just D." <no@.spam.please> wrote in message
news:fQG0e.517$k57.110@.fed1read07...
> Yes, the idea was correct - to switch from FULL recovery mode to Simple,
> then shrink. I got a 1 mbyte file size only, that's all I wanted.
>
don't
>