Why is Microsoft Sync Framework part of the SQL Server Install (and why should I care)?

  • I am installing SQL Server 2008 R2 Enterprise for a production server, and I am trying to eliminate all features that I don't need.

    One of the features listed in the Feature Selection window is the Microsoft Sync Framework.

    What is this, and why would I want it on my database server? Do any SQL Server features depend on it? What happens if I don't install it? Does my Microsoft stock decline in value??? :w00t:

  • Microsoft Sync Framework is a comprehensive synchronization platform that enables collaboration and offline access for applications, services, and devices. It features technologies and tools that enable roaming, sharing, and taking data offline. By using Sync Framework, developers can build sync ecosystems that integrate any application with any data from any store that uses any protocol over any network.

    Sync Framework consists of the following technologies, the first three of which can be installed with SQL Server 2008:

    •Sync Services for ADO.NET can be used to synchronize databases for offline and collaborative scenarios.

    •Sync Framework core components can be used by Sync Services for ADO.NET to synchronize databases, and can also be used to create synchronization providers for other types of data stores.

    •Sync Services for FeedSync can be used to synchronize RSS and Atom feeds with data in a local store.

    •Sync Services for File Systems can be used to synchronize files and folders in a file system.

    •Metadata Storage Service can be used to store synchronization metadata in SQL Server Compact 3.5.

    For More:

    http://msdn.microsoft.com/en-us/library/cc281959.aspx

  • I do appreciate the information, but that sounds an awful lot like a marketing spiel! 🙂 I mean, it sounds great, but what does it actually mean?

    It sort of sounds like a development tool. Something to go along with the various SDK's that you can also install as a part of the SQL Server Features. If that is true, then I wonder why you would install it on a production server.

    I was wondering if it was necessary for some other feature - like, "Oh, you need this to enable Policy-Based Management on a Cluster," or "You have to have this if you want to do remote management using Powershell."

    It actually sounds as though it doesn't really do anything - unless you create an application that somehow leverages it. Perhaps it is required for some 3rd party tools. Does anyone know of anything like that?

    The reason I ask is this - I don't want to install anything on a production server unless it is needed. I am not installing Business Intelligence Development Studio, Books Online or any of the SDK's on this server. So, why would I install this feature?

    I was also curious as to what one might do with it. Has anyone developed anything against this framework?

  • Who is this who darkens understanding with his counsel? May Codd rebuke you!:angry:

  • By using Sync Framework, developers can build sync ecosystems that integrate any application with any data from any store that uses any protocol over any network.

    However it's something like API given to DEV team for application builing I do believe SQL Server uses the same for it's SYNC up with other RDBMS.

  • Dev (12/1/2011)


    By using Sync Framework, developers can build sync ecosystems that integrate any application with any data from any store that uses any protocol over any network.

    However it's something like API given to DEV team for application builing I do believe SQL Server uses the same for it's SYNC up with other RDBMS.

    So, is it required in order to connect SQL Server to an Oracle database? If not, then what can I build with it that is better than the out-of-the-box functionality?

    It sounds interesting.

  • David Moutray (12/1/2011)


    Dev (12/1/2011)


    By using Sync Framework, developers can build sync ecosystems that integrate any application with any data from any store that uses any protocol over any network.

    However it's something like API given to DEV team for application builing I do believe SQL Server uses the same for it's SYNC up with other RDBMS.

    So, is it required in order to connect SQL Server to an Oracle database? If not, then what can I build with it that is better than the out-of-the-box functionality?

    It sounds interesting.

    To be honest, I am not sure. My previous comment was based on general observations.

    Just try it out & let everybody know.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply