Ira Bell

Power is for Open Source Databases too ! See how MariaDB on IBM Power allows you to resize CPU and memory in real time—without taking your database offline. This video demo shows the power of dynamic scaling in action, giving your workloads the flexibility to grow (or shrink) based on demand—all with zero disruption. https://lnkd.in/g3z5k6Qt

16

If you haven't checked out DQX for Data Quality, you need to read this. 🎉 DQX v0.9.3 is all about boosting your data quality game with better scalability, flexibility, and usability. Check out the highlights: 🚀 Multi-Table Checks: Run checks across multiple tables in a single go! 🗺️ New Validations: Introducing checks for IPv6 addresses, comprehensive Spatial Data (geometry, OGC validity), and ensuring your DataFrame conforms to the expected Schema! 📐 🧐 Smarter Comparisons: Enhanced dataset comparisons now include absolute and relative tolerance. 🎯 Targeted Profiling: Use SQL filters to profile specific subsets of your data for more relevant insights. 🛠️ Flexible Installs: Install DQX in custom workspaces and use group-assigned clusters. Ready to level up your data quality? Check out DQX v0.9.3! 👇 #DataQuality #DQX #DataEngineering #NewRelease

5

Context engineering shifts LLMs from oracle to analyst—frame the task, curate tokens, and apply reusable patterns (RAG, tool calls, memory) to keep complex systems robust. A must-read for product and Agile teams building trustworthy AI-enabled workflows. Explore Chris Loy's take: https://buff.ly/Ca2GrrO #Product

1

Reposting this because the Claude Code COBOL story is driving a lot of sloppy takes and it hurts: 1. A demo is not a core migration. Show a bank moving real transaction workloads off COBOL with testing, audit, and rollback. 2. AI can speed up dev work. It does not replace change control, integration testing, and on call ownership. 3. COBOL lives behind firewalls. Modernizing it needs system context, not code snippets. 4. IBM already ships COBOL modernization tooling: watsonx Code Assistant for Z. 5. No COBOL does not mean no mainframes. Mainframes win on throughput, reliability, security, and IO at scale. Do your research, don’t just trust the headlines.

43

2 Comments

🚀 We're expanding model choice by integrating Anthropic’s Claude Sonnet 4 and Claude Opus 4.1 into Microsoft 365 Copilot and Microsoft Copilot Studio!. This means more flexibility and power for users—whether you're diving deep with the Researcher agent or building enterprise-grade agents. Now you can mix and match models from OpenAI, Anthropic, and the Azure Model Catalog to tailor your AI experience to your business needs. This is a huge step forward in making Copilot even more adaptable, intelligent, and impactful. 🔍 Learn more about how this unlocks new possibilities for reasoning, automation, and agent orchestration. #Microsoft365 #Copilot #AI #Anthropic #Claude #CopilotStudio #PowerPlatform #FutureOfWork

4

Part 2 is live: C.R.A.F.T. Framework with .NET and Azure I broke down exactly how we're using systematic AI-assisted development on my current restaurant tech platform. Key insights: ✅ Multi-agent orchestration: Claude Code for complex logic, Copilot for patterns, GPT-5 for troubleshooting ✅ Centralized documentation that all AI agents reference ✅ GitHub Copilot's Azure integration providing real-time infrastructure context ✅ Multi-layer security scanning catching issues automatically ✅ What actually breaks (file sprawl, multi-tenant logic gaps, performance assumptions) The reality: Different AI models excel at different tasks. The teams getting 3-4x velocity aren't using one tool—they're orchestrating multiple agents with consistent documentation and validation. This is production implementation, not proof of concept. Multi-repository architecture. Real security requirements. Actual scaling constraints. Article: https://buff.ly/MPRBRvL What's your experience with multi-agent AI development? #SoftwareDevelopment #ArtificialIntelligence #DotNet #Azure #DevSecOps

2

Oracle was the first database I worked on, back in 2006, at BT Group, alongside my pair-programming buddy, Ritesh Agarwal, and our tech lead, Aditya S.. Along with SQL Server, Oracle forms the operational core for many enterprises, and for decades, people had to choose between them or migrate across them painstakingly. Interestingly, it's no longer about PL/SQL vs T-SQL; natural language is the new query language, allowing Tursio to support both SQL Server and Oracle! Language is no longer a barrier, and data can stay exactly where it is. #sqlserver #oracle #tursioai #fridaystory

23

We have discovered that an issue can occur with #sqlserver2025 if you have a large number of databases for your instance. We have documented this problem at https://lnkd.in/g-SmMk3r. On this page you will see a workaround to use a startup trace flag to avoid the problem. You are fully supported in production to use this until we produce a fix in a future cumulative update. Feel free to comment if you have questions about this. #sqlserver

319

21 Comments

Cultural change + measurable cost savings = growth. By moving workloads to @microsoft-azure with Azure VMware Solution, the department reduced costs, improved flexibility, and fostered a cultural shift toward innovation. Read this customer story to see how public sector organizations can achieve measurable savings while modernizing securely:

1

SQL Server 2025 brings a groundbreaking evolution to database technology, highlighting AI integration, performance enhancements, and seamless cloud connectivity. The newest capabilities not only enrich existing functions but also empower developers and data engineers to craft intelligent applications, featuring vector search, agents adept at handling rigorous workloads. Discover more about this innovation at: [https://lnkd.in/e3YsNm8G). #ai #agents #LLM

5

While GraphQL is a game-changer for complex, multi-client data fetching, it becomes an "architectural tax" when applied to simple CRUD apps or flat data structures where REST excels. To avoid performance and security debt, prioritize batching with DataLoaders, enforce query depth limits, and treat your schema as a stable product contract rather than a mirror of your database.

4

1 Comment