"noexec on" function parse errors, any alternatives?

Question

Hi there,
I'm strugling with the noxec option which still produces sql compile errors (not a simple syntax error).
Situation:
We use a custom delta script pattern which stops the execution on certain conditions by setting
noexec.
This is working fine so far but the problem starts when an old delta script is about to run.
We can still set noexec but functions which do not match in their parameter count (which is unavoidable) produce this error message:
An insufficient number of arguments were supplied for the procedure or function ...
This is pretty painful, because it's still valid syntax. We wouldn't care about the error, but the whole SQL Publish process is aborted by this kind of error.
Question:
Is there an alternative for that (besides wrapping everything in dynamic SQL)?
Maybe there's some kind of SQL Publish like "Ignore all 313 errors" which I could not find?
Regards and thanks in advance!
Knickedi

Answer 1

Thank you for your responses!
SQL Publish
SQL Publish is used by WebDeploy (which seems to be build on top of MSDeploy). (It's quite confusing and maybe I'm getting things wrong, so bare with me). In short: You can Publish a Web-Project in Visual Studio with WebPublish (server must support it) and
you have the option to list SQL files which will be executed against your Database (we have a staging application for testing we publish against before we publish against our productive application).
Example
Here's some stripped down example of our delta script:
We check for the version and if its already present we avoid executing it (noexec off at the end). So in this example I get the wrong parameter count message, because the function has changed in the next versions.
declare @retVal int;
execute @retVal = SpDeltaCheck('v1.2')
if @retVal <> 0
begin
set noexec on;
end
go
CREATE VIEW [Test]
AS
SELECT dbo.FnWithWrongParamCount(t.Id) as TestValue,
FROM Test t
set noexec off;
go
parseonly seems to be what we're looking for but you can't execute it conditionally in an if-block. It will be set as soon it is parsed.
Further consideration
Of course we could remove the old scripts after every successful publish but then we start adding further traps and complexity for the publisher. Because every developer will add scripts and that's not just one per version but one per git push (if s/he has
database changes). The idea was to list them all and don't care about which was already executed.