Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. XML / XSL
  4. Use XML to define SQL Server security?

Use XML to define SQL Server security?

Scheduled Pinned Locked Moved XML / XSL
databasetoolsxmlworkspacecsharp
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C Offline
    C Offline
    Clive Richardson
    wrote on last edited by
    #1

    We have a number of dev and test SQL Servers (2005) and I would like a more structured and manageable way to setup access/security on these test/dev servers. Currently, it's a time-consuming process because I generally have to manually setup whatever Logins/Security the developers want in test/dev on an ad-hoc basis. Sometimes it's a combination of copying Logins from production and creating test specific logins/security. When the test db's get refreshed/restored, I often end up having to start again - although I try to get the developers to script out the test environment specific security stuff. I was wondering if I could write/buy a utility, like an ASP.NET app that helped developers to input the required Logins, access and so on into a form and have the app save this info as an XML file. The XML file could then in turn be used as in input into another ASP.NET app using SMO to apply the security model defined in the XML file. It would also be necessary to be able to point the app at an existing server, production for example, and generate a template - ie. populate the XML file with that server's Logins, db access, schema info (db owner), db roles, role membership and permissions. I can code this up if necessary and SMO should gve me what I want. However, given that someone else might have already done this, maybe I could save myself a lot of time and effort. Thoughts or suggestions?

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups