Normal
Hi,In my setup SQL server takes about 24MB of memory (so would a well-configured MySQL database, by the way). I wouldn't call that resource-hungry now that 512MB or even more is pretty much standard.Personally I wouldn't even mind it taking more memory as it will more likely avoid high cost disk I/O and keep the system responding well.Another bad thing (IMHO even worse than the "single writer causes no readers" issue) is that all datatypes are implicitly converted to strings. You can even store a character string in a number field if you'd like to...File databases in the end just don't scale well when being accessed from multiple sources. Not to mention remote connectivity to a database.Kind regards,Michel
Hi,
In my setup SQL server takes about 24MB of memory (so would a well-configured MySQL database, by the way). I wouldn't call that resource-hungry now that 512MB or even more is pretty much standard.
Personally I wouldn't even mind it taking more memory as it will more likely avoid high cost disk I/O and keep the system responding well.
Another bad thing (IMHO even worse than the "single writer causes no readers" issue) is that all datatypes are implicitly converted to strings. You can even store a character string in a number field if you'd like to...
File databases in the end just don't scale well when being accessed from multiple sources. Not to mention remote connectivity to a database.
Kind regards,
Michel
