What type of Collector are you using? The OOTB disabled/locked state would imply you're using several AD collectors but you mention databases.
Unfortunately I think the account disabled attribute appears to be missing in the Multi-Application Collectors (I'm unsure why)
1.) For Databases you could extend the account attribute to hold an account disabled/locked state. You database collector would have to set this value (either writing directly the locked status or using a CASE to write a representative flag). For AFX connectors you'd have to implement the reverse logic (either writing a status code directly or deriving one in your update query).
2.) For Directories/LDAP you would have to extend the account to hold an attribute (such as userAccountControl). You could then map this value in your MAADC to collect this value and configure AFX to write to it for fulfilment.
