Solved

Dump Transaction does not work

Posted on 1999-01-05
6
261 Views
Last Modified: 2011-04-14
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
Comment
Question by:Rakesh010499
6 Comments
 
LVL 2

Expert Comment

by:tschill120198
ID: 1092490
Two possibilities:
1) Are there any open transactions at the time the transaction is dumped?
2) Does this database participate in replication?
0
 
LVL 9

Expert Comment

by:david_levine
ID: 1092491
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
 

Author Comment

by:Rakesh010499
ID: 1092492
Edited text of question
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 

Author Comment

by:Rakesh010499
ID: 1092493
Edited text of question
0
 
LVL 3

Accepted Solution

by:
Stefaan earned 0 total points
ID: 1092494
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
 

Author Comment

by:Rakesh010499
ID: 1092495
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

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Nowadays, some of developer are too much worried about data. Who is using data, who is updating it etc. etc. Because, data is more costlier in term of money and information. So security of data is focusing concern in days. Lets' understand the Au…
When you hear the word proxy, you may become apprehensive. This article will help you to understand Proxy and when it is useful. Let's talk Proxy for SQL Server. (Not in terms of Internet access.) Typically, you'll run into this type of problem w…
Via a live example, show how to backup a database, simulate a failure backup the tail of the database transaction log and perform the restore.
Viewers will learn how to use the INSERT statement to insert data into their tables. It will also introduce the NULL statement, to show them what happens when no value is giving for any given column.

867 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now