Allow Incremental DISK (Database Storage) Expansion in excess of tier limits
The tier level price jump is significant simply for more storage space. My preference would be that the tier pricing be more targeted to the CPU and MEMORY with a base storage limit plus price per GB per month over that size.
-
Guest
- Mar 1 2019
- Future consideration
Related ideas
Huge bump. Unable to store time-series data in my database.
Attachments Open full size
Any update on this?
Attachments Open full size
Duplicate marked as Planned: https://ideas.digitalocean.com/ideas/DBAAS-I-49
Attachments Open full size
Please implement, I'm on a clock with this. I can't justify doubling my cost for doubling my storage.
If this isn't implemented soon I'm going to have to revert to a self-managed solution...
Attachments Open full size
I see this is request is repeated, so I'll copy my comment in support of this: Not all use-cases are I/O intensive enough to justify an upgrade in the higher tiers. Sometimes more indexing is enoguh, which of course requires more disk space. I understand the complexity of having volumes attached/detached from the database cluster, though I can imagine this being implemented with tablespaces (at least in Postgres)
Attachments Open full size
An absolutely essential feature for production environments. Blown away this was not implemented when managed databases went live - a total non-starter.Â
Attachments Open full size
+1
Attachments Open full size
agree with Iban Eguia, it would be cool to be able to attach volumes to managed databases
Attachments Open full size
Would be nice to have something like the "block storage" for databases.
Attachments Open full size
This is absolutely essential. We need to store data on the order of many TBs (6TB+), but even if we were to use the 1.12TB database, we don't need 64GB of RAM and 16 CPUs. It'd be great to be able to provision additional storage on top of what the plan allocates.
Attachments Open full size