About dynamic layers
When you publish a map service to your ArcGIS Server site, you can optionally choose to allow clients of the server, such as the ArcGIS web APIs, to dynamically change layer appearance and behavior in your map service. Determining which layers will appear in a map, layer symbology, layer order and position, labeling, and more, can be achieved on the server through the use of dynamic layers. In this way, dynamic layers can increase the amount of interaction that users are able to have with your maps.
Although the process of enabling dynamic layers is achieved through ArcGIS for Desktop, making use of dynamic layers to change symbology, add layers, and so on, is typically done through code. The ArcGIS web APIs contain documentation on how to consume map services with dynamic layers enabled.
If you want to dynamically add data to your map service, such as feature layers, shapefiles, rasters, or feature attribute tables, you'll need to set up a workspace to contain the data you want to add. Dynamic workspaces can be any enterprise geodatabase, file geodatabase, or file directory on disk that is accessible to the server. If your dynamic workspace is an enterprise geodatabase, you have the option of limiting user access to the geodatabase by locking the database version.
When you select a workspace, an ID is generated to uniquely identify the workspace within the pool of workspaces available to the map service. The map service uses this ID to connect to the data source specified in dynamic layer requests. You have the option to modify the ID when you configure the dynamic workspace for your map service.
Requirements for dynamic layers
The ArcGIS Server account must have at least read access to the dynamic workspaces that contain the data you want to dynamically add to the map service. To learn more about setting share and file permissions on your workspaces when publishing, see Making your data accessible to ArcGIS for Server.
For a full list of dynamic layer requirements and the functionality exposed by dynamic layers in a map service, see Supported functionality in map services.