SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSIS vs SSMS !


SSIS vs SSMS !

Author
Message
Sim-473257
Sim-473257
SSC Rookie
SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)

Group: General Forum Members
Points: 32 Visits: 126
Here's a more theoretical question for you, to make change from all that hard code stuff.

It all started when someone ( a 'user') asked me what SSIS was.
So it was that I sat down and tried to explain some basics about what SQL Server was, how it worked etc.
Ultimately, I come to a slide to explain SSMS, and a slide to explain SSIS.

It is then that I realized that when in early development, I do often pull data into my DB with T-SQL and a linked server, or a bulk_insert.
So why do I need SSIS again ?
Ah yes, meta-data, wizards, auditing, logging, neat packages that simply be thrown at my scheduling utility.
And of course, I don't have to stop and think too much about 'how' I pull data across different servers and mash them all together without taking 24 hours to run ... it's all worked out for me.

So SSIS 'helps' me a lot .. but I could, in theory, do it all with views and T-SQL.
I think.

Thus it was that I found myself typing this little line :
“There is nothing that a dedicated ETL Tool can do, that cannot be done via SSMS”

I of course followed this up with:
"One is just a hell of a lot easier than the other for specific tasks".

But it's left me with a churning mind.
If we ignore that fact that to perform some ETL tasks in SSMS with pure T-SQL, would be a hell of a lot of coding, and setting up of support procedures, log tables etc ...
... we could do everything that SSIS does, ourselves, right ?

I'd love to hear comments on this.
Have I missed something obvious ?
Orlando Colamatteo
Orlando Colamatteo
SSChampion
SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)

Group: General Forum Members
Points: 14853 Visits: 14396
There are some things included in SSIS that it would be foolish to re-implement in T-SQL. However, if you consider the Windows Batch commands that can be issued via xp_cmdshell and the .NET code that can be implemented in SQLCLR modules part of T-SQL, and you overlook some aspects of securing SQL Server with respect to enabling those features in your instance then yes, you can do everything in T-SQL that you can do in SSIS.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Koen Verbeeck
Koen Verbeeck
One Orange Chip
One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)

Group: General Forum Members
Points: 27161 Visits: 13268
Jeff Moden - a TSQL guru on this site - swears by TSQL (and thus SSMS) and never uses SSIS for anything.

Reading text files --> bcp or bulk insert
Reading Excel --> OPENROWSET

And so on.

The biggest issue probably is security issues, as opc.three has pointed out.
But also row level error handling - which you can do easily in the SSIS dataflow - is problematic in TSQL. It requires a cursor, which will slow things down tremendously.

So, everything is possible in TSQL, but it will sometimes be harder and/or much slower.
Sometimes TSQL will be easier and much quicker (for example sorting, grouping and joining relational data).


How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?
My blog at SQLKover.

MCSE Business Intelligence - Microsoft Data Platform MVP
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search