No USE statement by default? Silly default state...

leedaviesleedavies Posts: 10
edited August 12, 2010 9:02AM in SQL Compare Previous Versions
Why on earth is the project option "Add database USE statement" not checked by default?

When working in a multi-database environment, a USE statement is rather important. It seems a crazy default option for this not to be checked...?

Comments

  • The 'add USE statement' option was only added in version 8; this option didn't exist in previous versions, and no USE statement was added. To aid people upgrading from previous versions, we kept the same default behaviour as version 7, which meant this option was off by default.

    Note that you can store your own default options in the project options screen (the 'Save As My Defaults' button), which will be used for all future new projects.
  • lfreijolfreijo Posts: 16 Bronze 1
    When generating a script through the command line, I don't see an option to add a use statement. Does one exist?
Sign In or Register to comment.