Nope.
BTW you don't need to default any parameter to NULL. They are NULL already :-)



>Do you know why I can not see the changes in the SP while I'm testing it from the .NET?
>
>I added ISNULL conditions, but it still showing me the same error.
>
>I guess it would work tomorrow... On Monday, actually, I'm not coming tomorrow.
>
>>>Hi everybody,
>>>
>>>When I try to change my SP and use Modify option from the Object Explorer, it gives me
>>>

>>>EXEC dbo.sp_executesql @statement = N'
>>>ALTER PROCEDURE [dbo].[RegistrationInsert](
>>>   @RegistrationID int = NULL OUTPUT,....
>>>

>>>
>>>Is there a way to get to the actual code of the procedure to fix rather than have it as a string?
>>>
>>>Thanks a lot in advance.
>>>
>>>One more question - is there a way to make the changes in the SP immediatelly visible to all the processes?
>>
>>
>>Tools->Options->Scripting:
>>Include IF NOT EXISTS clause = False
>>
>>Because ALTER/CREATE PROCEDURE must be the first statement in the Batch that is why is is scripting that way when you include IF NOT EXISTS clause :-)