Using parameters with OledbCommand - Integration Services

In OledbCommand, parameters are indicated by using question marks.

UPDATE PMT_SOLICITACAO
SET APP_STATUS = ?
WHERE APP_UID =  ?

MySQL / Integration Services

How could you use MySQL with Integration Services?

Step1
Download and install a suitable odbc connector to MySQL
http://dev.mysql.com/downloads/connector/odbc/
Be careful with the version.
If your version is 5.1.5, like mine you should download the odbc connector from here http://downloads.mysql.com/archives.php?p=mysql-connector-odbc-5.1&v=5.1.5

Step2
Create a datasource.

Step3
With datasource created, go back do Integration Services and chose DataRead component.

Step4
Drop the DataReader on the Data Flow and chose one of the connections of connection manager.

You're done. You're ready to work with MySQL data.

Integration Serivces x Sybase

Well, I didn't want to say that, but the interaction between integration services and Sybase is not good at all.

The version of my Sybase Database

Adaptive Server Enterprise/12.5.4/EBF 15444 ESD#8/P/ia64/HP-UX B.11.23/ase1254/2105/64-bit/OPT/Mon Mar 24 04:38:00 2008

Example:

When you try to preview a OLEDB Source configured with a Sybase Data Source, the following message appears.

If you try to click OK anyway, you're gonna receive another message

Is there a solution to this problem? No.

Sybase, at least the version I am working with, and when it comes to Data Flow Task, is completely incompatible with SQL Integration Server.

There are other tasks, those who don't need column mapping, that can work with Sybase. But the the great breakthrough of using Integration Services is exactly that, the column mapping to perform transformations without the need of code programming.

Conclusion: the use of Integration Services with Sybase is very limited.

Há!

: (

Integration Services - Sincronização entre duas tabelas de diferentes bancos de dados.

Veja bem,

Se você está tarado para usar o replicatedo SQLServer para sincronizar duas tabelas de bancos diferentes, controle-se!

Ao invés disso, utilize o integration service, é bem mais elegante. Usar replicate para sincronizar tabelas de bases diferentes é o mesmo que assassinar uma mosca usando um asteróide.

Ao invés disso, veja este exemplo

There are situations where a SQL Server DBA needs to keep two different tables in sync. Usually, the DBA needs to keep a copy of a table in a in a data warehouse repository that is used as a solution for archiving and/or reporting.

SQL Server provides a robust method for keeping data synchronized across databases using Replication but there are situations when all we need is just to keep an online copy of a single table for archiving or reporting purposes and we would prefer to do not tinker into SQL Server replication.

This post is divided into two parts: Part I explains how to update a destination table with the information that is added into a source table while Part II explains how to replicate any change that happens in existing records in the source table into destination. Please, take into account this is just another way of doing this, there are many other possibilities but the one listed here is probably one of the fastest to implement and modify on-demand.

This procedure is based on the following scenario: A “table A” on “database A” is periodically replicated using SSIS into “table B” on “database B”. “Table A” is updated with new records and we need to copy those records into “table B” too. Our final implementation will look like this in SQL Server Business Intelligence Development Studio:

http://blogs.msdn.com/b/jorgepc/archive/2010/12/07/synchronize-two-tables-using-sql-server-integration-services-ssis-part-i-of-ii.aspx

That's folks!