dimanche 29 avril 2012 20:05
The log file of a standalone SQL 2005 database is growing hugely. I use the sql query as below and found the column "log_reuse_wait_desc" = REPLICATION
select name, log_reuse_wait_desc from sys.databases;
To know what is the replication about, in SSMS, I expandded the "Replication ->Local publication" and " Replication ->Local Subscription" but found no objects existing inside that. So i believe replication is not enabled on the SQL Server.
To confirm it again, I opened the replication monitor but I dont see anything in the left or the right pane.
In the left pane, when I try to add a Add Publisher by (Replication Monitor -> My Publishers -> Add Publisher -> Add SQL Server Publisher) and connect to the current server, it throws an error like below.
'Server 'ABCDEFGH' is neither a Publisher nor a Distributor, or you do not have permission to access replication functionality on this server.'
As I am sysadmin on the SQL server, so I believe, this is not a permission issue and the error confirms that the server is neither a publisher nor a Distributor.
So here, my question is why 'log_reuse_wait_desc' is showing as REPLICATION where as no replication is enabled on the server. What to do to figure out what is the replication all about, analyse it, disable/ delete /stop the replication. I dont see any option in SSMS.
The log is growing hugely and is currently 150 GB. Please need your help.
Toutes les réponses
dimanche 29 avril 2012 21:58
Here is the solution or explanation you were looking for.
Regards JakDBA Please Mark this as Answered if this solves your issue or satisfied with the response.
dimanche 29 avril 2012 22:36Modérateur
dimanche 29 avril 2012 22:46
Are you using CDC (Change Data Capture) at all? It could also be this as CDC uses replication in the background and this is a very common reason for seeing replication when you are not using replication.
- Proposé comme réponse klarose jeudi 6 septembre 2012 19:00
lundi 30 avril 2012 01:10
This is SQL 2005. So I will rule out the possibility of CDC. Thanks for your suggestion and time Sean. I am checking the other 2 suggestions.
lundi 30 avril 2012 01:15
Thanks, I have been checking that tip. I believe someone has tried to setup a replication and removed it improperly and this has created the issue.
As Brandon has suggested, I will remove the replication using the sp.
Thanks for your time!
lundi 30 avril 2012 01:40
Thanks Brandon for the tip,
Also, I need to check when this unwanted replication was setup, when it was removed and if possible who did that. Can you please guide me.
lundi 30 avril 2012 05:30Modérateur