• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 307
  • Last Modified:

Dump Transaction does not work

The logspace of my database keep on increasing day by day.
I tried "Dump Transaction dbname with no_log" periodically with a task, but the log space does not seem to be reducing.
I also tried dbcc checktable(syslogs) and Dbcc checkdb(dbname). But still no change in the logspace, it still grows.
Well, The problem was the database had been participating in replication but the publishing was uninstalled and thus replication was removed around 15 days back.  But there were some unreplicated transactions present, this I observed using
DBCC OpenTran(DBname)
I could not bring the logspace down (I tried executing the code which I found in the Q184499. but nothing worked.)
Things started working when I started the replication again and the logspace came down to 0.001596%.
Can anybody tell me what was going on?

Rakesh
0
Rakesh010499
Asked:
Rakesh010499
1 Solution
 
tschill120198Commented:
Two possibilities:
1) Are there any open transactions at the time the transaction is dumped?
2) Does this database participate in replication?
0
 
david_levineCommented:
If you are doing a dump with no_log, why not just set the database to 'truncate log on checkpoint'? That way, after each app commits, it will truncate the log for you.

Unless I'm misunderstanding what you really want to do.

David
0
 
Rakesh010499Author Commented:
Edited text of question
0
What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

 
Rakesh010499Author Commented:
Edited text of question
0
 
StefaanCommented:
Why not create a daily routine for that.  As far as I know, you should backup your database.  Backing up your database will commit all transactions to the database and free the the transaction log.

When making changes to the database, the changes arn't processed immediately but create an entry in the transaction log.  By running the maintenace wizard, you can set up a maintenance plan.  I did it that way and created a daily maintenance plan which backs up my database, thus committing all transactions everyday.  The result is that each day I have an (almost) empty transaction log.

Try it out, you'll see that it works.


0
 
Rakesh010499Author Commented:
Stefaan,
Thanks for your answer. Since the database was involved in replication,with a separate machine which is solely dedicated for replcation, I think there was no neccessity to take a backup of the datbase. also, when the database is participating in replication the transaction log of that database will not be cleared unless and until all the transaction are read by the logreader task.
I will try your suggestion and let you know ASAP.
Thanks
Rakesh  
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now