Thank you for getting back to us.
Since your DB Admins do not allow invalid procedures you can do something like this. In fact the ORM that we use when it generates those procedures for other DB types such as MS SQL or MySQL it simply creates a dummy variable there. For example this is how the stored procedue sf_Notif_GroupNewsletter_upd looks like those two DB types.
/****** Object: StoredProcedure [dbo].[sf_Notif_GroupNewsletter_upd] Script
: 12/09/2009 13:40:27 ******/
[dbo].[sf_Notif_GroupNewsletter_upd] (@PO_NewsletterId uniqueidentifier, @PO_GroupId uniqueidentifier, @PO_Application nvarchar(50))
So the ORM has built in methods for handling this in other DB engines. If you declare a dummy variable there will be no problem. One think to note however - if you upgrade your version of Sitefinity the DB schema will be automatically upgraded too. This means that the ORM will overwrite all stored procedures to match the ones for the new version, therefore you will have to go to the invalid ones again and put the dummy variable.
In Sitefinity 4.0 we will not have this problem as we are using a different ORM software which will not generate invalid procedures.
the Telerik team