Distribution clean up job in transactional replication removed records but not files





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







1















Distribution clean up job ran without errors according to schedule, but I noticed that the snapshot files were not removed even if when created beyond max_disretention period. Records from msrepl_commands and msrepl_transactions were removed, but the files were not.





  • immediate_sync = 1


  • max_disretention = 72 hours










share|improve this question
















bumped to the homepage by Community 5 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 1





    This sounds like a permission issue. Have you granted the service accounts (SQL Engine and Agent on the distribution server) full access to the directory where the replication files live?

    – nkdbajoe
    Aug 28 '16 at 18:47


















1















Distribution clean up job ran without errors according to schedule, but I noticed that the snapshot files were not removed even if when created beyond max_disretention period. Records from msrepl_commands and msrepl_transactions were removed, but the files were not.





  • immediate_sync = 1


  • max_disretention = 72 hours










share|improve this question
















bumped to the homepage by Community 5 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 1





    This sounds like a permission issue. Have you granted the service accounts (SQL Engine and Agent on the distribution server) full access to the directory where the replication files live?

    – nkdbajoe
    Aug 28 '16 at 18:47














1












1








1








Distribution clean up job ran without errors according to schedule, but I noticed that the snapshot files were not removed even if when created beyond max_disretention period. Records from msrepl_commands and msrepl_transactions were removed, but the files were not.





  • immediate_sync = 1


  • max_disretention = 72 hours










share|improve this question
















Distribution clean up job ran without errors according to schedule, but I noticed that the snapshot files were not removed even if when created beyond max_disretention period. Records from msrepl_commands and msrepl_transactions were removed, but the files were not.





  • immediate_sync = 1


  • max_disretention = 72 hours







sql-server transactional-replication






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 28 '16 at 14:22









Eran

23914




23914










asked Feb 5 '15 at 15:07









EldarEldar

1135




1135





bumped to the homepage by Community 5 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 5 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.










  • 1





    This sounds like a permission issue. Have you granted the service accounts (SQL Engine and Agent on the distribution server) full access to the directory where the replication files live?

    – nkdbajoe
    Aug 28 '16 at 18:47














  • 1





    This sounds like a permission issue. Have you granted the service accounts (SQL Engine and Agent on the distribution server) full access to the directory where the replication files live?

    – nkdbajoe
    Aug 28 '16 at 18:47








1




1





This sounds like a permission issue. Have you granted the service accounts (SQL Engine and Agent on the distribution server) full access to the directory where the replication files live?

– nkdbajoe
Aug 28 '16 at 18:47





This sounds like a permission issue. Have you granted the service accounts (SQL Engine and Agent on the distribution server) full access to the directory where the replication files live?

– nkdbajoe
Aug 28 '16 at 18:47










1 Answer
1






active

oldest

votes


















0














the "immediate sync" option is the problem here. Unless you are regularly adding new subscribers every few hours, then this can be set to false and the snapshots are then cleared out after being applied.



exec sp_changepublication
@publication=N'<publication_name>',
@property=N'allow_anonymous',
@value='false';
go

exec sp_changepublication
@publication=N'<publication_name>',
@property=N'immediate_sync',
@value='false';
go


There is a lot of really good information about this here: http://www.replicationanswers.com/TransactionalOptimisation.asp






share|improve this answer
























  • Tried this with no luck. I suspect records from Msrepl_commands somehow removed without touching files, after that those files keep forever.

    – Eldar
    Feb 6 '15 at 8:01












Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f91188%2fdistribution-clean-up-job-in-transactional-replication-removed-records-but-not-f%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














the "immediate sync" option is the problem here. Unless you are regularly adding new subscribers every few hours, then this can be set to false and the snapshots are then cleared out after being applied.



exec sp_changepublication
@publication=N'<publication_name>',
@property=N'allow_anonymous',
@value='false';
go

exec sp_changepublication
@publication=N'<publication_name>',
@property=N'immediate_sync',
@value='false';
go


There is a lot of really good information about this here: http://www.replicationanswers.com/TransactionalOptimisation.asp






share|improve this answer
























  • Tried this with no luck. I suspect records from Msrepl_commands somehow removed without touching files, after that those files keep forever.

    – Eldar
    Feb 6 '15 at 8:01
















0














the "immediate sync" option is the problem here. Unless you are regularly adding new subscribers every few hours, then this can be set to false and the snapshots are then cleared out after being applied.



exec sp_changepublication
@publication=N'<publication_name>',
@property=N'allow_anonymous',
@value='false';
go

exec sp_changepublication
@publication=N'<publication_name>',
@property=N'immediate_sync',
@value='false';
go


There is a lot of really good information about this here: http://www.replicationanswers.com/TransactionalOptimisation.asp






share|improve this answer
























  • Tried this with no luck. I suspect records from Msrepl_commands somehow removed without touching files, after that those files keep forever.

    – Eldar
    Feb 6 '15 at 8:01














0












0








0







the "immediate sync" option is the problem here. Unless you are regularly adding new subscribers every few hours, then this can be set to false and the snapshots are then cleared out after being applied.



exec sp_changepublication
@publication=N'<publication_name>',
@property=N'allow_anonymous',
@value='false';
go

exec sp_changepublication
@publication=N'<publication_name>',
@property=N'immediate_sync',
@value='false';
go


There is a lot of really good information about this here: http://www.replicationanswers.com/TransactionalOptimisation.asp






share|improve this answer













the "immediate sync" option is the problem here. Unless you are regularly adding new subscribers every few hours, then this can be set to false and the snapshots are then cleared out after being applied.



exec sp_changepublication
@publication=N'<publication_name>',
@property=N'allow_anonymous',
@value='false';
go

exec sp_changepublication
@publication=N'<publication_name>',
@property=N'immediate_sync',
@value='false';
go


There is a lot of really good information about this here: http://www.replicationanswers.com/TransactionalOptimisation.asp







share|improve this answer












share|improve this answer



share|improve this answer










answered Feb 5 '15 at 21:50









Nick BurnsNick Burns

1662




1662













  • Tried this with no luck. I suspect records from Msrepl_commands somehow removed without touching files, after that those files keep forever.

    – Eldar
    Feb 6 '15 at 8:01



















  • Tried this with no luck. I suspect records from Msrepl_commands somehow removed without touching files, after that those files keep forever.

    – Eldar
    Feb 6 '15 at 8:01

















Tried this with no luck. I suspect records from Msrepl_commands somehow removed without touching files, after that those files keep forever.

– Eldar
Feb 6 '15 at 8:01





Tried this with no luck. I suspect records from Msrepl_commands somehow removed without touching files, after that those files keep forever.

– Eldar
Feb 6 '15 at 8:01


















draft saved

draft discarded




















































Thanks for contributing an answer to Database Administrators Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f91188%2fdistribution-clean-up-job-in-transactional-replication-removed-records-but-not-f%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Ronny Ackermann

Köttigit

MySQL 8.0.15 starts normally but any connection hangs