# Differences between running Derby in embedded mode and using the Network Server

This section describes the differences between running Derby in embedded mode and using the Network Server.

See "Configuring Network Server authentication in special circumstances" in the Derby Security Guide for information about authentication that is specific to the Network Server.

Note: There may be undocumented differences that have not yet been identified.

- Differences between the embedded client and the network client driver
  The following are known differences that exist between the Derby embedded driver and the network client driver.
- Updatable result sets
  In Derby, the functionality of updatable result sets in a server environment and in an embedded environment are similar, with the exception of the following differences.
- Differences in JDBC methods
  A few JDBC methods behave differently with the embedded driver from the way they behave with the client driver.
- Differences using the Connection.setReadOnly method
  In embedded mode, when the Connection.setReadOnly method has true as the parameter, the connection is marked as a read-only connection. When you use the Network Server, the Connection.setReadOnly(true) method is ignored, and the connection is not marked as a read-only connection.

Parent topic: Using the Network Server with preexisting Derby applications
Related concepts
The Network Server and Java Virtual Machines (JVMs)
Accessing the Network Server by using the network client driver
Accessing the Network Server by using a DataSource object
XA and the Network Server
Using the Derby tools with the Network Server
Related tasks
Installing required jar files and adding them to the classpath/modulepath
Starting the Network Server
Shutting down the Network Server
Obtaining system information
Setting port numbers