Hi everyone!

In writing a current web application, I had a thought about my stored procedure. Lets say it's a simple one as below:
Code:
Create procedure SaveToTable1
    @ValueToSave varchar(25)
AS
    INSERT INTO Table1 (Field1) VALUES (@ValueToSave)
Now, whilst I can write and secure web code from SQL injection attacks, and set permissions on SQL Server to preven anyone accessing this, I wondered if I could also be a little more paranoid and add an additional overhead of a check within the procedure.

I tried on search engines to look for stored procedure code hardening, but haven't turned up much. Some sites are saying SQL Server will check for invalid characters if parameters (like in that statment above) are used - similar to the way .Net code does. I don't know if there's any truth in this, or whether any of you might have your own parsing code - I just thought I'd ask everyones opinion to better understand/learn this please.

Thanks,
Alex