Thanks Steve, I didn't know about this. Very useful.

shkoli (10/27/2015)

---

CREATE TABLE [dbo].[Managements](

[ManagementId] [int] NOT NULL,

[FTAManagementNo] [varchar](35) NULL

)

CREATE TABLE [dbo].[MgmtCountries](

[MgmtCountryId] [int] not null,

[CountryId] [int] null,

[ManagementId] [int] null ,

[FTAManagementNo] [varchar](35) NULL

)

i want to get only those ManangementId which is available...

Have a read here and see whether that helps you at all.

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.