I suggest you ...

Make the xml document separate from the script

If the xml document is a separate entity from the sql script that would still allow scripts to be dropped in the folder as is and visible but with no propertes. Just add an optional form that creates an xml document with the same name with all the desired properties such as title, description, owner, and so on.

5 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Steve Prusik shared this idea  ·   ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Steve Prusik commented  · 

        Unless an organization adopts SQL Scripts Manager across the board, there would be a need to maintain the script itself and the script with the xml file. Separate them and teams can use source control on the script itself and update the xml file separately if needed

      Feedback and Knowledge Base