We have this database at work that started growing last week. We only noticed it because we got a message from the server that we were running low on disk space. Upon investigation, an archive database had grow by about 12 GB over the past few days. No, it’s important to note that this database doesn’t get anything added to it, it’s only there for reporting purposes, nor are there any views being added to the database, it is essentially static.
It’s grown to the point that until we figure out what’s wrong with it, we’ve moved it to another server, but it’s still adding about 5 GB per day in space. We’ve compacted the indexes, compacted the database and nothing seems to work… If we make a new replica, it starts out at the correct size (about 29 GB) but then starts growing itself.
Anyone come across this before?
It’s grown to the point that until we figure out what’s wrong with it, we’ve moved it to another server, but it’s still adding about 5 GB per day in space. We’ve compacted the indexes, compacted the database and nothing seems to work… If we make a new replica, it starts out at the correct size (about 29 GB) but then starts growing itself.
Anyone come across this before?
Comments
Post a Comment