For a long time now, I've wanted to build a new SQL Management that could do more than the built-in SQL Server Management Agent that you get out-of-the-box with FIM and MIM. And, finally, I have done just that.
It is here....
By using this generic Management Agent for SQL, you can synchronize almost any type of information with SQL Server tables - and now you can finally do deltas as well ...and hold on, you can run stored procedures against the tables as part of your synchronization import and export schedules. All these tings combined should give you the options to make some awesome solutions with FIM/MIM and SQL.
The MA have a lot of features that are needed for a modern FIM2010 or MIM2016 setup, including -
- Full and delta imports
- Delta and full exports
- Can keep and revive deleted information / rows
- Can execute pre- and post import/export Stored Procedures
I really hope that you make use of this MA and please let me know if there are any issues as this is the initial release - and I'll try to fix any issues as soon as possible.
You can get it on CodePlex from this URL - https://sqlma.codeplex.com/
Go it a go when you can...
Enjoy,
Soren
This looks great. Do you have any plans to extend it further? In particular I am interested in the possibility of using a separate pair of tables (single-value, multi-value) for each object type rather than having one large amalgamated table for all objects.
ReplyDeleteIf it looks to be popular, I'll surely keep this project alive. And I may extend with the option you're looking for, but it is not planned for right now and my time is scarse right now :-)
ReplyDeleteHi
ReplyDeleteDo you still maintain this project?
I have an issue using the SQL MA on MIM2016 SP1 installed on Window 2016. I get "Exception from HRESULT: 0x8023072C" when trying to create a MA, do you know if it should work on Win2016?
Thanks
Peter Sonander
Yes, still maintaining. Moving to Github soon. Havent had time to look at it lately though.
ReplyDeletePerfect, I really like it and uses it in an old FIM2010R2 on Win2k8R2. But now when trying to use it in MIM2016SP1 on Win2k16 I get the above message. Any idea what the issue might be?
ReplyDeleteThanks
Peter