Enabling versioning within the MDT Database

Coordinator
Apr 5, 2010 at 11:09 AM
Edited Apr 5, 2010 at 11:22 AM

This is a general discussion on how we would be able to implement some kind of versioning feature in the MDT Database.

I've outlined the details at http://myitforum.com/cs2/blogs/maikkoster/archive/2010/04/05/enabling-versioning-in-the-mdt-database-or-how-to-handle-different-task-sequences-versions-architectures-etc.aspx. To put it together, I would like to be able to restrict what entries are being returned on deployment time to enable the handling of specific problems like 32/64 Bit, different versions of the same TS, Client/Server deployments, etc. One way of doing this is adding something like a Tag, you could also call it version or category (while Category would not be the best name as the MDT Web FrontEnd is using this term already). Think about the typical blog. Each post has several tags that allows you to either see a full list of all posts or limit the list by one or several of these tags. If we now add a “Tag” (or “Version”) column to some of the tables in the MDT database, we would be able to limit the queries during deployment time by simply adding one (or several) allowed tags/versions to the task sequence itself (or even get these dynamically at runtime what makes it a bit more complicated but also more powerful). Now you have two general approaches of querying, depending on your needs. Get all “empty” entries including the ones with the configured tag/version, or get only the ones “tagged” the right way. (Or add something like a “All” tag/version to each entry to simulate the first approach).

Feel free to comment or suggest other ways but please stay on track ;-)

Appreciate your help

Maik