SSIS Package to Script All SQL Server Jobs to Individual Files

  • Comments posted to this topic are about the item SSIS Package to Script All SQL Server Jobs to Individual Files

  • Great article, unfortunately when I try to use the package on a SQL 2005 server I get a message indicating the package is a higher version than installed. Is there a SQL 2005 version of the package available?

    Ian.

  • I have attached the SQL Server 2005 version just remove the txt file extensions. Let me know if you have any issues. This version will only work on SQL Server 2000 and 2005 jobs with the package run from a SQL Server 2005 installed PC.

  • Thanks that seems to work with SQL 2005 now.

    Ian

  • Nice. Thanks for sharing!

  • Question I have downloaded both the files removed the .txt extension, but still I am not sure what to do. Can you please tell me the step by step process.

  • To use the scriptJobs2005.dtsx file you will need to have SQL Server 2005 installed with BIDS (SQL Server Business Intelligence Development Studio) and the SDKs (the folder C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies should many ddls in it). Then put the ScriptJobs.dtsconfig file in C:\temp. Then edit the ScriptJobs.dtsconfig file so that the server name is correct where the "########" is below. Then right click on scriptJobs2005.dtsx in windows explorer and click open. This will open the execute package Utility in which you will click execute. Then after it finishes, the sql files for each job will be in the C:\MyJobs folder. I am assuming the you have access to the SQL Server via your network password using integrated security.

    <?xml version="1.0"?>

    <DTSConfiguration>

    <DTSConfigurationHeading>

    <DTSConfigurationFileInfo GeneratedBy="xxxx" GeneratedFromPackageName="ScriptJobs" GeneratedFromPackageID="{BE7E98AD-FC33-4C70-BB2B-B081DBBB6B97}" GeneratedDate="6/10/2010 3:47:27 PM"/>

    </DTSConfigurationHeading>

    <Configuration ConfiguredType="Property" Path="\Package.Variables[User::varFilePath].Properties[Value]" ValueType="String">

    <ConfiguredValue>C:\MyJobs</ConfiguredValue>

    </Configuration>

    <Configuration ConfiguredType="Property" Path="\Package.Variables[User::varServerName].Properties[Value]" ValueType="String">

    <ConfiguredValue>########</ConfiguredValue>

    </Configuration>

    </DTSConfiguration>

  • Thanks you so much it worked.

  • Although I have sql2005 with SP3 and ssis and sdk installed, I receive "Error the task "script task" cannot run on this edition of integration services. it requires a higher level edition. Any ideas what I might be missing?

  • Please check SSC Vetran's reply it has two file in it.

  • I have figured out the how to change MYJOB folder. But can you please tell me how can I change TEMP folder location where you keep ScriptJobs.dtsconfig

  • Turns out that I can run from the server, just not from my desktop. Script is great and very useful. Thanks.

  • salman788 (7/6/2010)


    I have figured out the how to change MYJOB folder. But can you please tell me how can I change TEMP folder location where you keep ScriptJobs.dtsconfig

    You would need to open the package in the BIDS(SQL Server Business Intelligence Development Studio) and change it. Just select "SQL Server Business Intelligence Development Studio" from the SQL Server menu and create a new integration service project name it anything you like and right click on the SSIS Package and click on add existing package. From Add copy of existing package dialog box select file system from the Package Location drop-down and navigate to where you saved the package. Once added to the project open the package and right click in an open space on the design interface. Then select "Package Configuration" and remove the existing file and add a new one in any location you want. Add the two variable values to the configuration file. Save the SSIS package and retrieve the new package from the location in the project and it will run with the new configuration file.

  • kimetch (7/6/2010)


    Although I have sql2005 with SP3 and ssis and sdk installed, I receive "Error the task "script task" cannot run on this edition of integration services. it requires a higher level edition. Any ideas what I might be missing?

    Retrieve ScriptJobs2005.dtsx package and config file from my earlier post. If that does not work make sure you have BIDS and SDKs installed.

  • I have a script that runs in a Powershell script step of a SQL Agent job to do this.

    Makes deployment pretty easy as it's just T-SQL to create the SQL Agent job

    --------------------
    Colt 45 - the original point and click interface

Viewing 15 posts - 1 through 15 (of 36 total)

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