I've read a bit about Filemaker Server and still can't figure out whether it acts as a true database server in a full-blown client/server database environment, or just as some sort of optimized file server.
The difference, for anyone who doesn't know, is that a true database server responds to query requests (usually in SQL) from clients, and each query is processed entirely using the CPU on the server. For a select query, for example, the server will process the query independent of the requesting client, and will then send the result set back to the client. The client does no processing of the query. Fileservers, on the other hand, merely make the files available to the client machines, which do the processing of the queries themselves.
It strikes me as odd that the FM Server literature doesn't clarify whether it's a database server or a file server. It does talk about serving the database files, but in a way that leaves (to me, at least) some ambiguity about what's actually going on in the relationships between client machines and the server machine.
Can anybody clarify things for me?
Thanks,
Herb Sitz
The difference, for anyone who doesn't know, is that a true database server responds to query requests (usually in SQL) from clients, and each query is processed entirely using the CPU on the server. For a select query, for example, the server will process the query independent of the requesting client, and will then send the result set back to the client. The client does no processing of the query. Fileservers, on the other hand, merely make the files available to the client machines, which do the processing of the queries themselves.
It strikes me as odd that the FM Server literature doesn't clarify whether it's a database server or a file server. It does talk about serving the database files, but in a way that leaves (to me, at least) some ambiguity about what's actually going on in the relationships between client machines and the server machine.
Can anybody clarify things for me?
Thanks,
Herb Sitz