Share via

Database Connections (Sync Services)

  • Article

Sync Services for ADO.NET 2.0 makes at least two connections during synchronization: to the client and server, or to the two peers. Additional connections are required in N-tier and service-based architectures. Sync Services makes these connections by using ADO.NET. Be aware of the following behavior:

  • For performance reasons, the DbServerSyncProvider and DbSyncProvider use 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 or DbSyncProvider 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 (Sync Services).

See Also

Concepts

Considerations for Application Design and Deployment (Sync Services)