Execute Python with Powershell in SQL Server 2019

Question

I have been using SQL Server 2016's SQL Server Agent with bottom setting and script for last 3+ years. It was/is working fine.

enter image description here

But, now, I am migrating everything to SQL Server 2019, but the same command does not work.

So, I am wondering if there is anything that I have to modify (in terms of script) because I am using SQL Server 2019.

When I use SQL Server Agent to run other Powershell script (which executes something within Powershell), it works.

When I run the Powershell now, and I am getting this error message:

enter image description here

• Jonathan Fite: Have you looked at this? reddit.com/r/SQLServer/comments/jfrcyt/…
• Java: @JonathanFite What does it mean by "you should use a Proxy to run Python just like you would SSIS"?
• J. Mini: What's the error message?
• Java: @J.Mini Please see the updated post with error mesage. Actually, when I just ran the Powershell file which executes Python file, I see the error on the top. It appears that SQL Server Agent is now out of scope. So strange.
• J. Mini: @Java You're screwed. I've had similar problems on my own box. Unless you can grant the group policy that allows impersonation, then your only choice is to make the account a full Admin. Talk to your Windows people.

Answer 1

If you're not going to specify the program to run the .py file, you need Windows to have a default for that file type. Instead, specify the python executable/binary. This would be an example of what your final line should be, but you'll need to edit it to point to your python binary:

Start-Process C:\Path\To\Python\Executable\python.exe "$cmd"

• Java: It appears that it is working (with modifying the line), but don't I have to fix the original issue with some type of AD or group policy?
• Dave.Gugg: Are you getting an additional error? If so, what is it?
• Java: I do not see error now (by modifying that line). It is working. But, I am not sure whether I need to fix any set up in AD (for later).
• Dave.Gugg: That'll depend on whether you're using a different AD account for the SQL Agent than you were before.
• Java: So, it is not like a major issue, but only affecting AD account for the "SQL Agent" then, I guess.