preventing an accidental execution of a alter SPROC statement

  • What is the best way of preventing an accidental execution of a alter SPROC statatement against a running version of a database.  Is there a kind of locking mechanism that I can use?

  • This was removed by the editor as SPAM

  • I'm not sure but you might be able to use DDL triggers in SQL Server 2005... recommend that you read up about them. If you can't use 'em to prevent proc alterations you can at least get notifications about 'em

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply