SSDT Hangs

  • I'm setting up a simple file system task to copy a file, I was hoping to use variables to hold
    1) File path
    2) Filepath and name od exiting file
    2) File path and name of file to be created

    so for example my file to be created variable is being set in the variables pane as filepath + "Filename.csv"

    This process hangs for minutes - tens of minutes. I have treid it on to differant machines - same problem - si there something I am doing wrong?

    I haven't even gotten to adding the file system task!

    Thanks

  • Adam Sandler - Thursday, April 6, 2017 9:10 AM

    I'm setting up a simple file system task to copy a file, I was hoping to use variables to hold
    1) File path
    2) Filepath and name od exiting file
    2) File path and name of file to be created

    so for example my file to be created variable is being set in the variables pane as filepath + "Filename.csv"

    This process hangs for minutes - tens of minutes. I have treid it on to differant machines - same problem - si there something I am doing wrong?

    I haven't even gotten to adding the file system task!

    Thanks

    What is it doing when it hangs?

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • Well for instance now - ive successfully set up the variables. Trying to drag the task onto the control tab - its hangs = not responding in title bar.

    Only seems to have started since I started with setting up expression based variables? Have done lots of packages before on either machine? Thanks

  • Adam Sandler - Thursday, April 6, 2017 9:28 AM

    Well for instance now - ive successfully set up the variables. Trying to drag the task onto the control tab - its hangs = not responding in title bar.

    Only seems to have started since I started with setting up expression based variables? Have done lots of packages before on either machine? Thanks

    Ah, you mean you're in design mode and it's hanging?
    I have no idea then. I use variables with expressions all the time and do not experience problems like this.
    What happens to CPU/RAM/Disk while the process is hanging?

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • Task manager has it at 8 , 35% , 2%
    L

    in my expression do I set it as @variable to be set = "Value" or just "Value" - it certainly seems to be something to do with my expressions - works ok othewrise?g

  • Adam Sandler - Thursday, April 6, 2017 10:03 AM

    Task manager has it at 8 , 35% , 2%
    L

    in my expression do I set it as @variable to be set = "Value" or just "Value" - it certainly seems to be something to do with my expressions - works ok othewrise?g

    Just value. Here is one I use to get file type, for example:

    UPPER(TOKEN( @[User::FullSourceFilePath] , ".", TOKENCOUNT( @[User::FullSourceFilePath] , ".") ))

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • Thanks Phil - that seems to have solved it - I had @variable =  , whereas I now have just the value , and its working fine now.

    Interestingly with @Variable =  its still set the value, didnt "error" - just hung for ages! - If you have a spare 30 minutes - give it a go!

    Thanks very much for your help - muich appreciated.

  • Thanks for posting back & glad you got it working.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

Viewing 8 posts - 1 through 7 (of 7 total)

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