The reason why the code doesn't produce an error can be found in the execution plan.  Apparently, since SQL knows there's only 1 row, it never executes the ORDER...

• This reply was modified 2 years ago by kyagi.jo.

CREATE TABLE #tmp ([text] VARCHAR(10) ) 
INSERT INTO #tmp 
VALUES ('1')
INSERT INTO #tmp 
VALUES ('a3') 
CREATE TABLE #tmp2 ([text] varchar(10) )
BEGIN TRY 

INSERT #tmp2
SELECT *
FROM #tmp t
...

• This reply was modified 2 years ago by kyagi.jo.
• This reply was modified 2 years ago by kyagi.jo.

you know,  I can't seem to replicate it with a simple example, but the basic premise definitely was this, where my result set ends up saying (I pasted the code...

Ah that's true... my initial case was a bit more complex, and I tried to simplify it to a postable snippet... in my real case, it was actually producing an...

• This reply was modified 2 years ago by kyagi.jo.

I've managed to fix it. It required going into my registry, and finding the ISDeploymentWizard.exe key that it was opening the program with, the value was something like

"C:\Program Files (x86)\Microsoft...

Yes I've already installed the SSIS extension. It was working fine previously, it was only recently that it stopped working, after I updated my visual studio 2019 professional. I can...

I was using SET STATISTICS IO ON, along with reading through the query plan in SQL Sentry Plan Explorer.

Thanks, the simplified way of calculating the date range produced a much faster query plan than the originally stated way!

It turns out that I can get the simple package parameter example to work if my targetserverversion is set to SQL Server 2017 (an option that wasn't available before I...

Thanks guys. Luiz's code doesn't complete for me when I run it as is, but when I make my loop join change (which seemed to be the larger problem which led to...

This was the intention of the line:
DATEDIFF(DAY