{
  "id": 6334562,
  "title": "Four problems you inherit the moment your SQL client runs on a server",
  "url": "https://urgent.news/2026/09/08/four-problems-you-inherit-the-moment-your-sql-client-runs-on-a-server",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-08T21:47:00.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/cevheri/four-problems-you-inherit-the-moment-your-sql-client-runs-on-a-server-424e"
  },
  "original_language": "en",
  "account": "Running a SQL client on a server instead of a desktop machine introduces four key problems. First, the trust boundary shifts from the OS user on a laptop to the server process, which now has to verify the identity of each caller to the database. Second, the server must manage a single credential for all connections rather than distributing credentials to each laptop. Third, the network path transitions from a per-person VPN connection to a shared server topology for all database access. Fourth, desktop apps have no cookies or ambient authority, while browser-based clients do, requiring additional security measures like origin comparison. These issues were encountered while building LibreDB Studio, and two of them were initially addressed incorrectly.",
  "summary": "A desktop database client makes two demands nobody writes down: every laptop has to reach the production network, and every laptop has to hold a copy of every credential. Move the client onto a server next to the data and both demands disappear. The credential lives in one place instead of sixty. The network path becomes a deployment topology instead of a VPN grant per person. That is the trade.…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}