Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
purdyra
Starting Member
7 Posts |
Posted - 2011-05-23 : 16:10:37
|
Our company db file (not log file) has been about 160 gb monday thru saturday. Then on Sunday it grew to 260 gb. I am trying to figure out why or what is doing this.Due to the db growing so large, the backup failed becz their isn't enough disk space if the db is that large. I do realize I can do a shrink db, but I am just trying to understand what would cause this.I looked at the jobs/maintenance plan that ran and pretty much all I see is a dbcccheck integrity of db's, rebuild indexessystem db's weekly maintdbcc checkdb with no infomsgsany ideas of what could be causing this or some direction of something else to look at to uncover why this is happening? thanks for your help. |
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
purdyra
Starting Member
7 Posts |
Posted - 2011-05-23 : 16:35:31
|
I was thinking that was probably it but I don't understand why, not that I have to know everything about it.from what I read, it said that when indexes are rebuilt it makes a complete copy of it and when done deletes the other one (no data is lost). so in my mind, I would think it would grow but then shrink again. although as i type this and am thinking this thru now, if the db has enlarged for the copy of the indexes then it won't shrink unless i do an autoshrink. am i on the right track? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
purdyra
Starting Member
7 Posts |
Posted - 2011-05-23 : 17:12:42
|
thanks for the info. As I look at my maint plan I also have reorg indexes on the opposite weeks of the month.am i correct in thinking that a reorg does not create a copy so therefore will not increase my db size? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
|