Hopefully this is what you are looking for! 

Hi @gautham_madala,Normally I use python to connect with query service or I have seen some using DbvisualizerCould you please give it a try here instead of the query window inside AEP. It worked for me. Hope this resolves!

Hi @DebrajRo3 ,There are two ways of data deletion:Data hygiene: deletion of data based on "business driven decision" (e.g.- ecid causing incorrect profile stitching, your use case etc)Data privacy: data deletion but recommended when individual user asks to delete his own data (consider GDPR)Now bac...

Can you share the error! Also in terms of debugging, I can see "segment_ingestion_dataset" is at the inner most query, so is that one failing?To add further, I do not see "origin" field in this dataset, I guess you have to share most of the query for debugging.

You can look into catalog API where you will get the full view: urlUse an extra query param:Key = propertiesValue = observableSchema

If you do not need the "Map" field(s), then discard the field(s) from sql and go ahead with "set auto_to_json=true"If you need the "Map" type in sql, then get rid of "set auto_to_json=true" and only use "to_json(<columnName>)" - sample: SELECT to_json(identitymap), to_json(endUserIds) FROM <data...

You have to remove "Set auto_to_json=true;"This function tries to convert every data into json/json string type of object and you must be having some "Map" (identityMap?) field in the schema which it is unable to convert. It works when the data is in below format:Before data: [AAID -> "{(31892EE0800...

Easiest way to do this would be using query service/ data distiller, as long as you know how to differentiate between these 2 datasets, it will be quick & easy:INSERT INTO <target_dataset> SELECT * FROM <source_dataset>where <conditions>

UPS segmentDefinition schema keeps the versions of all audiences. And the identityMap is used to store the audience id (you can query the underlying table).The association between an audience and profile is set up in the profile snapshot schema. There you will find 'segmentMembership' column which w...

In our case, it is scheduled at weekly because the campaign is setup weekly. On top of it, the audience is used to filter out only the high value purchases, so the query can work with small and relevant records only.