Really Bizzare Flat File Destination issue

Question

Really Bizzare Flat File Destination issue

Viewing 7 posts - 16 through 21 (of 21 total)

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

Lowell SSC Guru Points: 323518 More actions · Answer 1

is your file name you are writing to dynamic? Did you modify your flat file destination to have an expression that points to what the dynamic file name should be?
Iif that is all set, are you sure your ForEach Loop is assigning variables?
It's fairy easy to miss a connection like that, so the dataflow loops through the same file over and over, but doesn't write to teh file, but points at a model document instead.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Steven.Grzybowski Hall of Fame Points: 3214 More actions · Answer 2

Lowell - Monday, January 23, 2017 2:28 PM
is your file name you are writing to dynamic? Did you modify your flat file destination to have an expression that points to what the dynamic file name should be?
Iif that is all set, are you sure your ForEach Loop is assigning variables?
It's fairy easy to miss a connection like that, so the dataflow loops through the same file over and over, but doesn't write to teh file, but points at a model document instead.

The expression in the connection manager is set to point at the dynamic file name. When I run it from my workstation, it works. I just doesn't work WHEN I run it on the server or a coworker's machine.

Phil Parkin SSC Guru Points: 246962 More actions · Answer 3

Steven.Grzybowski - Monday, January 23, 2017 2:32 PM
Lowell - Monday, January 23, 2017 2:28 PM
is your file name you are writing to dynamic? Did you modify your flat file destination to have an expression that points to what the dynamic file name should be?
Iif that is all set, are you sure your ForEach Loop is assigning variables?
It's fairy easy to miss a connection like that, so the dataflow loops through the same file over and over, but doesn't write to teh file, but points at a model document instead.
The expression in the connection manager is set to point at the dynamic file name. When I run it from my workstation, it works. I just doesn't work WHEN I run it on the server or a coworker's machine.

Can I suggest an alternative pattern? Try leaving the file name static and adding a subsequent task which does the rename.

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

Steven.Grzybowski Hall of Fame Points: 3214 More actions · Answer 4

Phil Parkin - Monday, January 23, 2017 3:13 PM
Steven.Grzybowski - Monday, January 23, 2017 2:32 PM
Lowell - Monday, January 23, 2017 2:28 PM
is your file name you are writing to dynamic? Did you modify your flat file destination to have an expression that points to what the dynamic file name should be?
Iif that is all set, are you sure your ForEach Loop is assigning variables?
It's fairy easy to miss a connection like that, so the dataflow loops through the same file over and over, but doesn't write to teh file, but points at a model document instead.
The expression in the connection manager is set to point at the dynamic file name. When I run it from my workstation, it works. I just doesn't work WHEN I run it on the server or a coworker's machine.
Can I suggest an alternative pattern? Try leaving the file name static and adding a subsequent task which does the rename.

Just tried that, and when I export it to a static filename and then copy the file to a new file with the MMDDYY appended to the end, the MMDDYY file ends up being empty.

Phil Parkin SSC Guru Points: 246962 More actions · Answer 5

Steven.Grzybowski - Tuesday, January 24, 2017 3:38 PM
Phil Parkin - Monday, January 23, 2017 3:13 PM
Steven.Grzybowski - Monday, January 23, 2017 2:32 PM
Lowell - Monday, January 23, 2017 2:28 PM
is your file name you are writing to dynamic? Did you modify your flat file destination to have an expression that points to what the dynamic file name should be?
Iif that is all set, are you sure your ForEach Loop is assigning variables?
It's fairy easy to miss a connection like that, so the dataflow loops through the same file over and over, but doesn't write to teh file, but points at a model document instead.
The expression in the connection manager is set to point at the dynamic file name. When I run it from my workstation, it works. I just doesn't work WHEN I run it on the server or a coworker's machine.
Can I suggest an alternative pattern? Try leaving the file name static and adding a subsequent task which does the rename.
Just tried that, and when I export it to a static filename and then copy the file to a new file with the MMDDYY appended to the end, the MMDDYY file ends up being empty.

Are you saying that your copy process somehow removes the file's contents? Please tell me how you are doing that.

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

Steven.Grzybowski Hall of Fame Points: 3214 More actions · Answer 6

Phil Parkin - Wednesday, January 25, 2017 7:21 AM
Steven.Grzybowski - Tuesday, January 24, 2017 3:38 PM
Phil Parkin - Monday, January 23, 2017 3:13 PM
Steven.Grzybowski - Monday, January 23, 2017 2:32 PM
Lowell - Monday, January 23, 2017 2:28 PM
is your file name you are writing to dynamic? Did you modify your flat file destination to have an expression that points to what the dynamic file name should be?
Iif that is all set, are you sure your ForEach Loop is assigning variables?
It's fairy easy to miss a connection like that, so the dataflow loops through the same file over and over, but doesn't write to teh file, but points at a model document instead.
The expression in the connection manager is set to point at the dynamic file name. When I run it from my workstation, it works. I just doesn't work WHEN I run it on the server or a coworker's machine.
Can I suggest an alternative pattern? Try leaving the file name static and adding a subsequent task which does the rename.
Just tried that, and when I export it to a static filename and then copy the file to a new file with the MMDDYY appended to the end, the MMDDYY file ends up being empty.
Are you saying that your copy process somehow removes the file's contents? Please tell me how you are doing that.

I am using a file system task with a variable destination path and a non-variable source path. The source path is my new static filename, and the the operation is copy file.

Phil Parkin SSC Guru Points: 246962 More actions · Answer 7

Steven.Grzybowski - Wednesday, January 25, 2017 7:31 AM
I am using a file system task with a variable destination path and a non-variable source path. The source path is my new static filename, and the the operation is copy file.

Are you using UNC file paths? Are you certain that the hardcoded source path points to a file which contains data? If you change the destination to be in the same folder as the source, is the outcome the same? (Trying to rule out permissions issues.)

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