SELECT TOP (1) DateTime, 
TOC = value
FROM runtime.dbo.History
WHERE TagName = 'WFI_LP01_TOC.PV'
AND DateTime >= '2018-01-01'
AND DateTime <= '2018-01-08'
AND wwRetrievalMode = 'Cyclic'
ORDER BY value desc

So you want the TOC column to show the same value for all the rows within the selected range?

• This reply was modified 5 years, 6 months ago by Phil Parkin.

Where in the process is the value being set to NULL? The source, somewhere in the data flow, or at the destination? (I suggest you use a Data Viewer if...

In our project, we use this tool to frequently promote SSIS project builds from  DEV ->TEST and further environments.

Hence, it would be a bit challenging to migrate the historical...

Interesting, I had no idea that this tool even existed!

Does it also migrate the run history? (That is, the information displayed on the All Executions report.) If migrating from one...

And then spent hours creating an exploding RBAR GIF, I seem to remember!

• This reply was modified 5 years, 6 months ago by Phil Parkin.

I know he's clever, but still probably prefers to be called Brian 🙂

I presume you've got a lot of this to do & you want to build an automated way of doing it.

The way I've approached tasks like this in the past...

The problem (as far as I can see), is knowing the value of PK_POSTE so that you can INSERT the FK rows in Params_Poste, is that right?

If so, SCOPE_IDENTITY()...

• This reply was modified 5 years, 6 months ago by Phil Parkin. Reason: Fix small typos in code

The...

It looks to me as though this statement

INSERT INTO Postes (NAME_POSTE)
VALUES (@NamePoste)

will fail, because you have not provided a value for PK_POSTE.

QUESTION: why do some queries work on older Compatibility level than the new? i thought microsoft made the Cardinality Estimator better in the new 2012+ versions? or maybe an update...

SSIS does not handle this scenario very well without code. The way I would do it is as follows:

• Set up a dataflow to read every row of the source...

Your problem here is that the underscore character is itself a wildcard in T-SQL, matching any single character. That explains the results you are seeing.

The solution is to ESCAPE the...

• This reply was modified 5 years, 6 months ago by Phil Parkin.

...it states that there are security implications to using it.

Not quite. It mentions 'potential security implications' – and Jeff has described some of those already.

• This reply was modified 5 years, 6 months ago by Phil Parkin.