That was not an SSMS error, it was an error generated by the server when attempting to execute your query. You can see your SQL Server version by running this:

Check this article for the DelimitedSplit8k function:

https://www.sqlservercentral.com/articles/tally-oh-an-improved-sql-8k-%E2%80%9Ccsv-splitter%E2%80%9D-function

We have assumed that you are using SQL Server 2022, as that is the forum you have posted in. The third argument of...

One possibility

DECLARE @x VARCHAR(500) = 'Hello world.  #1234 has been replaced by #014521';

SELECT STUFF (value, 1, 1, '')
FROM STRING_SPLIT(@x, ' ')
WHERE LEFT(value, 1) = '#';

Simply increase the frequency to every minute. The job won't kick off again if it is already running, if you know what I mean.

Thanks Drew. Now the question is, what does SQL consider commented out vs not commented out in my example.  In the example I gave will SQL consider everything between...

Haven't looked for your error, but you could replace all of this:

               ...

If this is a production server, you shouldn't be running Developer Edition on it!

But if it's not, and Integration Services has been installed as per the link I sent earlier,...

OK, I looked closer at the error and it sounds like Integration Services was not installed on the server. This is part of the SQL Server installation process and not...

That does not tell you the version of SQL Server. Please run this query on the server and post back the results:

SELECT
    Version =...

What version of SQL Server 2019 is installed? (Enterprise/Standard/Express etc)

Can you confirm that you have other SQL Agent jobs configured which execute SSIS packages?

The VS extension which allows you to...

DT_DECIMAL does not have a precision. Use DT_NUMERIC in your formula instead.

Although this does not address your question, I'd be tempted to try out this alternative syntax:

WHERE NOT EXISTS
(
    SELECT x.status
    ...

WHERE sent_rowid is null or vendor = @vendor_param

?

Frederico's message is spot on, as usual!

In my opinion, Excel should almost never be used to view *sv files, because as part of its parsing, it tends to display values...

If your databases are fully source-controlled, it should be possible to simply deploy them from the relevant branch. The act of deploying will take care of most of the DDL...