This is a mildly embarrassing story to publish for me but it has a great ending. Check out how I spent a ton of $ on a single query then made it so it will never happen again. https://lnkd.in/gY3txv-Y
I really like this post, Ryan Murray. Kind of reminds me of the fears I have around spinning up AWS resources. Curious to hear more stories like this when you have 'em!
(Also, 👋)
With CockroachDB, you can enable always-on experiences and global access when managing user generated data. This video featuring my colleague Rob Reid explains how and why.
With CockroachDB, you can enable always-on experiences and global access when managing user generated data. This video featuring my colleague Rob Reid explains how and why.
Information security (infosec) plays a crucial role in text-to-SQL (Structured Query Language) use cases by ensuring the confidentiality, integrity, and availability of data throughout the process. Here are key aspects of infosec relevant to text-to-SQL applications:
1. Data Encryption: Encrypting sensitive data during transmission and storage to prevent unauthorized access and data breaches. This includes encrypting SQL queries and responses exchanged between applications and databases.
2. Access Control: Implementing strict access controls to ensure that only authorized users and systems can interact with databases and query results. This involves using role-based access control (RBAC), multi-factor authentication (MFA), and least privilege principles.
3. Secure Data Storage: Applying secure database configuration and storage practices to protect SQL databases from vulnerabilities and exploits. Regular patching, secure configurations, and database auditing are essential.
4. SQL Injection Prevention: Guarding against SQL injection attacks, where malicious SQL code is inserted into text inputs to manipulate databases. This includes input validation, parameterized queries, and using ORM (Object-Relational Mapping) frameworks.
5. Auditing and Monitoring: Monitoring SQL query activities and database access logs to detect and respond to suspicious behavior or unauthorized access attempts promptly. Real-time alerting and auditing help maintain data integrity.
6. Compliance and Regulations: Adhering to relevant data protection regulations (e.g., GDPR, HIPAA) and industry standards to ensure lawful and secure handling of data. This includes data anonymization techniques where applicable.
7. Data Masking and Obfuscation: Masking or obfuscating sensitive data in SQL query results to protect privacy while maintaining usability for authorized users. This is particularly important in environments with stringent privacy requirements.
Building the future of LLMs. Cofounder & CEO, Lamini. CS Faculty at Stanford. MIT Technology Review’s 35 Under 35. (Speaker).
So we have a very popular use case Text-to-SQL that’s getting crazy high accuracy 95%-99.9% on different real enterprise schemas — in just days of dev effort. Scoping the problem in different ways that matter to the biz of course.
Are you working on this problem? Open to chatting about it?
Super interested in learning more about your particular schema / situation, esp if complex and not a toy problem…
My team set up a calendar link if easy - https://lnkd.in/gwvYCUfi
Really appreciate it! 🙌
The key unlock here is a SQL LLM agent that can look through your tables to figure out how your data is organized and Lamini Memory Tuning to teach this knowledge to the LLM.
Building the future of LLMs. Cofounder & CEO, Lamini. CS Faculty at Stanford. MIT Technology Review’s 35 Under 35. (Speaker).
So we have a very popular use case Text-to-SQL that’s getting crazy high accuracy 95%-99.9% on different real enterprise schemas — in just days of dev effort. Scoping the problem in different ways that matter to the biz of course.
Are you working on this problem? Open to chatting about it?
Super interested in learning more about your particular schema / situation, esp if complex and not a toy problem…
My team set up a calendar link if easy - https://lnkd.in/gwvYCUfi
Really appreciate it! 🙌
Using a FULL OUTER JOIN ensures we capture the complete picture, eg: including products with stock but no sales and vice versa. Unlike INNER, LEFT, or RIGHT JOINs, which can miss critical data, FULL OUTER JOIN includes all records of the comprehensive picture, eg: helping us accurately identify understock and overstock situations of all items during periods.
Let explore my latest update of SQLinRealworld.
By using a FULL OUTER JOIN, we ensure that all products, regardless of whether they have stock or sales entries in any given month, are included in the analysis. This comprehensive approach captures complete historical data, accurately calculates supply/demand ratios, and identifies potential risks in inventory management.
https://lnkd.in/gB2Ttn8T#InventoryManagement#DataAnalysis#SQL#SupplyChain
Star Schema vs Flat Table - which one performs better?
In his latest blog post, Mike studies their performance to better understand their use cases. View the results here: https://bit.ly/3PjHwtJ
Software Engineer
10moGreat work. Just curious: How do you define total query cost?