Hello everyone. Can somebody please explain to me why databases are intrinsically tied to the web host plan. Like with most hosts, you have to pay for databases, in size and in number. Why is that something that the host controls? Is it not possible to simply have a database file and read and write to that without having some dedicated database operated by the host? I'm just a little bit confused. If I'm not clarifying myself well, please let me know. Thank you.
There are basically 2 types of database: 1) An RDBMS where the database process executes externally to the web application process 2) An embedded database where db data processing is performed as part of the web application process. More info here: http://en.wikipedia.org/wiki/Relational_database_management_system http://en.wikipedia.org/wiki/Embedded_database Very often (but not always) there is a cost impact to the customer associated with a host provisioning a database in an RDBMS. Conversely almost always there's no cost associated by the use of an embedded database. As such there are pros and cons to both approaches. A 'database file' as you put it is the embedded option e.g. MS Access, SQL Server Compact, Sqlite etc When a host is provides an RDBMS platform including the maintenance of that platform, there's usually some cost involved because at the end of the day the host is a business providing a service to their customers and the host has their own costs to cover e.g. datacentre racking / tech staff etc.
Thank you for the fast response! So there it's technically possible to have an embedded database on DiscountASP.net without paying for a a dedicated database, provided I'm willing to cope with the added cpu cycles and storage concerns of not separating out my database? I only ask because I'm trying to weigh my options here, and I've never understood this aspect of web hosting.
Yes sure use of an embedded db is technically possible - there is no limiter WRT that on DASP. In the past I've developed proof of concept ASP.NET web apps and successfully hosted them on the DASP web server with a number of different embedded db types including MS Access, SQL Server Compact and VistaDB. I've never tried Sqlite but I've no reason to suspect that this wouldn't work either. A personal recommendation is to avoid MS Access altogether. It's also worth mentioning that an embedded database won't be an ideal fit for every use case - it really depends on your application and what you're trying to do. As I mentioned in my 1st post there are pros and cons to both RDBMS and embedded dbs. Some careful thought about your particular application and how it will be designed will hopefully result in you making the right choice now (RDBMS / embedded) and mitigate risk of having to u-turn on the chosen db technology later.
