Instead of making it part of the database using a stored procedure, I thought we will just add it to the deployment steps/notes. Much like how we manually schedule jobs which are newly added or edited after deployment. So, essentially, before scheduling this job after a deployment, run this script first

NOTE that this script does not create tables if they exist already and as you know, it is idempotent