← Back
AWS ML Blog

Multi-dataset Topic best practices for Amazon Quick Chat

28 min read
#amazon#enterprise#llm
Level:Intermediate
For:AI Engineers
TL;DR

Amazon QuickSight's Multi-Dataset Topics allows analytics teams to bring multiple datasets into a single Topic, enabling chat-powered, AI-generated SQL queries without pre-joining datasets. The generative AI engine uses semantic context to generate context-aware SQL at query time, supporting complex patterns like outer joins and cross-grain comparisons. This approach differs from defined-relationship Topics, which build a logical join graph and execute inner joins at query time. The practical implication for engineers building AI systems is the ability to create more flexible and dynamic data analysis workflows.

⚡ Key Takeaways

  • Amazon QuickSight's Multi-Dataset Topics support up to 12 datasets and produce deterministic results when using defined relationships.
  • The generative AI engine uses a semantic layer, including dataset-level custom instructions, topic-level instructions, field synonyms, and field descriptions, to generate context-aware SQL.
  • The AI can handle complex patterns like outer joins, many-to-many, recursive hierarchies, role-playing dimensions, and cross-grain comparisons.
  • A decision framework is provided to choose between defined relationships, semantic-only guidance, and hybrid approaches.
  • A complete end-to-end walkthrough is provided using a retail analytics Topic with five datasets.
💡 Why It Matters

The ability to generate SQL queries using chat-powered, AI-generated SQL enables more flexible and dynamic data analysis workflows, allowing data architects, business intelligence engineers, and analytics engineers to build more effective QuickSight Topics. This approach can simplify the process of analyzing complex data sets and improve the overall user experience.

✅ Practical Steps

  1. Configure a Topic for Chat by authoring a semantic layer that includes dataset-level custom instructions, topic-level instructions, field synonyms, and field descriptions.
  2. Use the Semantic Guidance Stack framework to structure metadata that guides the AI.
  3. Apply the eight concrete best practices, each with examples, anti-patterns, and sample instructions, to handle complex patterns and improve the effectiveness of the AI-generated SQL.

Want the full story? Read the original article.

Read on AWS ML Blog

More like this

57% of enterprises have watched AI agents be confidently wrong. The fix is an agentic context layer, but who has one?

VentureBeat AI#agents

Fine-tune NVIDIA Nemotron 3 models with Amazon SageMaker AI serverless model customization

AWS ML Blog#llm

Canva targets enterprise creativity with trusted AI creative workflows

SiliconANGLE AI#enterprise

From Hugging Face to Amazon SageMaker Studio in one click

Hugging Face Blog#deployment

EXPLORE AI NEWS

Daily hand-picked stories on LLMs, RAG, agents and production AI — curated for engineers who ship.

BROWSE NEWS

GET THE WEEKLY DIGEST

Join engineers getting the Monday signal-over-noise AI breakdown. No spam, unsubscribe anytime.

LEARN AI ENGINEERING

Curated courses, research papers, repos and tutorials built for engineers leveling up in AI.

START LEARNING