Open Linking and Embedding Database (OLEDB) is a set of COM-based interfaces that expose data from a variety of sources. They provide applications with uniform access to data stored in diverse information sources, or data stores. These interfaces support the amount of DBMS functionality appropriate to the data store, enabling the data store to share its data.
To Connect to OLEDB, set the Server and Database Properties. Additionally, set the provider and Integrated Security Property.
|Provider||Set this to SQLOLEDB.|
|Data Source||Set this to the Hostname of the server.|
|Initial Catalog||Set this to the DatabaseName.|
|Integrated Security||Set this to authenticate with Using Windows authentication.|
Set the ‘Provider’ parameter to “sqloledb”.
Set the ‘Data Source’ to the address to your database’s server. Since using a local network server to test this tutorial. I place the server name and instance name, separated by a backslash.
Set the ‘Initial Catalog’ parameter to the name of your database.
Set the Integrated Security to SSPI to authenticate your connection string to use windows authentication. SSPI is the OLEDB compatible way of setting integrated security to true.
To Check for the data migrations:
Add a new connection in data governor as shown.
Using the connection string parameters created (You can Specify the Username and password either in the connection string or in the box Shown Below), Verify the connection using the VERIFY CONNECTION Option in Data Governor. Once the Connection is verified, Insert the Connection Using Insert Option.
Create a Job Using ADD A JOB option in data governor, add a data migration task to the job.
Create a New Task by right clicking job list and then Add a New Task Option. If you want to edit an Existing Task Use Edit Task.
Choose a Data Migration Task.
Choose the source and the destination for the migration of data. Name the Task.
Choose the Tables or the data that need to be migrated from the source to the destination. You can Copy all Tables by checking Copy all tables box.
Execute the Job. Check for results and the details of the data migrated in Execution History.