Skip to content

Commit baf116c

Browse files
committed
Update text2sql
1 parent 9955524 commit baf116c

File tree

3 files changed

+20
-15
lines changed

3 files changed

+20
-15
lines changed

deploy_ai_search/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
# AI Search Indexing Pre-built Index Setup
22

3-
The associated scripts in this portion of the repository contains pre-built scripts to deploy the skillset with Azure Document Intelligence.
3+
The associated scripts in this portion of the repository contains pre-built scripts to deploy the skillsets needed for both Text2SQL and Image Processing.
44

5-
## Steps for Rag Documents Index Deployment (For Unstructured RAG)
5+
## Steps for Rag Documents Index Deployment (For Image Processing)
66

77
1. Update `.env` file with the associated values. Not all values are required dependent on whether you are using System / User Assigned Identities or a Key based authentication.
88
2. Adjust `rag_documents.py` with any changes to the index / indexer. The `get_skills()` method implements the skills pipeline. Make any adjustments here in the skills needed to enrich the data source.
@@ -13,7 +13,7 @@ The associated scripts in this portion of the repository contains pre-built scri
1313
- `rebuild`. Whether to delete and rebuild the index.
1414
- `suffix`. Optional parameter that will apply a suffix onto the deployed index and indexer. This is useful if you want deploy a test version, before overwriting the main version.
1515

16-
## Steps for Text2SQL Index Deployment (For Structured RAG)
16+
## Steps for Text2SQL Index Deployment (For Text2SQL)
1717

1818
### Schema Store Index
1919

text_2_sql/GETTING_STARTED.md

Lines changed: 15 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,26 @@
11
# Getting Started with Agentic Text2SQL Component
22

3-
**Execute the following commands in the `text_2_sql` directory.**
4-
53
To get started, perform the following steps:
64

5+
**Execute the following commands in the `deploy_ai_search` directory:**
6+
77
1. Setup Azure OpenAI in your subscription with **gpt-4o-mini** & an embedding model, alongside a SQL Server sample database, AI Search and a storage account.
8-
2. Clone this repository and deploy the AI Search text2sql indexes from `deploy_ai_search`.
9-
3. Run `uv sync` within the text_2_sql directory to install dependencies.
8+
2. Create your `.env` file based on the provided sample `deploy_ai_search/.env.example`. Place this file in the same place in `deploy_ai_search/.env`.
9+
3. Clone this repository and deploy the AI Search text2sql indexes from `deploy_ai_search`. See the instructions in the **Steps for Text2SQL Index Deployment (For Structured RAG)** section of the `deploy_ai_search/README.md`.
10+
11+
**Execute the following commands in the `text_2_sql_core` directory:**
12+
13+
4. Create your `.env` file based on the provided sample `text_2_sql/.env.example`. Place this file in the same place in `text_2_sql/.env`.
14+
5. Run `uv sync` within the text_2_sql directory to install dependencies.
1015
- Install the optional dependencies if you need a database connector other than TSQL. `uv sync --extra <DATABASE ENGINE>`
1116
- See the supported connectors in `text_2_sql_core/src/text_2_sql_core/connectors`.
12-
4. Create your `.env` file based on the provided sample `.env.example`. Place this file in the same place as the `.env.example`.
13-
5. Generate a data dictionary for your target server using the instructions in the **Running** section of the `data_dictionary/README.md`.
14-
6. Upload these generated data dictionaries files to the relevant containers in your storage account. Wait for them to be automatically indexed with the included skillsets.
17+
6. Create your `.env` file based on the provided sample `text_2_sql/.env.example`. Place this file in the same place in `text_2_sql/.env`.
18+
7. Generate a data dictionary for your target server using the instructions in the **Running** section of the `data_dictionary/README.md`.
19+
8. Upload these generated data dictionaries files to the relevant containers in your storage account. Wait for them to be automatically indexed with the included skillsets.
1520

16-
**Execute the following commands in the `autogen` directory.**
21+
**Execute the following commands in the `autogen` directory:**
1722

18-
7. Run `uv sync` within the text_2_sql directory to install dependencies.
23+
9. Run `uv sync` within the text_2_sql directory to install dependencies.
1924
- Install the optional dependencies if you need a database connector other than TSQL. `uv sync --extra <DATABASE ENGINE>`
2025
- See the supported connectors in `text_2_sql_core/src/text_2_sql_core/connectors`.
21-
8. Navigate to `autogen` directory to view the AutoGen implementation. Follow the steps in `Iteration 5 - Agentic Vector Based Text2SQL.ipynb` to get started.
26+
10. Navigate to `autogen` directory to view the AutoGen implementation. Follow the steps in `Iteration 5 - Agentic Vector Based Text2SQL.ipynb` to get started.

text_2_sql/data_dictionary/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -224,11 +224,11 @@ If there is no pre-built script for your database engine, take one of the above
224224

225225
## Running
226226

227-
**Execute the following commands in the `text_2_sql` directory.**
228-
229227
To generate a data dictionary, perform the following steps:
230228

231229
1. Create your `.env` file based on the provided sample `text_2_sql/.env.example`. Place this file in the same place in `text_2_sql/.env`.
230+
231+
**Execute the following commands in the `text_2_sql_core` directory:**
232232
2. Package and install the `text_2_sql_core` library. See [build](https://docs.astral.sh/uv/concepts/projects/build/) if you want to build as a wheel and install on an agent. Or you can run from within a `uv` environment and skip packaging.
233233
- Install the optional dependencies if you need a database connector other than TSQL. `uv sync --extra <DATABASE ENGINE>`
234234
3. Run `data_dictionary <DATABASE ENGINE>`

0 commit comments

Comments
 (0)