How safe is to use BACKUP LOG WITH TRUNCATE_ONLY












0















As per the title, how much is it safe to use BACKUP LOG db_name WITH TRUNCATE_ONLY in last STEP of any SQL-job execution? Randomly found on google that this Code line can be very harmful in use. But how?



I am using my code as below in one of my SQL-job's last STEP.



BACKUP LOG  my_database with Truncate_Only
DBCC SHRINKFILE (N'my_database_Data')
DBCC SHRINKFILE (N'my_database_Log')


Let me simplify the question with below aspects:




  1. What actually doing this code in the SQL-Job? Does it really help?

  2. Is there anything related performance of the DB-Server?

  3. If I remove first line of code (BACKUP LOG), how it can get effect?

  4. Currently I am not able see SQL-Job history of same SQL-Job, is this the reason that it clears all logs?


This could be opinion based question but still let's discuss if you can share some Ideas on it.









share























  • I'm not sure if this will even work - truncate_only was removed in 2008 as far as I'm aware? The only log specific backup options I can find are no_truncate and copy_only.

    – George.Palacios
    3 mins ago
















0















As per the title, how much is it safe to use BACKUP LOG db_name WITH TRUNCATE_ONLY in last STEP of any SQL-job execution? Randomly found on google that this Code line can be very harmful in use. But how?



I am using my code as below in one of my SQL-job's last STEP.



BACKUP LOG  my_database with Truncate_Only
DBCC SHRINKFILE (N'my_database_Data')
DBCC SHRINKFILE (N'my_database_Log')


Let me simplify the question with below aspects:




  1. What actually doing this code in the SQL-Job? Does it really help?

  2. Is there anything related performance of the DB-Server?

  3. If I remove first line of code (BACKUP LOG), how it can get effect?

  4. Currently I am not able see SQL-Job history of same SQL-Job, is this the reason that it clears all logs?


This could be opinion based question but still let's discuss if you can share some Ideas on it.









share























  • I'm not sure if this will even work - truncate_only was removed in 2008 as far as I'm aware? The only log specific backup options I can find are no_truncate and copy_only.

    – George.Palacios
    3 mins ago














0












0








0








As per the title, how much is it safe to use BACKUP LOG db_name WITH TRUNCATE_ONLY in last STEP of any SQL-job execution? Randomly found on google that this Code line can be very harmful in use. But how?



I am using my code as below in one of my SQL-job's last STEP.



BACKUP LOG  my_database with Truncate_Only
DBCC SHRINKFILE (N'my_database_Data')
DBCC SHRINKFILE (N'my_database_Log')


Let me simplify the question with below aspects:




  1. What actually doing this code in the SQL-Job? Does it really help?

  2. Is there anything related performance of the DB-Server?

  3. If I remove first line of code (BACKUP LOG), how it can get effect?

  4. Currently I am not able see SQL-Job history of same SQL-Job, is this the reason that it clears all logs?


This could be opinion based question but still let's discuss if you can share some Ideas on it.









share














As per the title, how much is it safe to use BACKUP LOG db_name WITH TRUNCATE_ONLY in last STEP of any SQL-job execution? Randomly found on google that this Code line can be very harmful in use. But how?



I am using my code as below in one of my SQL-job's last STEP.



BACKUP LOG  my_database with Truncate_Only
DBCC SHRINKFILE (N'my_database_Data')
DBCC SHRINKFILE (N'my_database_Log')


Let me simplify the question with below aspects:




  1. What actually doing this code in the SQL-Job? Does it really help?

  2. Is there anything related performance of the DB-Server?

  3. If I remove first line of code (BACKUP LOG), how it can get effect?

  4. Currently I am not able see SQL-Job history of same SQL-Job, is this the reason that it clears all logs?


This could be opinion based question but still let's discuss if you can share some Ideas on it.







sql-server sql-server-2012 backup transaction-log shrink





share












share










share



share










asked 9 mins ago









im_oneim_one

1177




1177













  • I'm not sure if this will even work - truncate_only was removed in 2008 as far as I'm aware? The only log specific backup options I can find are no_truncate and copy_only.

    – George.Palacios
    3 mins ago



















  • I'm not sure if this will even work - truncate_only was removed in 2008 as far as I'm aware? The only log specific backup options I can find are no_truncate and copy_only.

    – George.Palacios
    3 mins ago

















I'm not sure if this will even work - truncate_only was removed in 2008 as far as I'm aware? The only log specific backup options I can find are no_truncate and copy_only.

– George.Palacios
3 mins ago





I'm not sure if this will even work - truncate_only was removed in 2008 as far as I'm aware? The only log specific backup options I can find are no_truncate and copy_only.

– George.Palacios
3 mins ago










0






active

oldest

votes











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%2f227947%2fhow-safe-is-to-use-backup-log-with-truncate-only%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















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%2f227947%2fhow-safe-is-to-use-backup-log-with-truncate-only%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

SQL Server 17 - Attemping to backup to remote NAS but Access is denied

Always On Availability groups resolving state after failover - Remote harden of transaction...

Restoring from pg_dump with foreign key constraints