We moved our back-end system to a hosting provider a couple of years ago. When it was onsite the db was running around 18 gig, and had been fairly consistent at that size most of the time I'd been here, about 3 years.
Now our provider is changing their pricing model to reflect the database size and they're saying it's up to 55 gig, and that's just over a level for a price increase.
Now, we have been putting a little more data in, mostly comments related to accounts, but there has been a ton of activity since our new data manager came on board and has been de-duplicating data, merging accounts, etc.
No one here is remotely SQL savvy, even when the data was here we let the vendor manage it. And I am presuming the current provider is using MS SQL since they also provide lots of remote services that center around MS products, like MS Terminal Services and Office.
So the question is, do we request that our provider perform some kind of maintenance on the database to see if it can be smaller? Would they have good reason to refuse? Or should we not bother and just leave it as is and pay the next higher rate?
