One of the more useful technologies introduced by Microsoft with Visual Studio 2008 leverages the work done by the ADO.NET team. Synchronization Services is at the core of this enhancement and coupled with the new Data Cache class, distributed applications can now generate both the code and client-side databases to implement half-duplex or fully bi-directional synchronization. This provides architects with an entirely new way to distribute data to multiple clients that are only "occasionally" connected without compromising data security or server performance.
By the end of the class students will discover:
- What's new with ADO.NET Synchronization Services and why is this innovation important?
- How do replicated application designs differ from client/server or other multi-user architectures?
- How are both the client and server-side synchronization code components created?
- How can application architects and developers build-in concurrency into their designs?
- How can locally cached data improve application performance and increase data viability?
- What additional code or infrastructure must be added to implement full bi-directional synchronization?
Understanding Replication Architectures
- What replication options are available?
- How are these multi-user approaches different from connected systems?
- How is concurrency managed in replication architectures?
- How can collisions be avoided in the first place?
Understanding How Sync Services Leverages the SQL Server Compact Edition
- How to choose what to replicate and what to fetch using conventional queries.
- How the cached data stored and protected.
- How to trigger synchronization
- What types of synchronization are available
Understanding How to Implement Bidirectional Synchronization
- Choosing between static and incremental synchronization
- Making changes to the host Publisher database with SQL Server 2005
- Making changes to the host Publisher database with SQL Server 2008
- Handling replication collisions