This works great for me.

How would I go about grabbing the dates dynamically?

Thanks!, D

Thanks.

This gives me a clean header.

employee  12/1/2019   12/2/2019   12/3/2019   12/4/2019   12/5/2019

• This reply was modified 4 years, 11 months ago by  delizat4g.
• This reply was modified 4 years, 11 months ago by  delizat4g.

Yes...I've added them to the bottom of the OP.

Thanks, D

These are great. I'm studying them now.

Thanks!!

CREATE TABLE aaaMyTable(
rowId int IDENTITY(1,1),
myDatetime datetime,
myCount integer,
invalid bit
)

INSERT INTO aaaMyTable(myDatetime, myCount, invalid)
VALUES
('2019-09-25 13:34:00.000', 3, 0),
('2019-09-25 13:35:00.000', 2, 0),
('2019-09-25 13:36:00.000', 2, 0),
('2019-09-25 13:44:00.000', 2, 0),
('2019-09-25 13:44:20.000', 2, 0)

SELECT...

• This reply was modified 5 years, 1 month ago by  delizat4g.

I def want to thank @scottpletcher's for the help also!

It's difficult and I'm sure annoying because I have to create "dummy" queries, but in this case the two...

@desnorton Thanks very much for the help! Using EXISTS ended up being a few seconds faster and I haven't seen it used this way soo also nice.

Awesome! I think this will work. I'm gonna test it out now.

Thanks!!

@drew_allen your response is not helpful in the least.

1. If you had bothered to read my original post I've already stated that I

"I'm trying to find a way to rewrite...

Both of these are great. This exist might work for me.  I now need to add a third table like...

Working on trying out the WHERE EXISITS @scottpletcher

Yes....I know...

We have databases that need to, eventually, fully migrate to PostgreSQL for the future environment they will be hosted on.

Yea...I think I agree. Just run a job at x intervals to sync up the data. I'll look up linking to a PostgreSQL server.

The schema conversion I'm thinking of just...

Maybe something like datepart

and to_char(a.PROCESSED_DATE, 'MMYYYY') = '042019' ----- Change the month as per request e.g. 062018

AND (DATEPART(year, a.PROCESSED_DATE) = @year and DATEPART(month, a.PROCESSED_DATE) = @month)

Well...I figured it out.

Pretty new upgrade to SQL Server 2016 instance and recently took the database out of 2008R2 compatibility also.

So the stored procedure had 'SET QUOTED_IDENTIFIER ON'  the job...

Here are some examples of what I'm trying to do, but the problem doesn't seem to be the syntax.

SET @point = (select "geo" FROM "objectLocation" where "objectId"...