<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>default on DBA von Nebenan</title><link>https://dbavonnebenan.de/en/tags/default/</link><description>Recent content in default on DBA von Nebenan</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 08 Jun 2025 11:13:55 +0200</lastBuildDate><atom:link href="https://dbavonnebenan.de/en/tags/default/index.xml" rel="self" type="application/rss+xml"/><item><title>SysAdmin Role ignores the Default User Schema – A confusing story</title><link>https://dbavonnebenan.de/en/sql-server-sysadmin-role-can-override-the-default-schema/</link><pubDate>Thu, 08 May 2025 11:20:44 +0200</pubDate><guid>https://dbavonnebenan.de/en/sql-server-sysadmin-role-can-override-the-default-schema/</guid><description>Today I had another call on my desk where an error message from an application stated that an object in the Sql Server DB couldn’t be accessed. The vendor claimed „connection problem“, I said „DB or at least server problem“, customer says „everything used to work before“. The Extended Events were quickly set up, „Remote</description></item></channel></rss>