Hate to break it to you, but the way you get better at SQL is the same way you get better at anything else. By trying, maybe failing, and learning...

So what part of DATEADD didn't work for you?

If you're adding values from the previous record, you need to look at the windowing function LAG().

And if you need to do...

Are you just adding [Duration] minutes to [CodeStartTime]? If so, then use DATEADD

select dateadd(minute,12,'6/1/2020 11:15')

I don't there is a reliable way of doing this in SSRS or T-SQL. It's just that some names have spaces in them etc. They're not standard, so a pure...

• This reply was modified 3 years, 11 months ago by pietlinden.

"It takes too much time" -- Got any indexes on the tables? like on the Primary/Foreign Keys that you're doing your joins on? Did you look at the query's execution...

Seems like you could create a step in your SSIS package that groups all the files that start or end with the same prefix/suffix together. Then just use a For...

I think this does what you want:

select person_id,
string_agg(name_change,' || ')
from dbo.test
group by person_id;

Are you using Access to write your queries? Shouldn't that HAVING clause be a WHERE clause?

Why are you storing dates as text?

You're looking for LAG().

SELECT from_set
,prevVal =  LAG(from_set,1) OVER (ORDER BY from_set)
FROM Test;

Found and article that does most of what I want. Now to build it and practice... oh, and break it, just so I know what it looks like when it...

• This reply was modified 3 years, 11 months ago by pietlinden.

Uh oh... so I should learn some basic C# or Powershell (or both).

I guess it's time to look for a good validation tutorial maybe. Thanks!

You would have to modify the bottom part of the query...

SELECT Field1, Field2, Field3
FROM
(SELECT Cast('DQUOTE'+Member4Parent.NAME+'DQUOTE' AS VARCHAR(20)) AS Field1 ,
       ...

Where's b.[DMDPostDate] is your SELECT statement, because it's in your GROUP BY clause?

Do you have an existing OLTP database to build from?

What does each record in your fact table represent? What kind of reporting/summarizing do you want to do?

The fun part is...

Are all the KEN_N## tanks or something? Sounds like a design flaw.  What does the underlying table look like?