SQL, MCP, JSON, and Vector Search Explained with Jerry Nixon | Adam Cogan

📞 Contact us: https://bit.ly/4fAFrVx

In this interview from NDC, Adam Cogan sits down with Jerry Nixon to talk about the future of SQL Server and why it remains such a powerful platform for modern applications. Jerry explains how the SQL MCP Server helps AI agents securely connect to databases without developers needing to build and maintain custom APIs for every table and operation. They also explore how SQL Server is evolving with smarter search capabilities, including fuzzy search, regex, full text, and semantic vector search.

Jerry shares how developers can now store vectors directly in SQL, run similarity searches, and keep structured, document, and semantic data in one place instead of spreading it across multiple platforms. The conversation also covers JSON vs XML, document database trade-offs, business logic in the database, and why SQL Server still competes strongly with Postgres. It’s a practical discussion for developers and architects who want to simplify their stack while taking advantage of modern AI and data features.

00:00 | Introduction
00:30 | Jerry Nixon on SQL and MCP Server
01:18 | Why MCP replaces custom database APIs
02:10 | One MCP for SQL, Postgres, Cosmos, and MySQL
02:35 | Token usage and why SQL MCP uses only seven tools
05:03 | Replacing CRUD code with Data API Builder
07:46 | Business logic in the database
09:24 | Fuzzy search, regex, full text, and semantic search
12:00 | Vector data type and semantic similarity in SQL
15:29 | JSON vs XML and SQL Server vs Postgres

🌐 About SSW: https://linktr.ee/SSWTV

🔗 Links:
LinkedIn:   / ssw
Twitter:   / ssw_tv
Facebook:   / ssw.page
Instagram:   / ssw_tv
Tiktok:   / ssw_tv

👋 Get in touch:
Adam Cogan – SSW Chief Architect + Microsoft Regional Director
About: https://www.ssw.com.au/people/adam-co…
LinkedIn:   / adamcogan

#SQLServer #JerryNixon #AdamCogan #MCP #AIAgents #VectorSearch #SemanticSearch #JSON #Postgres #SSWTV

V2 – Bahjat

About the speakers

Adam Cogan blogs at adamcogan.com and interviews for SSW TV frequently. He is the Chief Architect at SSW, a Microsoft Solutions Partner specializing in custom enterprise .NET and Azure solutions mostly using Blazor, Angular, and React. His solutions also involve AI, Office 365, SharePoint, Dynamics 365, and the Power Platform.

Adam is currently working on TinaCMS - the world's best Markdown GitHub editor.

His deep knowledge of SharePoint's many capabilities, combined with the latest technologies (Angular, React, SPFx), let him propose high-quality tailored SharePoint Applications to clients.

Microsoft Teams Etiquette: Simple Habits That Make Meetings Better | Adam Cogan

Whether you’re working remotely or in the office, small habits can make a huge difference in Microsoft Teams meetings. In this video, Adam Cogan shares practical etiquette tips to help meetings run more smoothly—from introducing people who join the room, to announcing yourself when joining a call, using screen sharing respectfully, and ending meetings with a recorded summary that can automatically create a Product Backlog Item (PBI).

These simple communication habits improve collaboration, reduce confusion, and make hybrid meetings more inclusive and productive.

Treat Your Code Like Uranium | Adam Cogan

Adam Cogan shares a striking story comparing two World War II factories—one ordinary, one handling uranium—and the surprising lesson that the uranium workers lived longer because they followed disciplined, risk-aware practices. He connects that idea to software teams: the best outcomes come from careful habits like automated tests, telemetry, pull requests, retrospectives, shared rules, and good tools. The message is simple: treat software delivery with the same respect as dangerous work, and you’ll reduce stress, avoid chaos, and get better results.

3 Tips for Better Video Recordings | Adam Cogan

Great coaching can dramatically improve how you present, communicate, and learn. In this video, Adam Cogan shares 3 practical coaching tips that SSW uses every day—from onboarding and role plays to improving video delivery. He explains why having a coach matters, why immediate interruption beats delayed feedback, and how repeating corrections helps lock in better habits.

TinaCMS + Fumadocs: Bring Visual Editing to Your Docs | Hark Singh

Discover how to connect Playwright with AI agents and unlock powerful workflows.

Stop Using 👍 Wrong in Teams | Adam Cogan

A quick communication tip from Adam Cogan: don’t use 👍 as a catch-all response when someone assigns you a task in Teams, Slack, or Google Chat. In the example Adam gives, if a task will take about five minutes, a thumbs up is too ambiguous because it does not clearly say whether you’ve read it, agree with it, are doing it now, or will do it later. Instead, use 👍 for agreement, 👀 to show you’ve seen the task and are actively working on it, and then replace 👀 with ✅ once the task is done. It is a small change, but it removes ambiguity and cuts down unnecessary follow-up messages.

How to record a done video in SSW | Sylvia Huang | SSW Rules

Sylvia Huang from SSW shares her SSW Cultural Exchange experience from Hangzhou, China to Australia

4 Essential Sales Tips for Engineers | Adam Cogan

Not a salesman? No problem. Adam Cogan shares 4 practical tips to help engineers navigate sales meetings with confidence. Learn how to stop “selling” and start solving, how to talk numbers without the awkwardness, and why being transparent about your process wins more clients.

Do you explain why you’ve deleted or updated an appointment? | Adam Cogan | SSW Rules

Ever wonder why a meeting was moved or cancelled? Adam Cogan explains the “Secret Ingredient” to professional scheduling: always include a version history and reason for change at the top of your appointments. Improve clarity, keep a record of changes, and hold participants accountable with this simple SSW Rule.

Chat first before changing others’ code | Adam Cogan

Changing someone else’s code? Don’t just dive in! Adam explains why it’s important to check the source history and talk to the original developer before making changes. A quick chat can save headaches and keep everyone on the same page. Perfect advice for devs working in teams!