David McAfee
davidmcafee at gmail.com
Mon Jun 25 16:37:30 CDT 2012
Arthur, I do understand the ETL part of SSIS. The thing is I've been asked is if I've used SSIS for anything else besides ETL. What else is there? D On Mon, Jun 25, 2012 at 2:16 PM, Arthur Fuller <fuller.artful at gmail.com>wrote: > David, > > Scheduled jobs and backup/restores are easy in T-SQL, and even easier in > SMO. But that's hardly the point. > > As Robert said, a major strength of SSIS is ETL (Extract, Load, Transform). > That kind of job is made so much easier with SSIS that I couldn't even > imagine writing the T-SQL I'd need to accomplish the same thing. A couple > of example should suffice: > > 1. Suck in a flat file that originated on a mainframe, examine it row by > row, and then insert parts of each row into different tables (Customers, > Orders, OrderItems) depending on what's found in the particular row. > 2. Map an Oracle database to a SQL Server database, where the tables barely > match and the column names may differ significantly. Add to that such > niceties as one database is in 3NF and the other is in BCNF. > > Yeah, one could write the T-SQL to do both of these jobs, but no thanks. > I'd rather use a GUI designed for such tasks, with decision trees, visual > column-mapping, and other neat tools. > > Arthur > > On Mon, Jun 25, 2012 at 12:17 PM, David McAfee <davidmcafee at gmail.com > >wrote: > > > But that's the thing, what is the thing I should be doing in SSIS that > I'm > > not already doing via TSQL? > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >