Hence my suggestion to read the whole post before trying to help... It's happening far too often these days (not just you ).

not in on 8 M records?????????????????????????

I would strongly suggest left join or not exists on this situation.

As it's been suggested you can run a left join or a not exists statement to see which line is missing from the second table. As far as syntaxe...

Might I suggest you read the whole post, or at least the first question before posting ??

From dw_dsa.dbo.e3bdjr_a4bidm e3a4

Left Join dw_dsa.dbo.JobCostDimLookupTbl jcdl on e3a4.Job = jcdl.JOB

Left Join dw_sd.dbo.Job j on...

I don't wanna hurt anyone's feelings, but the obvious answer seems to lie in that column that you change in the final join. I think you'll have to look...

Why r u changing the last join in the 2nd query?

R u looking for bad data?

I've seen something similar, but it's something you have to do yourself... try this :

create Proc A;1 @Param as int

as

set nocount on

select @Param

set nocount off

GO

create Proc A;2 @Param as...

We should post this in the faq in the section : What do we mean by DDL some sample data??

As I was saying you are getting records only for the 16th NOT the 17th.

You can change the query to this :

where oao_date2 >= '" + dayA + "'...

Did you try runnning the query?

What results did you get?

What results did you want to get?

SysDepends is notoriously unreliable. The message tells you exactly what happens : a line cannot be added because the proc is not created yet (even if it is being...

Hence the vartype dateTIME. In sql server, the time always comes with the date. The only thing you can do is to set the time to midnight. ...

Select id_col, col1, col2 from dbo.YourTable where date_col between '" + varDateStart + "' and '" + varDateEnd + "'"

It would be a good idea to use a stored proc...

Forgot to mention that... I gues it's a given to me by now...

Can't you join on the street code?