I figured I would ask Thwack Nation, while I wait on support. Anyone else out there have this problem before, any advice?
Support keeps wanting to tell me this is all due to record retention, however, I simply cannot wrap my brain around that answer. I am not saying that answer is wrong. I am simply saying it does not make sense to me. Perhaps there is a better example out there that would better assist my acceptance, however, as it stands now, I am simply not buying that answer.
DB server was configured based on SolarWinds best practice pdf, so the current settings, for the most part, should be configured accordingly.
We have not recently added a massive amount of nodes/interfaces/etc.
I know there are many other specific details I have not mentioned here, but I figured I would at least get this posted, and will add more details if needed.
Orion Platform 2015.1.2, NCM 7.4, NPM 11.5.2, DPA 10.0.0, IVIM 2.1.0, SAM 6.2.2
Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64)
Oct 19 2012 13:38:57
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
I have pasted a couple of the descriptions I sent to support, below.
"Case # 950343 Created: Our Orion database has been rapidly increasing in size over the past few weeks."
Our Orion database has been rapidly increasing in size over the past few weeks. Prior to this issue, our database was growing slowly and steadily, being approximately 65GB-70GB. We had projections of the database reaching 100GB by the end of 2016, or early 2017.
We had a few latency issue, so we rebuilt the SQL server, and swapped them out. A few weeks later, and our database is now over 100GB, which is approximately a full year ahead of schedule.
I have gone through the SQL server settings, as well as the DB settings, and verified the new server matches the old server. I have even gone through and reduced the number of device configs stored in the db, as well as the length of time, which freed up over 5GB of db storage space.
We need to determine why our db is growing so rapidly, and see what we can do to prevent this, or at least slow it down.
Shrinking the DB does absolutely nothing, as there is no space to shrink. Everything there is being used, or at least appears to be, and does not shrink more than a few MB.
Before we rebuilt our SQL server, our DB was approximately 70GB. DB growth was very slow, taking 4-6 months to grow from 60GB to 70GB. We had projected to reach, or be close to reaching, the 100GB size close to the end of this year, or early 2017. Over the past 4 weeks, or so, after rebuilding, and switching over to, our new SQL server, our DB has grown nearly 40 GB. Currently, our DB is approximately 107GB, and growing roughly 100MB every 45-75 minutes.
I have attached a chart/graph showing the severely sharp and rapid increase in the DB size. I am very far from being convinced this is simply due to our data retention. There must be a better, and more believable, explanation.