Is It normal to keep log file larger than data file?Shrink Tempdb log file when reaching a specific sizeSQL Server Transaction Log Initial Data LoadHow best to maintain SQL log file sizesHow to pinpoint root cause of excessive log file growthTransaction log backup file larger than expected?Should I shrink the Log FileAlways On log files bigger than database filesIs it bad to have index space larger than data space?Why is my log file so massive? 22gb. I am running log backups
Understanding the past growth of an ETF
'Cheddar goes "good" with burgers?' Can "go" be seen as a verb of the senses?
Why not build an "approximate" Analytical Engine before the complete one?
Why is matter-antimatter asymmetry surprising, if asymmetry can be generated by a random walk in which particles go into black holes?
Creating chess engine, machine learning vs. traditional engine?
D&D Monsters and Copyright
grep pairs of patterns and file
How much money should I save in order to generate $1000/month for the rest of my life?
Does journal access significantly influence choice in which journal to publish in?
Is having your hand in your pocket during a presentation bad?
Postman Delivery
A sentient carnivorous species trying to preserve life. How could they find a new food source?
Relation between signal processing and control systems engineering?
Are there any privately owned large commercial airports?
Are there any official mechanics for grafts or anything similar?
Why do English transliterations of Arabic names have so many Qs in them?
Rat proofing compost bin but allowing worms in
Does the Creighton Method of Natural Family Planning have a failure rate of 3.2% or less?
Proving roots of a function cannot all be real
How are steel imports supposed to threaten US national security?
Comparison of values in dictionary
"Es gefällt ihm." How to identify similar exceptions?
Do "chess engine in the cloud" services exist?
What determines the top speed in ice skating?
Is It normal to keep log file larger than data file?
Shrink Tempdb log file when reaching a specific sizeSQL Server Transaction Log Initial Data LoadHow best to maintain SQL log file sizesHow to pinpoint root cause of excessive log file growthTransaction log backup file larger than expected?Should I shrink the Log FileAlways On log files bigger than database filesIs it bad to have index space larger than data space?Why is my log file so massive? 22gb. I am running log backups
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
Is It normal to keep log file larger than data file?
I know why my log file is large, it is because I have a huge modification and locking occurred on a specific time, and caused my log file to be large.. as i'm using log shipping, I normally take log backups every 10 minutes.
What I'm asking is "Is it normal to see Log file larger than data file as my data file is about 7,216 GB and my log file is about 9,930 GB?" I'm afraid there is a standard ratio between log and data file? I don't want to shrink my log file because I have enough space on my hard disk.
sql-server sql-server-2008-r2
edited 7 hours ago
dezso
23.5k12 gold badges63 silver badges103 bronze badges
asked 8 hours ago
Ayman FaroukAyman Farouk
111 bronze badge
New contributor
Ayman Farouk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment
|
Is It normal to keep log file larger than data file?
I know why my log file is large, it is because I have a huge modification and locking occurred on a specific time, and caused my log file to be large.. as i'm using log shipping, I normally take log backups every 10 minutes.
What I'm asking is "Is it normal to see Log file larger than data file as my data file is about 7,216 GB and my log file is about 9,930 GB?" I'm afraid there is a standard ratio between log and data file? I don't want to shrink my log file because I have enough space on my hard disk.
sql-server sql-server-2008-r2
edited 7 hours ago
dezso
23.5k12 gold badges63 silver badges103 bronze badges
asked 8 hours ago
Ayman FaroukAyman Farouk
111 bronze badge
New contributor
Ayman Farouk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Possible duplicate of Shrink Tempdb log file when reaching a specific size
– mustaccio
8 hours ago
add a comment
|
Is It normal to keep log file larger than data file?
I know why my log file is large, it is because I have a huge modification and locking occurred on a specific time, and caused my log file to be large.. as i'm using log shipping, I normally take log backups every 10 minutes.
What I'm asking is "Is it normal to see Log file larger than data file as my data file is about 7,216 GB and my log file is about 9,930 GB?" I'm afraid there is a standard ratio between log and data file? I don't want to shrink my log file because I have enough space on my hard disk.
sql-server sql-server-2008-r2
edited 7 hours ago
dezso
23.5k12 gold badges63 silver badges103 bronze badges
asked 8 hours ago
Ayman FaroukAyman Farouk
111 bronze badge
New contributor
Ayman Farouk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Is It normal to keep log file larger than data file?
I know why my log file is large, it is because I have a huge modification and locking occurred on a specific time, and caused my log file to be large.. as i'm using log shipping, I normally take log backups every 10 minutes.
What I'm asking is "Is it normal to see Log file larger than data file as my data file is about 7,216 GB and my log file is about 9,930 GB?" I'm afraid there is a standard ratio between log and data file? I don't want to shrink my log file because I have enough space on my hard disk.
sql-server sql-server-2008-r2
sql-server sql-server-2008-r2
edited 7 hours ago
dezso
23.5k12 gold badges63 silver badges103 bronze badges
asked 8 hours ago
Ayman FaroukAyman Farouk
111 bronze badge
New contributor
Ayman Farouk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 7 hours ago
dezso
23.5k12 gold badges63 silver badges103 bronze badges
asked 8 hours ago
Ayman FaroukAyman Farouk
111 bronze badge
New contributor
Ayman Farouk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 7 hours ago
dezso
23.5k12 gold badges63 silver badges103 bronze badges
edited 7 hours ago
dezso
23.5k12 gold badges63 silver badges103 bronze badges
edited 7 hours ago
dezso
23.5k12 gold badges63 silver badges103 bronze badges
23.5k12 gold badges63 silver badges103 bronze badges
asked 8 hours ago
Ayman FaroukAyman Farouk
111 bronze badge
New contributor
Ayman Farouk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 8 hours ago
Ayman FaroukAyman Farouk
111 bronze badge
asked 8 hours ago
Ayman FaroukAyman Farouk
111 bronze badge
111 bronze badge
New contributor
Ayman Farouk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Ayman Farouk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Possible duplicate of Shrink Tempdb log file when reaching a specific size
– mustaccio
8 hours ago
add a comment
|
1
Possible duplicate of Shrink Tempdb log file when reaching a specific size
– mustaccio
8 hours ago
1
1
Possible duplicate of Shrink Tempdb log file when reaching a specific size
– mustaccio
8 hours ago
Possible duplicate of Shrink Tempdb log file when reaching a specific size
– mustaccio
8 hours ago
add a comment
|
2 Answers
2
active
oldest
votes
If you have a huge modification going on, then yes, it can be normal to have a log file larger than your data file. After the huge modification is over, and the log backup is done, the file will not shrink back to it's original size however. But the file will be empty.
You can see this in Management Studio, if you right-click on the database and select Reports->Disk Usage.
I don't recommend shrinking your log file as it will only grow back the next time it needs space. But, if you are running out of disk space, know that it is possible to shrink your log file. I just don't do it, as the space gets used every time it needs to and as it's a better practice to leave it as it is.
answered 8 hours ago
Danielle Paquette-HarveyDanielle Paquette-Harvey
6761 gold badge7 silver badges16 bronze badges
add a comment
|
It may be unusual to see log files much larger than the data in a properly configured server with well behaved applications, but it isn't wrong. SQL Server assumes that because at one time the log file needed to be grown that long that it will need that much space again so keeps it that long unless told to do otherwise.
I'm afraid there is a standard ratio between log and data file?
There is not. There are circumstances where you would expect the log file to be relatively large even without one-off large operations like the one you mention (for instance: any small database configured for full recovery, that sees a great many insert/update/delete operations over that small set of data between each log backup).
I don't want to shrink my log file because I have enough space on my hard disk.
If the operation that caused the log file to balloon is genuinely a one-off or otherwise a rare event then there would be no harm in truncating it (just truncate, not rearrange, and down to a size that still leaves plenty free for expected growth) to free filesystem space, but if you don't need the filesystem space to be freed then I wouldn't bother as the space being allocated for possible future use is not causing issues.
answered 6 hours ago
David SpillettDavid Spillett
24.2k3 gold badges34 silver badges71 bronze badges
add a comment
|
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/4.0/"u003ecc by-sa 4.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
);
);
Ayman Farouk is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f250016%2fis-it-normal-to-keep-log-file-larger-than-data-file%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you have a huge modification going on, then yes, it can be normal to have a log file larger than your data file. After the huge modification is over, and the log backup is done, the file will not shrink back to it's original size however. But the file will be empty.
You can see this in Management Studio, if you right-click on the database and select Reports->Disk Usage.
I don't recommend shrinking your log file as it will only grow back the next time it needs space. But, if you are running out of disk space, know that it is possible to shrink your log file. I just don't do it, as the space gets used every time it needs to and as it's a better practice to leave it as it is.
answered 8 hours ago
Danielle Paquette-HarveyDanielle Paquette-Harvey
6761 gold badge7 silver badges16 bronze badges
add a comment
|
If you have a huge modification going on, then yes, it can be normal to have a log file larger than your data file. After the huge modification is over, and the log backup is done, the file will not shrink back to it's original size however. But the file will be empty.
You can see this in Management Studio, if you right-click on the database and select Reports->Disk Usage.
I don't recommend shrinking your log file as it will only grow back the next time it needs space. But, if you are running out of disk space, know that it is possible to shrink your log file. I just don't do it, as the space gets used every time it needs to and as it's a better practice to leave it as it is.
answered 8 hours ago
Danielle Paquette-HarveyDanielle Paquette-Harvey
6761 gold badge7 silver badges16 bronze badges
add a comment
|
If you have a huge modification going on, then yes, it can be normal to have a log file larger than your data file. After the huge modification is over, and the log backup is done, the file will not shrink back to it's original size however. But the file will be empty.
You can see this in Management Studio, if you right-click on the database and select Reports->Disk Usage.
I don't recommend shrinking your log file as it will only grow back the next time it needs space. But, if you are running out of disk space, know that it is possible to shrink your log file. I just don't do it, as the space gets used every time it needs to and as it's a better practice to leave it as it is.
answered 8 hours ago
Danielle Paquette-HarveyDanielle Paquette-Harvey
6761 gold badge7 silver badges16 bronze badges
If you have a huge modification going on, then yes, it can be normal to have a log file larger than your data file. After the huge modification is over, and the log backup is done, the file will not shrink back to it's original size however. But the file will be empty.
You can see this in Management Studio, if you right-click on the database and select Reports->Disk Usage.
I don't recommend shrinking your log file as it will only grow back the next time it needs space. But, if you are running out of disk space, know that it is possible to shrink your log file. I just don't do it, as the space gets used every time it needs to and as it's a better practice to leave it as it is.
answered 8 hours ago
Danielle Paquette-HarveyDanielle Paquette-Harvey
6761 gold badge7 silver badges16 bronze badges
answered 8 hours ago
Danielle Paquette-HarveyDanielle Paquette-Harvey
6761 gold badge7 silver badges16 bronze badges
answered 8 hours ago
Danielle Paquette-HarveyDanielle Paquette-Harvey
6761 gold badge7 silver badges16 bronze badges
answered 8 hours ago
Danielle Paquette-HarveyDanielle Paquette-Harvey
6761 gold badge7 silver badges16 bronze badges
6761 gold badge7 silver badges16 bronze badges
add a comment
|
add a comment
|
It may be unusual to see log files much larger than the data in a properly configured server with well behaved applications, but it isn't wrong. SQL Server assumes that because at one time the log file needed to be grown that long that it will need that much space again so keeps it that long unless told to do otherwise.
I'm afraid there is a standard ratio between log and data file?
There is not. There are circumstances where you would expect the log file to be relatively large even without one-off large operations like the one you mention (for instance: any small database configured for full recovery, that sees a great many insert/update/delete operations over that small set of data between each log backup).
I don't want to shrink my log file because I have enough space on my hard disk.
If the operation that caused the log file to balloon is genuinely a one-off or otherwise a rare event then there would be no harm in truncating it (just truncate, not rearrange, and down to a size that still leaves plenty free for expected growth) to free filesystem space, but if you don't need the filesystem space to be freed then I wouldn't bother as the space being allocated for possible future use is not causing issues.
answered 6 hours ago
David SpillettDavid Spillett
24.2k3 gold badges34 silver badges71 bronze badges
add a comment
|
It may be unusual to see log files much larger than the data in a properly configured server with well behaved applications, but it isn't wrong. SQL Server assumes that because at one time the log file needed to be grown that long that it will need that much space again so keeps it that long unless told to do otherwise.
I'm afraid there is a standard ratio between log and data file?
There is not. There are circumstances where you would expect the log file to be relatively large even without one-off large operations like the one you mention (for instance: any small database configured for full recovery, that sees a great many insert/update/delete operations over that small set of data between each log backup).
I don't want to shrink my log file because I have enough space on my hard disk.
If the operation that caused the log file to balloon is genuinely a one-off or otherwise a rare event then there would be no harm in truncating it (just truncate, not rearrange, and down to a size that still leaves plenty free for expected growth) to free filesystem space, but if you don't need the filesystem space to be freed then I wouldn't bother as the space being allocated for possible future use is not causing issues.
answered 6 hours ago
David SpillettDavid Spillett
24.2k3 gold badges34 silver badges71 bronze badges
add a comment
|
It may be unusual to see log files much larger than the data in a properly configured server with well behaved applications, but it isn't wrong. SQL Server assumes that because at one time the log file needed to be grown that long that it will need that much space again so keeps it that long unless told to do otherwise.
I'm afraid there is a standard ratio between log and data file?
There is not. There are circumstances where you would expect the log file to be relatively large even without one-off large operations like the one you mention (for instance: any small database configured for full recovery, that sees a great many insert/update/delete operations over that small set of data between each log backup).
I don't want to shrink my log file because I have enough space on my hard disk.
If the operation that caused the log file to balloon is genuinely a one-off or otherwise a rare event then there would be no harm in truncating it (just truncate, not rearrange, and down to a size that still leaves plenty free for expected growth) to free filesystem space, but if you don't need the filesystem space to be freed then I wouldn't bother as the space being allocated for possible future use is not causing issues.
answered 6 hours ago
David SpillettDavid Spillett
24.2k3 gold badges34 silver badges71 bronze badges
It may be unusual to see log files much larger than the data in a properly configured server with well behaved applications, but it isn't wrong. SQL Server assumes that because at one time the log file needed to be grown that long that it will need that much space again so keeps it that long unless told to do otherwise.
I'm afraid there is a standard ratio between log and data file?
There is not. There are circumstances where you would expect the log file to be relatively large even without one-off large operations like the one you mention (for instance: any small database configured for full recovery, that sees a great many insert/update/delete operations over that small set of data between each log backup).
I don't want to shrink my log file because I have enough space on my hard disk.
If the operation that caused the log file to balloon is genuinely a one-off or otherwise a rare event then there would be no harm in truncating it (just truncate, not rearrange, and down to a size that still leaves plenty free for expected growth) to free filesystem space, but if you don't need the filesystem space to be freed then I wouldn't bother as the space being allocated for possible future use is not causing issues.
answered 6 hours ago
David SpillettDavid Spillett
24.2k3 gold badges34 silver badges71 bronze badges
answered 6 hours ago
David SpillettDavid Spillett
24.2k3 gold badges34 silver badges71 bronze badges
answered 6 hours ago
David SpillettDavid Spillett
24.2k3 gold badges34 silver badges71 bronze badges
answered 6 hours ago
David SpillettDavid Spillett
24.2k3 gold badges34 silver badges71 bronze badges
24.2k3 gold badges34 silver badges71 bronze badges
add a comment
|
add a comment
|
Ayman Farouk is a new contributor. Be nice, and check out our Code of Conduct.
Ayman Farouk is a new contributor. Be nice, and check out our Code of Conduct.
Ayman Farouk is a new contributor. Be nice, and check out our Code of Conduct.
Ayman Farouk is a new contributor. Be nice, and check out our Code of Conduct.
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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f250016%2fis-it-normal-to-keep-log-file-larger-than-data-file%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
1
Possible duplicate of Shrink Tempdb log file when reaching a specific size
– mustaccio
8 hours ago