Even negatives can be coded in a positive way, to help avoid possible double-negative mistakes.

Rather than 'IsInactive', I'd use 'IsDead' or similar.

I also recommend SQL Compare, though if your databases are developed using VS DB projects, there is a Schema Compare tool built in.

Check the mappings on your OLEDB destination.

Each of the derived columns should map to its target column.

Your fact key columns should always have matching entries in their associated dim tables, even if that entry is -1 (unknown, N/A, or whatever default you choose).

Once you have this...

sqlbaby2 (10/26/2015)

---

Hi

I've data as below

1111 null ...

It's a warning, not an error. If you're happy with the suggested alternative, just go ahead.

Why use DATEPART(), when you can use YEAR() for this?

Change it to don't save sensitive and redeploy

david.dilworth (10/23/2015)

---

As a C# developer I believe it's better to show the intent of the code or schema with a positive naming convention. Therefore I'd definitely favour the "IsActive"...

You are wrong...

Hawkeye112 (10/23/2015)

---

Hi,

I have a really simple Data Flow Task with a Lookup Task in it. If I run the Task with Full Cache (inmemmory) all my records will be directed...

I am definitely in the 'IsActive', 'IsCurrent' camp.

Have a look here for the general principle.

Your outputs would, of course, each contain different columns, depending on the...

Have a read here[/url].

I suspect that the package protection level has been set to EncryptAllWithUserKey. That is where I would start looking.

I'd be tempted to use an asynchronous Script Component Transformation with five (or however many tables you have) outputs.

--Edit: changed 'asymmetric' to 'asynchronous', oops 🙂