Stored procedures can be used to customize security permissions in much the same way as views and are commonly used as an easy interface to perform complex activities. In an archiving scenario, data older than a specified interval is copied into an archive table and then deleted from the primary table. Permissions can be used to prevent users from deleting the rows from the primary table directly or from inserting rows into the archive table without deleting them from the primary table. You can create a procedure to ensure that both of these activities are performed together, and then grant users permissions to execute the procedure.