[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8},"actionData","errors","root",{"_29":-5,"_39":-5,"_40":41,"_42":43,"_44":45,"_46":47,"_48":49,"_50":51,"_52":53,"_54":55,"_56":57,"_58":59},"routes/_store+/_readers+/email_author.$slug/route",{"_9":10,"_11":-5,"_12":-5},"book",{"_13":14,"_15":16,"_17":18,"_19":20,"_21":22,"_23":24},"currentUser","formToken","id","Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6Qm9va1Byb2R1Y3QvODQ0ODA","title","Migrate your SQL Server Workloads to PostgreSQL - Third Edition","state","unpublished","contactAuthorMethod","email","aboutText","

I wrote the first edition of this book in 2020, after several years moving production workloads off SQL Server. The second edition, in 2022, updated that guidance as PostgreSQL matured. This third edition is a ground-up rewrite, not an update, because two things changed enough since 2022 to justify starting over: PostgreSQL shipped four major releases that closed real gaps (native temporal constraints, cheaper vacuuming, async I/O, built-in OAuth), and the shape of a migration project itself changed, serverless Postgres turned provisioning into a five-second decision, and LLM-assisted tooling turned schema and code conversion into a supervised, semi-automated process.

The book is restructured around how a migration actually unfolds: understand both platforms, assess what you have, choose a target, execute the move in stages, run it well once you're there, and validate that you landed where you meant to. It follows one migration end to end, three databases moving from SQL Server to PostgreSQL, covering schema conversion, data movement and validation, translating T-SQL to PL/pgSQL, security, monitoring, high availability, performance, and the validation and rollback planning that comes after cutover.

Almost every migration I've been involved in went sideways at least once, in some small, recoverable way, and rarely for the reason anyone predicted going in. This edition keeps that texture rather than the sanitized version where every conversion goes cleanly, with short field notes drawn from real migrations throughout. It's written for database administrators, platform engineers, and architects deciding whether, or how, to move relational workloads from SQL Server to PostgreSQL. Working knowledge of SQL Server is assumed; prior PostgreSQL experience is not.

","authors",[25],{"_13":26,"_27":28,"_29":30},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci85MDE0OA","name","Shameel Ahmed Z","user",{"_31":32},"avatar",{"_33":34,"_35":36,"_37":38},"url","https://d39qdlcrvnra4b.cloudfront.net/avatars/3349573/medium/avatar.jpg?1784447868","styleName","medium","exists",true,"shoppingCartId","shoppingCart",{"_13":72,"_73":74,"_75":38,"_76":77,"_78":79,"_80":81,"_82":38},"locale","en","readerTheme","light","constants",{"_70":71},"publishers",{"_66":67,"_68":69},"learnerOrganizations",[],"needsLocaleCookieSync",false,"announcements",{"_60":61,"_62":-5},"sentryEnvironment","production","sentryRelease","cb566d39bffff58e48bd71e05a109506232f3ba9","announcement_store",{"_63":53,"_64":65},"announcement_authors","flag","text","

Kick off your book project, get started with GhostAI, get better at marketing, or spend the day doing all three! Free live workshops on Zoom. Saturday, June 27, 2026.

\n","companies",[],"universities",[],"paypalClientId","AX53Cwz8jR6rVVzzZiZNWWXl0dGagi-GZrjG-S3Ua14E5nrKMn7DxDQ730O4R8LusLPp49ALn6aRVaEy","no-cart","count",0,"free","updatedAt","","paymentGateway","STRIPE","cartItems",[],"loading"]

Email the Author