jim (7/16/2009)

---

Hi Phil, the data source is a table from SQL server rather than from a file system. So, can I still use your script to do it? Thanks a...

ryan213 (7/16/2009)

---

Hey Phil,

Do I need to change anything in that script? I'm pretty sure I followed everything. I created a string variable called SourceFile that contains the location/filename...

Huh? Are you talking about a row-by-row comparison, or something else? What do you mean by binary - are you referring to a checksum?

More detail needed about why you are...

You should not need a script.

Configure a flat file connection, setting the format to 'fixed width' and then set all your start positions and lengths ...

No problem. Just a script task is needed to take the variable containing the file name and do the file copy for you. This would be on the Control Flow,...

Whoa, what is that!? 😀

I'm assuming that 12345 is just dummy data and not some obscure representation of a date (number of days since a blue moon,...

I agree with your findings - it's as if the insert happens and then rolls back, using up a number in the process.

I do not know whether that behaviour can...

Assume that you have a Boolean variable called Test. Here is how you would set it to True using a Script Task.

1) Create a Script Task.

2) Add 'User::Test' (no quotes)...

This should...

Here is how I would do it, I think.

1. Ensure that there is a string variable defined (eg SourceFile) which contains the filepath of the source data (eg C:\Ryan\Output_.xls)

2. Create...

Should not affect that - I assume you are talking about an IDENTITY primary key?

There must be something else happening ... can you post a bit more detail?

Excellent! My pleasure.

You might find this link interesting - goes deeper than you wanted, but should still be informative for you ...

http://blogs.conchango.com/jamiethomson/archive/2006/09/12/SSIS_3A00_-Checking-if-a-row-exists-and-if-it-does_2C00_-has-it-changed.aspx

Phil

There is another (possibly faster) way of doing this which might help in your case.

Try creating a unique index on RealEstateID in your destination table.

CREATE UNIQUE NONCLUSTERED INDEX [IX_RealEstateID]...

You have not explained your problem very clearly.

Can you describe the requirement and post some sample data showing what's it's like as source and how you would like it to...

Your idea number 2 sounds like it should work OK, except you'll need a multicast before you send the output to the log table destination: one output to the log...