Razlike su velike za ozbiljan rad. Evo malog izvoda iz MSDN-a:
Citat:
Database Server Advantages
The decision to use a client/server solution is driven primarily by two factors: scalability and reliability. If your solution needs to scale to serve more than 25 to 50 users, you should consider using a client/server solution instead of a file-server solution. A file-server database also has inherent reliability limitations because it is maintained as a file in the file system, which can easily become damaged if either the client or server computer (or the connection between them) fails during a transaction or other operation that writes to the database file. By isolating all database files under the control of a database server such as SQL Server, the client/server architecture can provide greater reliability and other advanced features that can't be furnished by the file-server architecture, such as the following:
Online backup
When you are using a database server, you can use an automatic scheduler to back up your database without having to exclude users from the database.
Durable transactions
SQL Server and MSDE log transactions so that updates made within a transaction can always be recovered or rolled back to the last consistent state if either the client or the server computer fails. Although the Microsoft Jet database engine and .mdb files also provide transactions, the transactions in .mdb files aren't managed by a separate transaction log and can fail without recovery if the database file becomes damaged.
Better reliability and data protection
If either a workstation or file server fails while an .mdb file is being written to, the database may be damaged. You can usually recover a damaged database by compacting and repairing the database, but you must have all users close the database before doing so. This rarely happens with a server database such as Microsoft SQL Server or MSDE.
Faster query processing
Using an .mdb file, regardless of where it is located, requires your solution to load the Jet database engine locally to process queries on the client. For large databases, this can involve moving a lot of data over the network. In contrast, SQL Server runs queries on the server, which is typically a much more powerful computer than the client workstations. Running queries on the server increases the load on the server more than would happen with an Access file-server solution, but it can reduce the network traffic substantially—especially if users are selecting a small subset of the data.
Advanced hardware support
Uninterruptible power supplies, hot-swappable disk drives, and multiple processors can all be added to the server with no changes to the client workstations.
Integrated Windows NT security
Both SQL Server and MSDE support using Windows NT® security accounts to authenticate users who are logging on to a database. This means that, unlike security for Access/Jet databases, if users are already logging on to a Windows NT network, you can use their existing Windows NT security groups and accounts to define permissions in your database, as an alternative to creating and maintaining accounts on the database server yourself.
Advanced server-side programming and support for business rules
Microsoft SQL Server and MSDE support a very feature-rich SQL dialect called Transact-SQL. Used in conjunction with features such as constraints and triggers, Transact-SQL allows you to define business and security rules on the server that are enforced equally among all users of the database. You can also use Transact-SQL to create stored procedures that run on your server to provide flexible and secure access to your data from any client.
Ako bi radi sa InterBase-om mozes koristiti knjigu "Delphi/Kylix klijent server programiranje" - Kompjuter biblioteka. Mozda nisam naslov pogodio sto posto :)
Mozes na jednom racunaru simulirati rad u mrezi.
Videcemo za primer...
prelazak na klijent server programiranje
