I am using CA IT Asset Manager version 12.9. I want to know can we make changes in mdb database such as creating triggers,stored procedures etc..
So, while you can indeed add a trigger to the MDB, it would be something that CA would not support. So if your trigger caused issues elsewhere in the MDB (aka, bad data, performance problems, corruption), you would be on your own in solving those problems.
Why is it that you feel you need a trigger? What is it you are trying to accomplish?
Thanks for your response.
I just want to create a trigger on one specific table to populate the data from one column to another column automatically. Or can say modify some thing in that data and store it in another column.
But this trigger i want to apply on one specified table of CA ITAM. Will the trigger work on the data entered from CA IT Portfolio Management.
So, it sounds like you want to keep two fields in sync.. such that when one changes, the other automatically gets the value. You could do this via a PAM process, which is fired when an event occurs on that field (AKA, the value has changed), which then utilizes a custom PAM process (which you would need to write), and uses the ITAM Web Services to update the other field on the asset.
That would be the supported method, but it is quite heavy, with a lot of overhead.
Why is it that you need to keep those fields in sync, or need to copy the data from one column to another? What is the business outcome you are trying to achieve?
Thanks a lot for your expert advice, we have PAM in placed in customer environment we will do like this only.
our requirement is for one financial field, which will populate data only after first field value insertion.
Is there any other possible way to do this.
Richard is completely right, you will lost CA support. Please let we know what do you need.
However you can do it using a new database, somethimes we need something information in our and we cannot change original MDB.
1. Create a new database mdb_aux
2. Always when you need something, do a copy to this new database.
3. IF you need change or add something, you can do everthing in this new database.
How to do copy, for example discovery HW:
get UUID from HW_discovered and copy to a new table in your new database.
Good Work and never change MDB database, you can get problems in future.
Retrieving data ...