Thanks for getting in touch!
If I understand the issue correctly you are bundling a SQL script file within your website package so that you can call and run it from the
SQL - Execute Script File step?
What I would suggest as a possible alternative is to have the script file added as a second package to your deployment using the
Deploy a Package step and enabling the
Custom Install Directory option which is available under
Configure Features in the top right right hand corner. What this will let you do is deploy your script file to the deployment target at a known location that you can then call in your SQL script step.
The advantage here is that you can then have a following script step at the end of your process that then removes this directory (or the files in the directory) as part of you deployment, which means that your SQL file should only be there for the duration of the deployment. I would also suggest selecting the
Purge this directory option as part of configuring your Custom Install Directory, just as a safety measure to ensure that only one SQL file can be present at any time.
I hope that helps, please let me know if there is anything else that I can assist with, or if I’ve misunderstood the issue at all.