Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Note: Forums will be making significant UX changes to address key usability improvements surrounding search, discoverability and navigation. To learn more about these changes please visit the announcement which can be found HERE.
Windows Server TechCenter >
> 
> 
change attribute property of default schema of ADLDS

Answered change attribute property of default schema of ADLDS

  • Friday, March 08, 2013 8:36 AM
     
     
    Sign In to Vote
    0
    I need to increase default schema attribute rangeUpper, for attribute title(64), postofficeBox(40) etc.

    Is there any impact on performance, search query or any operation?
     

All Replies

  • Friday, March 08, 2013 10:03 AM
     
     
    Sign In to Vote
    0

    It can have such impact, though I can't tell you how to predict it. But what's more important, it can break some applications, which were written with the default range in mind.

    Best Regards, Alexander Trofimov
     
  • Friday, March 08, 2013 1:01 PM
    Moderator
     
     
    Sign In to Vote
    0

    I don't believe you can change the attribute maximum length, which is what I believe you are asking.  This is a database where the attributes have set sizes.

    -- 
    Paul Bergson
    MVP - Directory Services
    MCITP: Enterprise Administrator
    MCTS, MCT, MCSE, MCSA, Security+, BS CSci
    2008, Vista, 2003, 2000 (Early Achiever), NT4
    http://www.pbbergs.com    Twitter @pbbergs
    http://blogs.dirteam.com/blogs/paulbergson

    Please no e-mails, any questions should be posted in the NewsGroup. This posting is provided "AS IS" with no warranties, and confers no rights.

     
  • Friday, March 08, 2013 2:11 PM
     
     Answered
    Sign In to Vote
    0

    pbbergs, hello.

    With all due respect, you can change Range-Upper attribute. As you can clearly see from this page: http://msdn.microsoft.com/en-us/library/windows/desktop/ms680037(v=vs.85).aspx, in transition from Windows 2003R2 to Windows 2008 Upper-Range for title attribute was changed. As updating schema is nothing more than running some kind ldap script with the permissions of schema admin, one can clearly change those parameters. I still would recommend to be extremely cautious, while doing this.

    Best Regards, Alexander Trofimov

     
  • Friday, March 08, 2013 2:22 PM
    Moderator
     
     
    Sign In to Vote
    0

    I would be very interested in seeing your doc, the page you provided doesn't exist.

    -- 
    Paul Bergson
    MVP - Directory Services
    MCITP: Enterprise Administrator
    MCTS, MCT, MCSE, MCSA, Security+, BS CSci
    2008, Vista, 2003, 2000 (Early Achiever), NT4
    http://www.pbbergs.com    Twitter @pbbergs
    http://blogs.dirteam.com/blogs/paulbergson

    Please no e-mails, any questions should be posted in the NewsGroup. This posting is provided "AS IS" with no warranties, and confers no rights.

     
  • Friday, March 08, 2013 2:38 PM
     
     
    Sign In to Vote
    0

    http://msdn.microsoft.com/en-us/library/windows/desktop/ms680037(v=vs.85).aspx

    in previous post a comma was added to the end of the link, sorry.

    Anyhow, we can try it in a lab ;) I'm going to try it on WS 2012.

    Best Regards, Alexander Trofimov

     
  • Friday, March 08, 2013 2:41 PM
    Moderator
     
     
    Sign In to Vote
    0

    That is just the attribute definition.  I would be interested to hear if this actually works, it would really surprise me.  I would have thought the upper limit would have been fixed and if you change it things would either break or it wouldn't allow the change.

    Please update this thread I would be very interested to hear your results.

    -- 
    Paul Bergson
    MVP - Directory Services
    MCITP: Enterprise Administrator
    MCTS, MCT, MCSE, MCSA, Security+, BS CSci
    2008, Vista, 2003, 2000 (Early Achiever), NT4
    http://www.pbbergs.com    Twitter @pbbergs
    http://blogs.dirteam.com/blogs/paulbergson

    Please no e-mails, any questions should be posted in the NewsGroup. This posting is provided "AS IS" with no warranties, and confers no rights.

     
  • Friday, March 08, 2013 2:44 PM
     
     
    Sign In to Vote
    0

    As I said, this definition changes between 2003R2 and 2008. Anyway, I'm going to test it in the lab roght now, so we'll get the answer in an hour or so =)

    Best Regards, Alexander Trofimov

     
  • Friday, March 08, 2013 2:45 PM
    Moderator
     
     
    Sign In to Vote
    0

    Ok, good luck.  :-)

    -- 
    Paul Bergson
    MVP - Directory Services
    MCITP: Enterprise Administrator
    MCTS, MCT, MCSE, MCSA, Security+, BS CSci
    2008, Vista, 2003, 2000 (Early Achiever), NT4
    http://www.pbbergs.com    Twitter @pbbergs
    http://blogs.dirteam.com/blogs/paulbergson

    Please no e-mails, any questions should be posted in the NewsGroup. This posting is provided "AS IS" with no warranties, and confers no rights.

     
  • Friday, March 08, 2013 4:44 PM
     
     
    Sign In to Vote
    0

    I believe I recall people modifying the rangeUpper value for some string attributes. I believe I saw a recommendation to use powers of 2, probably for efficient storage, but I cannot find a reference now. Common values are 64, 128, 256, 1024, 4096, but there are also examples that are not powers of 2. Schema updates sometimes increase the value. I would not decrease. The impact would be on dit size, but I doubt any performance consequences.

    Richard Mueller - MVP Directory Services

     
  • Friday, March 08, 2013 5:08 PM
    Moderator
     
     
    Sign In to Vote
    0

    So AD can make on the fly LDAP size changes to the attributes within its DB.  Wow, I would have never believed that.  That is pretty slick.

    -- 
    Paul Bergson
    MVP - Directory Services
    MCITP: Enterprise Administrator
    MCTS, MCT, MCSE, MCSA, Security+, BS CSci
    2008, Vista, 2003, 2000 (Early Achiever), NT4
    http://www.pbbergs.com    Twitter @pbbergs
    http://blogs.dirteam.com/blogs/paulbergson

    Please no e-mails, any questions should be posted in the NewsGroup. This posting is provided "AS IS" with no warranties, and confers no rights.

     
  • Friday, March 08, 2013 6:07 PM
     
     
    Sign In to Vote
    0

    Well, my experiment allowed me to increase title's upper range to 130. Though, there were some inconsistencies in my test, so I'd like to investigate it more, after I get again to the lab (connection suddenly broke ;(  ).

    http://www.screencast.com/t/Nqz1sXOSm4k

    Now, after I answered our own question, Paul, time to answer topicstarter's question: can AD LDS do this. =)

    I, personally, haven't worked with LDS much, so it is an interesting question, too =)

    Best Regards, Alexander Trofimov


    • Edited by Alex Trofimov Friday, March 08, 2013 6:36 PM OMG... Oh My Grammar... =)
    •  
     
  • Friday, March 08, 2013 7:52 PM
     
     Answered
    Sign In to Vote
    0

    I believe this is the article I remember, where the fix was to increase the rangeUpper value for the userWorkstations attribute from 1024 to as much as 8192. I am experimenting in my lab domain.

    http://support.microsoft.com/kb/938458

    Richard Mueller - MVP Directory Services