David McAfee
davidmcafee at gmail.com
Mon Jun 25 11:17:29 CDT 2012
But that's the thing, what is the thing I should be doing in SSIS that I'm not already doing via TSQL? I have jobs that run every hour, if certain conditions are met/found/not met/not found I am (or other people are) emailed. I have another job that backs up the database on the live server. The file is copied over via a C# program that I have that runs at midnight. I have another job that restores the database on a development server a few minutes later. I guess that would be something that SSIS could handle a little less "rube goldberg-ish" than the way I am currently doing it. But seriously, I have yet to hear of something that SSIS does that I am missing out on. D On Mon, Jun 25, 2012 at 6:11 AM, Robert Stewart <rls at webedb.com> wrote: > SSIS is very powerful. It is generally used as an ETL (Extract, > Transform, and Load) tool. > But, you can also move entire databases with it between servers. You can > run SQL scripts. > Really, you can do just about anything you can do from T-SQL with it. So, > the limitations > are your imagination. > > At 04:07 AM 6/25/2012, you wrote: > >> > I've experienced the same thing. Both as the interviewers and >> > interviewees. >> > >> > I've used SSIS and DTS for import processes. >> > >> > I've been asked if I've used it for anything else. >> > >> > What other reasons are there to use it? >> > >> > There hasn't been a need for me to do something in a different manner. >> > > Robert L. Stewart > www.WeBeDb.com > www.DBGUIDesign.com > www.RLStewartPhotography.com > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/**mailman/listinfo/accessd<http://databaseadvisors.com/mailman/listinfo/accessd> > Website: http://www.databaseadvisors.**com<http://www.databaseadvisors.com> >