Database Log File

Hello there
i have a huge problem here our database .mdb file is 240 m.b
the log file is 20 g.b
so is there a missing configuration or a database problem
or what should i do to reduce the log file
Amir FahmyHi Amir
Most likely you have the db set up with FULL recover mode and you do not
perform backup log file. Set the db with SIMPLE recovery mode and then
shrink the log.
"Amir Fahmy" <AmirFahmy@.discussions.microsoft.com> wrote in message
news:43248209-E33C-489A-AC88-D98EF4AABD84@.microsoft.com...
> Hello there
> i have a huge problem here our database .mdb file is 240 m.b
> the log file is 20 g.b
> so is there a missing configuration or a database problem
> or what should i do to reduce the log file
> Amir Fahmy|||"Amir Fahmy" <AmirFahmy@.discussions.microsoft.com> wrote in message
news:43248209-E33C-489A-AC88-D98EF4AABD84@.microsoft.com...
> Hello there
> i have a huge problem here our database .mdb file is 240 m.b
> the log file is 20 g.b
> so is there a missing configuration or a database problem
> or what should i do to reduce the log file
> Amir Fahmy
When did you last backup the log? What recovery model are you using?
If you don't understand log backup and recovery then lookup those topics in
Books Online.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eIisJLvwHHA.4568@.TK2MSFTNGP03.phx.gbl...
> Hi Amir
> Most likely you have the db set up with FULL recover mode and you do not
> perform backup log file. Set the db with SIMPLE recovery mode and then
> shrink the log.
>
Hi Uri,
What you have said is of course the most likely explanation. However, Amir
should not attempt what you have suggested unless he understands the meaning
of different recovery models, log backups and the impact on his ability to
recover from a disaster. If he did understand those things then I suspect he
wouldn't need to ask the question. So that's why I replied as I did rather
than give a direct answer that won't necessarily be appropriate for every
eventuality.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||Hi David
I agree with you. I did give the answer as for solving the problem
immediatly as disk could run out of space. Then I should mention that he
needs to undestand those thing as you said.
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:%23q1SVQvwHHA.484@.TK2MSFTNGP06.phx.gbl...
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:eIisJLvwHHA.4568@.TK2MSFTNGP03.phx.gbl...
>> Hi Amir
>> Most likely you have the db set up with FULL recover mode and you do not
>> perform backup log file. Set the db with SIMPLE recovery mode and then
>> shrink the log.
> Hi Uri,
> What you have said is of course the most likely explanation. However, Amir
> should not attempt what you have suggested unless he understands the
> meaning of different recovery models, log backups and the impact on his
> ability to recover from a disaster. If he did understand those things then
> I suspect he wouldn't need to ask the question. So that's why I replied as
> I did rather than give a direct answer that won't necessarily be
> appropriate for every eventuality.
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>