OPTION (MAXDOP 1)

• 
  Hi James,
  
  I'd take that to mean that "when you run the synchronization script inside SQL Compare, you get an error that you do not when running the SQL Compare-produced script from inside SQL Server Management Studio"?
  
  If you let us know the error message, that would be most helpful.

  Brian Donahue April 12, 2010 09:47

  - 0 +
• 
  Actually, I mean I have a set of script files I'm trying to compare to a database. In one of the scripts it has OPTION (MAXDOP 1) following an insert statement. When the initial parsing of the scripts happens, it is unable to parse this sproc.

  jamal April 12, 2010 10:59

  - 0 +
• 
  Does SQL Compare ignore the query, or the entire file?
  
  I'll probably need to double-check, but I suspect that SQL Compare's script parser is only supporting database-level DDL and not server-level stuff like setting options.
  
  If that's true, it should warn you but still parse the rest of the DDL in the file.

  Brian Donahue April 12, 2010 12:43

  - 0 +
• 
  SQL Compare ignores the entire file when the script is in a set of script files. We use the option as a result of this bug:
  
  https://connect.microsoft.com/SQL/feedb ... wsignin1.0

  jamal April 26, 2010 09:08

  - 0 +
• 
  Thanks for the reference. I have created bug number SDC-1123 to deal with the OPTION in SQL Data Compare scripts folders.

  Brian Donahue April 26, 2010 09:38

  - 0 +

Add comment

Please sign in to leave a comment.