Building the ultimate chatbot on your own data with Azure SQL and Semantic | Data Exposed

[@xyola]

I did the same for where i work in elixir and postgress sql, obviously there are many things to consider like 1. make sure the sql generated is secure, correct, you want to prevent any change operations 2. In a multi-tenant single database instance, a user of one organization cannot see data of another organization 3. Performing retries 4. Avoiding db connection pool overload. These days I recommend using SQLite as an in memory subset of data isolation if the data is not too bulky

[@dsheardown]

Well, because I am in the UK, all I can say is CRIKEY! or BLIMEY! this is the sort of great utility AI is bringing to the business world. The company I work for has years of old support/knowledge base data - this is perfect to ask questions of it!

[@DesignsbyBlanc]

That’s really cool! Hypothetically, if I’m working for a company and the chatbot should only surface information to a user that’s related to their respective department, what’s the ideal way to go about this? Would it involve some sort of dynamic data injection based on the user, an interface abstraction between the chatbot and the various departmental data that routes to a specific department based on the user, or would it be best to create a separate instance for each department?

[@DavideMauri]

I would strongly recommend to use Row-Level Security to make sure data is not leaked no matter what hacked prompt may be used to fool the AI model to return data that it shouldn't

[@gandharjayantaundhe4023]

Great stuff! Thanks!

[@balajishetty]

❤