Export logic from integration services to stored procedures - 10-09-2007 , 11:16 AM
I'm involved in a project working in a SQL Environment, let's call it
SQLDB. We have to integrate in a single database data extracted from
two different sources: Source1 and Source2.
We don't have direct access to manage the execution environment and we
have been told that we cannot use Integration Services to transform
the data extracted from Source1 and Source2. This is something we have
to deal with, a fact, it's an assumption we cannot change.
Because of this fact we will have to create our own Stored Procedures
directly, and export them to SQLDB.
Would it be possible/feasible/convenient to use Integration Services
as our development tool for the transformations? I think it would be
really useful to use the facilities of Integration Services in order
to transform data and later export this code to store procedures that
we could import in SQLDB. Is this possible?
Thanks a lot
RE: Export logic from integration services to stored procedures - 10-09-2007 , 02:41 PM
I really don't think that you can take a completed SSIS package and
reverse-engineer it into a T-SQL stored procedure. True that SSIS files are
saved in xml format, but the whole CONCEPT of SSIS is so different from
stored procedures that it jsut wouldn't work.
SSIS works on Control Flow/Data Flow, and 'pipeline' based analogies. But
stroed procedures are typically set-based operations (unless you make
extensive use of staging tables, etc).
If someone has heard othersise, please post so here, but I have never heard
of such a process or tool.
[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]
"david.leiva (AT) gmail (DOT) com" wrote:
Re: Export logic from integration services to stored procedures - 10-09-2007 , 04:15 PM
Hello david.leiva (AT) gmail (DOT) com,
I'll second the "no" here with a tangent. SSIS and SQL scripts are very different
things -- Unless you can use SQLCLR for your stored procs and that might
just be asking for way too much trouble.
That, SSIS might be okay as a planning/prototype tool and to help you discover
the conversion issues you'll have to face. Helpful, but understand that there
is lot of T-SQL to write after the fact.
Re: Export logic from integration services to stored procedures - 10-10-2007 , 02:16 AM
On 9 oct, 23:15, Kent Tegels <kteg... (AT) develop (DOT) com> wrote: