You can use Data Synchronisation Studio with Firebird via the ODBC connection provider and the Firebird ODBC Driver.

Ensure you have the Firebird/InterBase ODBC Driver installed and if you have Data Sync 64 bit edition you also have the 64 bit version of the ODBC Driver.

Select the ODBC Driver and enter the connection string to Firebird like this.

DRIVER=Firebird/InterBase(r) driver;UID=SYSDBA;PWD=masterkey;DBNAME=C:\Temp\EMPLOYEE.FDB

Then select the Object in the database or switch to the SQL Tab and enter your own SQL.

Once the Schema Loads you can start defining your Project.

Or just preview the Data to check the connection.

Data Synchronisation Studio has a new feature to make it unbelievably easy to link data by way of Lookup Columns. A column can now link to any other data via a special Lookup column, you could do this with Dynamic Columns before but now it’s just click…click…click.

You can connect SQL Data to SharePoint data for example or Join SQL Data across servers like SQL and Oracle or whatever you get the idea anything to anything.  

To get started connect your data source as before and select the column that represents the Link or Join

Then click the Icon in the Data source Toolbar to Add a Lookup

Once you configure the connection details you need to confirm the Lookup Join details which is essentially the Data Type and Column.

Now once the Lookup loads you will see all the columns from the related Data source listed and you can add any of them to the Schema Map as if they were already in the source.

That’s it really easy lookup columns in Data Synchronisation Studio, this feature is in release 3.0.444

For the Data Sync Exchange Providers to read Calendars,Contacts or Tasks from other mailboxes you will need to add Reviewer permission to the mailboxes for the user that is used in Data Sync. Fortunately you can do this with a PowerShell script like this.

Add-MailboxFolderPermission -Identity ayla@contoso.com:\Contacts -User Ed@contoso.com -AccessRights Reviewer

-Identity is mailbox and folder your targeting and –User is the user to grant access.

This blog article describes how you might synchronise Documents between SharePoint 2007 and SharePoint 2010 with Data Synchronisation Studio including custom Metadata columns whilst preserving the Created and Modified Timestamps and user accounts.

Here we have a Document Library in SharePoint 2007 with a few Documents and a Folder where going to Synchronise this to a new SharePoint 2010 document library.

Here’s the Empty Document Library in SharePoint 2010 which will be the Target

To define the project in Data Synchronisation Studio we need to use the SharePoint provider for SharePoint 2007 and the new SharePoint Client API provider for SharePoint 2010.

Connect Data Source A to the SharePoint Provider

Connect Data Source B to the SharePoint 2010 Client API Provider

Configure the Schema Map like this and add any other meta data columns you also wish to synchronise.

Ensure that the Document Library Update Behaviour is set for FileAndMetaData on each side to that the Documents are uploaded.

Run a Compare A->B and Synchronise the Documents

And now the documents have been synchronised including the Created/Modified Timestamps and User accounts.

As the number of Providers has increased that Data Synchronisation Studio now supports it was getting increasingly harder to locate the provider in the list. Therefore we have now re-worked the Connection Dialog into groups and allowed you to select your own Favourites which are easy to find under the Favourite Tab.

This update is in release 3.0.434

We have created a new Data Synchronisation Studio Provider that allows you to synchronise the Members in a SharePoint Security Group. You may want to use this to keep the Members in sync with Members in an Active Directory Group.

This new Provider is in release 3.0.432 of Data Synchronisation Studio.

Example

Synchronise Members from AD Group to SharePoint Group

Connect Data Source A to Active Directory

In this example we use a LDAP Filter to return only those users of a specific AD group, for example

(&(objectClass=User)(memberOf=CN=SharePoint Team Users,CN=Users,DC=corp,DC=litware,DC=inc))

Connect Data Source B to the Microsoft SharePoint Security Groups provider

Choose the SharePoint Group to synchronise from the dropdown.

Adjust the schema map like this so that the AD Account Name is mapped to Login name and Display Name is mapped to Name. Account Name should be the Key Column.

Your completed project will look like this.

Running a Compare A to B shows the differences and you can now synchronise the member lists.

And now after synchronisation in SharePoint the Group Members is populated.

Now that the users have been correctly added to SharePoint you can also setup a standard SharePoint List sync with the User Information List to populate other meta data from AD into SharePoint.

Now with Ouvvi you can upload and download files into Azure Blob Storage, this is especially useful if you need to backup some files off site such as Database Backup images as part of your automated daily system processes.

Here’s a screenshot of the new Reporting Views were creating for Ouvvi. The view shows Tasks running in Ouvvi, how long they took and their status.

Were working on a refresh of Ouvvi and creating better integration between Data Sync and Ouvvi so that eventually they will become one product together.

The UI has been refreshed with a more modern look and feel.

Opening Data Sync Projects from Ouvvi now integrate with Data Sync and can simply be saved directly back to the Ouvvi Step without having to re-Import.

Changes to Ouvvi Include

• View Queue and Queue Failure Tables
• Re-Submit a Queue Failure back to the processing Queue
• Stop/Abort a Running Instance
• Aborting a Running Instance now injects a ThreadAbortException
• Queue Peek support to prevent multiple instances of the Same Project from the UI
• New REST URL’s to remotely start a Project i.e. http://localhost:4000/Project/Start/10
• Simple Step re-ordering
• Change the Order of Projects on the Project View
• Control the Re-try count per Step
• Control the Failure Mode per Step
• Enable/Disable Steps
• Import/Export Project definitions
• Synchronise Running Threads back to main Project
• Step Handler for SQL Batch
• Support for OleDb, SQLClient and ODBC Data sources in SQL Commands
• Custom Step Handlers are loaded in the Database
• Updated Log Views
• Cross browser support

Were also working on new features as we get ready for Ouvvi 2.0

Were creating report views so you can see statistics about processes running in Ouvvi. Were also working on a solution which will submit log data to the “Ouvvi-Cloud” and allow us to create iPhone/Web Apps so that you can view the status of your running system from outside of your corporate network. (Handy for Remote Support)