title: do i need to explicitely add SET ANSI_NULLS ON in EntityFramework migration
body: <p>I am writing migration for <code>stored procedure</code> with <code>EF 6</code></p>
  
  <pre><code>string sqlQuery = @"
                              /****** Object:  StoredProcedure [dbo].[GetSalesByLocation]    Script Date: 9/21/2016 8:32:36 AM ******/
                              SET ANSI_NULLS ON GO 
  
                              SET QUOTED_IDENTIFIER ON GO
  
                              CREATE PROCEDURE [dbo].[GetSalesByLocation] 
                                                      @MerchantID bigint,
                                                      @LocationID bigint,
                                                      @AccountAccessID bigint,
                                                      @KioskID bigint,
                                                      @StartDate DATETIME,
                                                      @EndDate DATETIME
                              AS
                              BEGIN
                              .....
                              END
                              GO";
                 Sql(sqlQuery);
  </code></pre>
  
  <p>when i try to run <code>Update-database</code> command i get below error</p>
  
  <pre><code>Incorrect syntax near 'GO'.
  Incorrect syntax near 'GO'.
  'CREATE/ALTER PROCEDURE' must be the first statement in a query batch.
  Incorrect syntax near 'GO'.
  </code></pre>
  
  <p>Also when i create <code>SP</code> without </p>
  
  <pre><code> SET ANSI_NULLS ON GO                                 
   SET QUOTED_IDENTIFIER ON GO
  </code></pre>
  
  <p>and open in SQL management studio i can see above statement getting added automatically.</p>
  
  <p>So my question is if i am writing migration for stored procedure do i need to `set ansi null on explicitly?</p>