Post reply

Regarding Record set destination and for each loop container Task to SQL task

  • July 25, 2011 at 1:09 am

    #254333

    Hello Every one.

    I have a ssis packge with a dataflow task followed by a foreach loop container.

    dataflow task is extracting some varibles from a ado.net source and storing it in record set destination. Then for each loop container is processing those records using ADO.net enumerator. and the whole task is scheduled to run everyday. Now i want to convert this task as SQL job. How can i do that. Please help me out?

  • July 25, 2011 at 4:01 am

    #1357662

    So in short you want to schedule a SSIS package as part of SQL Agent job ?

    Assuming the package was created on a different machine from which it needs to be scheduled on.

    You need to first package and deploy the SSIS using a deployment manifest ? If you need help with that look up

    http://msdn.microsoft.com/en-us/library/ms140117.aspx

    once the package is deployed then under the sql server agent , right click the Jobs folder and select new job, type a name , then click the steps menu option on the left and click new . In the drop down for type select "Sql server integration services package " and then fill in the required details in the boxes below , ( you should have this from the time you performed the deployment) . Then move to Schedules on the left and fill in the requried schedule information and your good to go.

    Jayanth Kurup[/url]

  • July 25, 2011 at 9:51 am

    #1357904

    thanks for the reply..

    i want to convert the whole ssis package into sql. i do not want to use ssis packge again. i want to convert into sql and schedule the same on everyday. thanks

  • July 25, 2011 at 1:58 pm

    #1358126

    I don't think you will find a tool to do this for you - you will just have to re-write the functionality of the package in T-SQL manually & the schedule it in a job.

  • July 25, 2011 at 2:03 pm

    #1358130

    SinisterPenguin (7/25/2011)

    I don't think you will find a tool to do this for you - you will just have to re-write the functionality of the package in T-SQL manually & the schedule it in a job.

    I agree - there is no conversion tool. Some of the stuff SSIS does cannot even be achieved in T-SQL. You've got a manual job ahead of you and might need to change the way that the problem is solved to accommodate the differences between the environments you're working in.

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • July 25, 2011 at 9:41 pm

    #1358230

    Thank you all for the replies.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply