Database Connections (Synchronization Services)
Microsoft Synchronization Services for ADO.NET makes at least two connections during synchronization: one to the client and one to the server. Additional connections are required in N-tier and service-based architectures. Synchronization Services makes these connections by using ADO.NET. Be aware of the following behavior:
For performance reasons, the DbServerSyncProvider uses ADO.NET connection pooling. Connection pooling can retain a physical connection to a SQL Server database even if synchronization is not running. Typically, this is not an issue. However, if you must drop the physical connection, call ClearPool.
Connection strings that are passed to DbServerSyncProvider must always include the name of the database from which tables will be synchronized, as shown in the following example:
Data Source=localhost; Initial Catalog=AdventureWorks; Integrated Security=True;
For information about how to secure connections, see Security Considerations (Synchronization Services).