log file on subscriber db growing fast

replication between to sql 2005 servers the publication type is snapshot and
the
subscriber type is transactional
I have a problem with fast growing log files on the subscription database
the data in the db is 48mb but the log file is 60 gb
this is becomming a problem i urgently need to know how to purge the log files
If you don't need to back the logs up and just want them to stay small, then
change the recovery mode to simple. Once the data has been purged, you'll
need to shrink the size of the log file to recover the extra space. If the
simple recovery mode doesn't cause the occupied space to fall, have a look
for an open transaction (dbcc opentran) and kill the relevant SPID if
necessary.
HTH,
Paul Ibison
|||Paul thank you very much it did the job
"Paul Ibison" wrote:

> If you don't need to back the logs up and just want them to stay small, then
> change the recovery mode to simple. Once the data has been purged, you'll
> need to shrink the size of the log file to recover the extra space. If the
> simple recovery mode doesn't cause the occupied space to fall, have a look
> for an open transaction (dbcc opentran) and kill the relevant SPID if
> necessary.
> HTH,
> Paul Ibison
|||thanx Paul,
it worked perfectly
"Paul Ibison" wrote:

> If you don't need to back the logs up and just want them to stay small, then
> change the recovery mode to simple. Once the data has been purged, you'll
> need to shrink the size of the log file to recover the extra space. If the
> simple recovery mode doesn't cause the occupied space to fall, have a look
> for an open transaction (dbcc opentran) and kill the relevant SPID if
> necessary.
> HTH,
> Paul Ibison
|||Paul thank you very much it did the job
"Paul Ibison" wrote:

> If you don't need to back the logs up and just want them to stay small, then
> change the recovery mode to simple. Once the data has been purged, you'll
> need to shrink the size of the log file to recover the extra space. If the
> simple recovery mode doesn't cause the occupied space to fall, have a look
> for an open transaction (dbcc opentran) and kill the relevant SPID if
> necessary.
> HTH,
> Paul Ibison
|||thanx Paul,
it worked perfectly
"Paul Ibison" wrote:

> If you don't need to back the logs up and just want them to stay small, then
> change the recovery mode to simple. Once the data has been purged, you'll
> need to shrink the size of the log file to recover the extra space. If the
> simple recovery mode doesn't cause the occupied space to fall, have a look
> for an open transaction (dbcc opentran) and kill the relevant SPID if
> necessary.
> HTH,
> Paul Ibison
|||thanx Paul it worked fine
if you she this message three times it is because the ms server cannot be
found everytime i post my response
"Paul Ibison" wrote:

> If you don't need to back the logs up and just want them to stay small, then
> change the recovery mode to simple. Once the data has been purged, you'll
> need to shrink the size of the log file to recover the extra space. If the
> simple recovery mode doesn't cause the occupied space to fall, have a look
> for an open transaction (dbcc opentran) and kill the relevant SPID if
> necessary.
> HTH,
> Paul Ibison