Forum Discussion

RaajPritvi26's avatar
RaajPritvi26
Frequent Visitor
8 months ago
Solved

Data Agent Example Queries

Hello everyone,   While creating a data agent in Fabric, I added some SQL queries as direction for the agent. While doing it manually, I noticed that everytime I added a query, the agent will proce...
data engineering
  • v-dineshya's avatar
    v-dineshya
    8 months ago

    Hi RaajPritvi26 ,

    Thank you for reaching out to the Microsoft Community Forum.

     

    Hi ssrithar  and apturlov , Thank you for your prompt responses.

     

    Hi RaajPritvi26 , 

    The agent only uses the top four most relevant examples at runtime, but it does not define an upper storage limit. Even the UI currently struggles with large sets. The validator re-checks the entire set every time an example is added or changed. Large sets increase validation load significantly.

     

    Note: 20–40 well‑crafted examples per domain confirmed to work reliably across creators. Avoid attempts to upload >100 until Microsoft improves validation performance. The agent makes use of only a handful during execution, so massive libraries provide minimal additional benefit but large authoring overhead.

     

    Please refer below links.

    Data Agent Example Queries - Microsoft Fabric | Microsoft Learn

    Creator Improvements in the Data Agent | Microsoft Fabric Blog | Microsoft Fabric

     

    I hope this information helps. Please do let us know if you have any further queries.

     

    Regards,

    Dinesh

RaajPritvi26's avatar
RaajPritvi26
Frequent Visitor
8 months ago

Hi ssrithar 

 

Thanks! Appreciate your insights! Another thing that came across my mind is that is there a max number of example queries we can input into the data agent? I played around and noticed anything above 100 will also result in the perpetual validation issue.

apturlov's avatar
apturlov
Icon for Super User rankSuper User
8 months ago

ssrithar I am not an expert in how this is done in Fabric, but I wanted to mention that the Data Agent instructions become part of the context during the chat. The larger the instruction the larger the context the more tokens it consumes during the chats. That will be eating the Fabric Capacity faster. I would suggest there should be a balance between how compex the instructions are and the goal of what you are trying to achive with the agent. I would try and match the instructions set with the main case scenario of this agent intended usage.