This may be relevant:

https://community.fabric.microsoft.com/t5/Power-Query/ODBC-ERROR-07002-Snowflake-ODBC-10690-Expected-descriptor-record/td-p/3194442

Perhaps try making the proc very simple and seeing whether the error goes away. If it does, you will know that the problem relates (somehow) to...

1. Are the file paths local to the server on which the command is executing, or on a network?
2. Does the account running the SSIS package have the necessary rights...

The following solution assumes that the data should be ordered by (DocEntry, Itemcode)

DROP TABLE IF EXISTS #Test;

CREATE TABLE #Test
(
    DocEntry INT NOT NULL
 ...

You have >1,000 points, so you must know by now how to provide sample data (in the form of CREATE TABLE and INSERT statements) and desired results based on that...

I'm no DBA, but doesn't log shipping require a single primary DB and one or more secondary DBs, with the secondary DBs being (effectively) copies of the primary?

Your requirement seems...

Totally understand why you don't want to do this manually! But …

I know of nothing in the market that can do it, though I haven't looked for a few years....

Hi, thanks for replying. its 50% of the way there. splits out my uniqueidentifier perfectly.

I however, also need the false or true part that relates to each identifier, so...

This issue is likely due to how the Excel driver interprets data types dynamically. If possible, switch to .xlsx format, as it's more stable.

Also, try adding IMEX=1 to the...

Regarding the Excel file, is it empty when the job runs? If not, what does it contain?

I suspect the problem may be to do with the guesswork employed by the...

Regarding my 'easier to read' comment, please also consider using table aliases and removing superfluous brackets.

SELECT h.Date
      ,h.EstCompDate
    ...

This is not directly related, but still worth mentioning.

We try to avoid using FORMAT() here because of its poor performance. Assuming tblWTHistory.EstCompDate is a date, please try changing those two...

If you are really sure that it's not going to cause issues, you can do this.

Disable the trigger, perform the deletion, then re-enable the trigger.

https://www.mssqltips.com/tutorial/sql-server-disable-and-enable-triggers/

OK, that explains it. The deletes are being blocked and instead the delete attempts are being logged in table JournalDeleteAudit.

Please right-click / Script as Create

and post the code here.

Weird. Are there any triggers on this table?