Decoding Repository Table Data

AETLE v6.3.11.6 Repository SQL Server

Hi,

I was wondering if you could explain how to decode the repository tables that store data in image type fields. I am looking to use an SQL Query to find certain packages that have a certain text element in the OBJECT_COMMENTS field.

I have found a similar post related to Search & Replace but it does not seem to decode as expected.
Appreciate some help.

Most of the Image fields are encrypted so you will not be able to SQL against it I am afraid

Thanks Mike.

Is there perhaps something else I could use to somehow flag specific packages? My desire is to present a list of 'flagged' packages in an internally developed webapp that would allow an end user who does not have access to AETL to 'trigger' an ETL workflow to run outside of schedule or as in a retry scenario.

We already have the triggering all setup and functional. In fact, so is the end use UI. However, we maintain a separate table with PackageID and Name in a different database to achieve this.

Which means double handling when it comes to adding in new Packages or removing stale ones.

Since there are no user-definable attributes against a package I thought I would just use the comment attribute and put a flag in there. We could then filter on that and just present a list of acceptable packages that can be triggered.

Cheers & Happy New Year

>>> Is there perhaps something else I could use to somehow flag specific packages?

Do you want to flag it from your own application or from AETL?

Hi Mike.

The idea would be that this flag would exist on the AETL Package Object and only authorised AETL users which is basically just myself and my team colleague.

We would flag specific Parent Package Objects and then the idea I had would be that our application would perform some type of lookup against the AETL database repo and collect all of the package IDs that had this flag set. The names and IDs of the packages would be collected and then presented to the user who would then select one of the packages to manually trigger. AETL to run.

My initial thought of using the comments field would have been to repurpose it to hold extra package attributes which would then provide some extra flexibility if we were to interface to the repo database - for whatever reasons. This is not always a good idea but without any other options I was looking for a workable solution.




I have all of this except for dynamically collecting the list of packages working in production.

Regards

I see what you mean now.
I think the best approach would be to add user fields to the objects_tree table
eg
user_filed1
user_filed2
user_filed3
user_filed4
user_filed5

That will benefit a lot of users