re: Some things I don’t like about the MDT Database

maikkoster — Thu, 10 Sep 2009 11:11:39 GMT

I agree on Applications, Packages and Administrators. It's not possible to verify if the entry is valid. But on Roles you actually do know. I can't really think of a reason of having a role still in the configuration of an Computer if that role has been removed from the database.

Anyway, I can imagine how the database has been developed at the beginning. It just has to work ;-) Isn't that mostly the way some things start?

re: Some things I don’t like about the MDT Database

mniehaus — Mon, 31 Aug 2009 19:57:04 GMT

It is basically a copy-and-paste trigger, making sure all possible child Settings* rows are cleaned up. It's not designed to remove the rows from other items (e.g. computers) that might reference the role.

Expand the scenario to applications and you see the complication: We don't know inside the database what the valid list of applications is, so we can't clean that up.

It shouldn't surprise you that the MDT database was originally developed in about a week - there's only so much you can do in that amount of time :-) We thought we'd be able to make some enhancements in the future (and we did make some in MDT 2010, adding new columns), but other priorities continue to win out.

Eventually we want to be able to move to a true CMDB.

-Michael

Maik Koster at myITforum.com - All Comments

re: Some things I don’t like about the MDT Database

re: Some things I don’t like about the MDT Database