Post reply

Problem setting global variables when executing dts package

  • June 1, 2006 at 3:39 am

    #168663

    Hi

    I have a dts package which has some global variables so I configure the connections to 2 databases using dynamic properties task.  I have set up a job using cmd prompt to execute the dts package through dtsrun utility.  I am setting the global variables in dtsrun but the dtspackage will not use them it still runs the package on the database set in the package.  Can anyone shed any light on why it is not changing the global variables??

    Thanks

  • June 1, 2006 at 6:42 am

    #641154

    Perhaps it's a syntax issue, are there any errors being reported?  Have you turned on logging on the package itself and also if you're calling it from the cmd line you can output what would normally be echoed back to you by using something like 

    >>c:\test.txt

    That what you can see if there are any errors at that point as well.

    Can you post the syntax you are using?

    thanks.

    -Luke.

    To help us help you read this[/url]For better help with performance problems please read this[/url]

  • June 1, 2006 at 9:37 am

    #641219

    I am running the following command in the SQL Jobstep using the CmdExec as the type. 

    dtsrun.exe /S aqu_lhcit_mis03  /U user /P password /N dw_geneva_Helpdesk /A ServerName:8=AQU_LHCIT_MIS03 /A DatabaseName:8=GenevaPhilipsDW /A Debug:11=-1 /A StagingDB:8=GenevaPhilips /A ParentPackage:8=n/a /A Package:8=dw_geneva_Helpdesk /A FullReload:11=0

    The package doesnt fail as it is running it on another database which uses the same package to update the data warehouse so I dont get an error, but I need it to set the global variables to the values Im passing so it runs it on the correct database for this job. I have checked permissions and this is all ok.

    Thanks

  • June 1, 2006 at 10:50 pm

    #641355

    If you are using DataPump task, then you need to use global variables for each datapump task to modify SourceObjectName and/or DestinationObjectName, whichever you need. They hold the value set at design time in [DB].[DBO].[TableName] format. When you pass Sever/database in global variables for your conncetion, the datapump still keeps the old values.

    I used VB script task to first generate the property value in [DB].[DBO].[Tablename] format and set global variables. Then the Dynamic Properties task assigns those variables to datapump tasks.

    Thanks,

     

  • June 2, 2006 at 3:53 pm

    #641536

    One of the possible reason could be the global variable names.  These are case sensitive so if not defined correctly in DTSRun command, it uses from the last execution of package.  I had a similar problem which was solved by change variable names to match the ones defined in package

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

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