I am using Azure Assistants API as code_interpreter and wanted to know about what are other options/parameters I could use to pass data to Azure Assiatants API, does it always need to be file_ids? The data I want to pass to Assitants is stored in SQL Server, what are the steps I should take to ingest data from SQL Server to Azure Assistants API, apart from creating file_ids? I am following this doc doc

Hi @Karishma Nanda Thank you for using the Microsoft Q&A platform. The file_ids parameter is required to give tools like code_interpreter access to files. When using the File upload endpoint, you must have the purpose set to assistants to be used with the Assistants API . Files can be uploaded via Studio or programmatically using the File upload endpoint . When using the File upload endpoint, you must have the purpose parameter set to assistants to be used with the Assistants API. If you have data stored in SQL Server, you can ingest it into Azure Assistants API. To ingest data from SQL Server into Azure Assistants API, begin by retrieving the desired data through SQL queries. Optionally, transform the data to fit the API's requirements and its supported file types . Then, pass the prepared data to the API using suitable parameters, including direct Rest API requests . Finally, invoke the Azure Assistants API with the prepared data to execute desired tasks like generating visualizations or responding to queries. I hope the provided details help you in your particular use case. Thank you.

Does Azure Assistant API code_ interpreter takes other form of data input apart from file_ids?

Accepted answer

dupammi 8,540 Reputation points Microsoft Vendor

2024-04-30T10:45:30.9533333+00:00

Hi @Karishma Nanda

Thank you for using the Microsoft Q&A platform.

The file_ids parameter is required to give tools like code_interpreter access to files. When using the File upload endpoint, you must have the purpose set to assistants to be used with the Assistants API.

Files can be uploaded via Studio or programmatically using the File upload endpoint. When using the File upload endpoint, you must have the purpose parameter set to assistants to be used with the Assistants API.

If you have data stored in SQL Server, you can ingest it into Azure Assistants API. To ingest data from SQL Server into Azure Assistants API, begin by retrieving the desired data through SQL queries. Optionally, transform the data to fit the API's requirements and its supported file types. Then, pass the prepared data to the API using suitable parameters, including direct Rest API requests. Finally, invoke the Azure Assistants API with the prepared data to execute desired tasks like generating visualizations or responding to queries.

I hope the provided details help you in your particular use case. Thank you.
Please sign in to rate this answer.

1 person found this answer helpful.
Karishma Nanda 265 Reputation points

2024-05-02T08:34:00.06+00:00

thank you dupammi ! Could you please point me to some code based approach(best practice), like github link or anything for getting structured data from SQL Server. I am trying to figure out the most optimized way of data ingestion into Assistants from SQL Server which deal with both cost and latency? I have below questions.

Which format of data to use (csv, json...)?

How to ingest data through assistant, thread, function call...?

dupammi 8,540 Reputation points Microsoft Vendor

2024-05-02T11:31:49.0166667+00:00

Hi @Karishma Nanda

Regarding your specific questions:

Data Format: You can choose the appropriate data format based on your data structure and requirements. Common formats include CSV and JSON. If your data has a tabular structure, CSV may be suitable, while JSON provides flexibility for complex hierarchical data.

Ingestion Method: You can ingest data through the Azure Assistants API using various methods, including direct REST API requests, function calls, or threads. The method you choose depends on your specific use case and requirements. Consider factors such as scalability, latency, and ease of implementation when selecting the ingestion method. For ingestion jobs create, list etc, please check here.

Unfortunately, I couldn't get direct implementation code specific to your use case. Nevertheless, here are some resources that can help you get started to build-upon:

parallel-copy-from-sql-database

Copy data to/from Azure SQL Database using Azure Data Factory

Azure SQL Database connector in Data Factory

Azure SQL Database - Best practices for performance and scalability

I hope the provided details help you in building a scalable solution.

Thank you.

If the earlier provided answer was helpful, do click Accept Answer and Yes for was this answer helpful.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Does Azure Assistant API code_ interpreter takes other form of data input apart from file_ids?

0 additional answers

Your answer