FYI, just in case you care, I was able to get my code fully corrected.

I personally wouldn't use "+2", as it's nebulous unless you already know what it's doing; instead, I'd use the actual base date.  And, if you shift from Excel, the base...

Under no circumstances should you use the actual SSN to link accounts.  You might have to store the SSN in one place, but you sure don't have to store it...

Sorry, I thought you only wanted it down to the minute based on your initial description

duration in terms of minutes

SELECT SUM(DATEDIFF(MINUTE, '1899-12-30', duration)) AS duration_in_mins

SELECT emailaddress, COUNT(DISTINCT emailID) AS emailID_Count
FROM ##myTable
GROUP BY emailaddress
HAVING COUNT(DISTINCT emailID) > 1

Table "C" only has each unique Name and EIN combination only 1 time, no matter how many fiscal years or amounts it has.  That't the whole point of the "C"...

You can use either VALUES or SELECT, you can't combine them:

Insert into Cntrl.tbl_Entity_master

select distinct [Entity Name], [Entity EIN] from B

Yep, just create another table.

CREATE TABLE dbo.Entity_master (

[Entity Name] nvarchar(60) NOT NULL, [Entity EIN] char(10) /*or whatever*/ NOT NULL,

CONSTRAINT Entity_master__PK PRIMARY KEY ( [Entity Name], [Entity EIN] )

)

• This reply was modified 6 years, 9 months ago by ScottPletcher.

Itzik Ben-Gan books and/or videos.

Books will typically you a much more in-depth knowledge.  If you'd rather just have an overview level of knowledge, then a video(s) would work.

We really need to see the execution plan.  Estimated is probably good enough, although actual is better.

You need a separate table to specify a unique entry for ( [Entity Name], [Entity EIN] ).

(Actually, hopefully EIN by itself would be unique.  If it is, use just that. ...

Which specific brand of SQL?  MySQL?  SQL Server?  Oracle (not likely in a 2-person shop, too expensive)?

You can't pass expressions as parameter values.  You need to resolve the expression yourself and pass only a single (scalar) value.  For example:

DECLARE @start_date date

DECLARE @end_date date

SET @start_date = DATEADD(MONTH,...

I don't know that  you'll be able to fix it, particularly without the details of how the "standard audit dates" are maintained.

It seems like this is an integrity check to...