Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

My typical discovery scenario:

We receive an alert that the transaction log is growing quickly. We are in Simple Recovery so I go to check it out. Log is already sized to 100GB and is at 80% capacity. I run the "Whats using my log files" script from SQL Server Central and see that Replication is enabled on the database.

We do not set up replication, and I don't think Replication can be done on SharePoint content db's as Replication is not supported (requires PK on all tables). This has been occurring on random servers (about 5 so far, all within the past three weeks) and it only occurs on Content Databases.

sp_removedbreplication does not always work in removing the Replication either. We have found that we need to run the sp_removedbreplication, change all db owners to SA and reset Recovery Mode to Simple to completely eradicate any vestiges of this bug.

How would Replication be enabling itself? We have never set up Replication on these servers. There is no evidence of any type of Replication other than the 'log_reuse_wait_desc' from the DMV query and log growth. Any help on this ghost would be appreciated!

share|improve this question

2 Answers 2

Someone has to be turning it on. Sharepoint won't just enable replication by it self.

Setup a profiler trace for the replication stored procedures (I can get you some procedures names if needed) to see who is running them. That or enable server auditing for the execution of these procedures.

share|improve this answer
    
Any proc names you could get me would be appreciated, thank you! We restrict access to the servers to our team of four SQL engineers (none of us have set it up) and SQL and SharePoint Service accounts. Users can have access to the Service Accounts, but we cannot come up with how/why anyone would be doing this. –  Ddono25 Jan 6 '11 at 20:39
    
Some procedure names to trace for are: sp_replicationdboption, sp_adddistpublisher, sp_get_distrubutor. Those would be the procedures needed to flip the flag on replication for a database. Specifically the first one. –  mrdenny Jan 6 '11 at 20:50

Have you checked if any Change Data Capture isn't used? CDC is based on transactional replication and would also cause log growth if the log reader agent is unable to keep up.

share|improve this answer
    
No CDC inproduction yet, and that is where are issues are coming from. –  Ddono25 Mar 22 '11 at 17:23

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.