Can you be more specific?

You are using SSIS right? What are you trying to accomplish?

I believe it is worth taking a look at the following URL:

http://msdn.microsoft.com/en-us/library/aa259187(SQL.80).aspx

Look at the section explaining...

You are combining two different filters at once in the conditional split.

1. Are the values different?

2. Is the value null?

Since you nested filter 1 into filter 2, filter 1 doesn't...

The OLE DB Command doesn't work that way.

It is fired for every row in the dataflow. So, the update statement of the last row will determine what is updated.

Instead, it...

According to this issue on Connect, SSIS indeed truncates the milliseconds:

https://connect.microsoft.com/SQLServer/feedback/details/351786/ssis-datetime-variable-precision?wa=wsignin1.0

If you are handy with T-SQL, you can create a loop over some dynamic T-SQL that will accomplish the same thing.

Relax. The week is almost in the middle. It is almost weekend 🙂

Is there a question?

Please see the link in my signature and reformulate your question. Help us to help you.

Nice question. I got it right because I just checked what rights I have on the development server and what rights I have on the production server.

I believe the most elegant way is the following:

use a task first to check if the necessary file is present (this can be a script task or whatever).

Store the result...

You can only use SQL Server Destination if the destination is on the same server.

This BOl article explains why:

http://msdn.microsoft.com/en-us/library/ms141095.aspx

I can't immediately find the "error" either.

But what are you trying to accomplish?

Or you trying to format a string to another string that looks like a date, or are you...

I have to agree with Brandie.

Scripting isn't really necessary to solve this problem. SSIS (or T-SQL) offers enough elegant possibilities to handle this.

You can use the IDENTITY property as said...

As you said, SSIS can't provide the documentation you need out of the box.

You can check out BI documentor, but I haven't found real evidence on their site that it...

Oh yeah I forgot: great question! 😀

Option 1 isn't that reliable. For really really large tables (e.g. number of records > 2^31-1) it will produce an error. To be 100% sure, COUNT_BIG should have been used.