title: How to Stop SSMS 2012 from scripting SPs using sp_executesql
body: <p>I realise this is a very similar question to <a href="https://stackoverflow.com/questions/1263588/stop-ssms-from-scripting-sps-using-sp-executesql">Stop SSMS from scripting SPs using sp_executesql?</a></p>
  
  <p>However, they seem to have changed the behaviour with SSMS 2012.</p>
  
  <p>If you have the 'Check for existence' option selected, as in:</p>
  
  <p><img src="https://i.stack.imgur.com/cOo9K.png" alt="enter image description here"></p>
  
  <p>... it now generates an IF NOT EXISTS for the proc about to be created, <strong>as well</strong> as an IF EXISTS for the previous drop proc, if, as I usually do, I select the DROP and CREATE option:</p>
  
  <p><img src="https://i.stack.imgur.com/ANh8V.png" alt="enter image description here"></p>
  
  <p>This forces it to script the CREATE using sp_executesql.  It's pointless, since you don't need the IF NOT EXISTS check on the CREATE, if the DROP has just dropped it.</p>
  
  <p>It doesn't seem possible to have the one without the other.</p>
  
  <p>Any ideas?</p>