Yea iirc they disabled new alpha dbs a few months ago Under Workers & Pages -> D1, the database ID would be helpful (or you could just copy it from that error, it's the one at the end there hyphen seperated. Your Account ID would also be useful. It's under Workers & Pges overview or the /accounts/<accountid> in that error. I would OCR them but it's going to mess them up somewhere. They aren't private or anything but would let the D1 Team look into the DB
looks like it recovered a bit - but yeah its reaching the limits of what a single d1 db can do in terms of read/writes before we add read replication and autoscaling
I've been working on analytics for D1's queries on the side, starting with wrangler, you'll be able to find your slowest or most expensive queries by rowsRead/rowsWritten
Hey! Is there an estimate of what should be the expected per-db storage limit after the beta is over?
2GB would be way too low for any production application, and i understand it will probably be increased, but i'd like to know how high is it expected to go, as i know that the intended use case is "one db per user" but we expected to use it as a normal database.
is there any way of "dynamically binding" a D1 database? I cant see a way of applying the idea of using D1 in a multitenant environment without needing to manage a worker deployment for every customer..