@Johnakahot2use I have no idea what you are talking about

@Johnakahot2use yeah 9.5% isn't low-alcohol at all

Also, that hospital reminds me of this: theguardian.com/society/2016/apr/26/…

Morning

Nice day on Monfri, the 54th of Mocember

morning

Morning

morning

@MichaelGreen +1

afternoon

let's say I have this query

JOIN
(
       SELECT *
       FROM   splitforecasttransfervalues(@TijdstipBerekening)) ftv ON ft.id = ftv.forecast_transfer_id JOIN forecast.run ftr ON ft.runid = ftr.id JOIN forecast.batch fbs ON fbs.batchnumber = ft.sourcebatchid
AND
fbs.unitid = ft.sourceunitid
AND
fbsr.[timestamp] = ftr.[timestamp] JOIN forecast.run fbsr ON fbs.runid = fbsr.id

i want to do a join with a column that is not yet been made.

I was told to use CROSS/OUTER APPLY

Not sure how to do that ...

I have a fiddle here dbfiddle.uk/…

what do you expect as output there?

also, your Name column in the ForecastTransfer table should be length 10

@AndyK Why do you have Dutch variable names there? :)

@TomV-trytopanswers.xyz yes

Is there an actual answer to the SSIS "the component metedata is out of sync with the compiled script. Recompile the script using the Script Component Editor" problem? My package works locally, it even works locally when targeting the deployment environment in question, but when I deploy the project, a dataflow script task 'failed validation and returned validation status "VS_ISBROKEN".'

@MikeTheLiar SSIS error messages be like: youtube.com/watch?v=KeFoGo3N_4g

Morning!

@James too straightforward

see you folks

TTYL!

.....I've been seeing this error message on and off for several years at this point and am only just now noticing the "metEdata" typo. As if this error wasn't infuriating enough.