Advice on how to build a business case for partitioning
Hi Everyone,
I'm the architect of a business intelligence/data warehouse team. We've grown to the point where I believe we need database partitioning. I believe we are at about 1.5 TB of data. Our largest tables are in the 100 million row counts with relatively wide record lengths (~100 columns). Our just sort of large tables are in the 10 million to 50 million range, however, they have very long row lengths (~300 columns). Based on our future source system plans, our data will become even more granular and there is still a need to maintain our historical data.
Those aren't the only reasons, but are some of the larger driving issues that are making most members of our team think it's time we purchased database partitioning. Our team is pretty unanimous for partitioning, many of our source system partners also consider it a "no-brainer", however, we're getting push back from our CIO saying that 1.5 TB and 100 million records isn't that much data as compared to other "big data" companies and that it doesn't require partitioning.
Does anyone have a advice on how to build an business case for purchasing partitioning? Is there a good way to demonstrate cost-vs-benefit value?
Thanks for your feedback.
-=Joe