About SET Statements (Transact-SQL)

• jiangrj1

  Old Hand

  Points: 347

  More actions

  May 20, 2014 at 4:40 am

  #150098

  Hi

  Can somebody share some experience about some general set statement in your project? e.g. SET QUOTED_IDENTIFIER

  We've encountered an issue about it, we use the sqlcmd to upgrade the DB. So if a developer forget add set SET QUOTED_IDENTIFIER explicitly in their delivered script, it may be overrided by the previouse (other developer's) script. To overcome this, we should ask developer always put some general set statement before their script like below, is it?

  SET QUOTED_IDENTIFIER ON

  GO

  SET ANSI_PADDING ON

  GO

  ...

  CREATE PROCEDURE

  ...

  If this is a good practice, then how many general set statement need put here normally?

  Thanks,

  Billy

• Jack Corbett

  SSC Guru

  Points: 184394

  More actions

  May 20, 2014 at 1:16 pm

  #1715101

  I don't normally include SET OPTIONS in my scripts. I allow the script to inherit the database/connection SET OPTIONS.

  Jack Corbett
  Consultant - Straight Path Solutions
  Check out these links on how to get faster and more accurate answers:
  Forum Etiquette: How to post data/code on a forum to get the best help
  Need an Answer? Actually, No ... You Need a Question