|
|
|
|
|
by jnesbitt
5185 days ago
|
|
At the moment we only support what's documented in the SBQL docs, but we're open to any suggestions you have. Other features can be implemented as add-ons, if the demand is strong enough. Note taken about the docs only being available after signing in. Thanks for your feedback! |
|
For something like 100,000 records - in general a pretty standard instance of mysql can cope just fine. A lot of the time the database you get free with shared hosting, can cope with queries on this sort of size database just fine (as long as they have indexes). (Or the free database you get with heroku)
... true yes you have to do a bit more sysadmin tasks - maybe even backups etc. But all very doable.
As a beginner at sysadmin tasks, I start to struggle with mid-size datasets. A couple of million records. This is when backups begin getting a pain. Query optimization is actully required. Things start getting painful. full-text search is non trivial. geo-indexes are cumbersome.
But its harder finding a database provider for this sort of size. getsignalbox's doesn't even consider this possibility (other than the 'get in touch') - it might well be able to cater. But talking at $200+ a month, which starts to get serious. + this sort of mid size is where the cloud could excel, where sysadmin tasks start to get non-trivial.
Another thing missing - is a simple bulk upload - to be able to import a midsized dataset to be able to try out the service. Even if that is a 200Mb CSV file :)
IMHO of course! (Or I need to think smaller ;)