Categories

Error Solution: Fix for 'The database principal owns a schema in the database, and cannot be dropped' Error in SQL Server 2005

In SQL Server 2005 , if you try to drop a database user by right-clicking the user name and clicking Delete , you may encounter an error as follows. "The database principal owns a schema in the database, and cannot be dropped. (Microsoft SQL Server, Error: 15138)" The reason for this is that in SQL Server 2005

Filed under: Database,SQL | On : 2007 Mar 27 | From: Shiva @Compile blog |

CS Dev Guide: Forums

WHITEPAPER - Online Indexing Operations in SQL Server 2005

Similar Posts

Basic SQL Server Security concepts - permissions and special principals: sa, dbo, guest

In a previous post , I talked about the various types of principals in SQL Server. Let's have a further look in this post at permissions and at some of

SYSK 200: How To Detect and Remove No Longer Valid Windows Logins From SQL Server

It is a good idea to occasionally audit your SQL servers for users groups that no longer exist in the Windows domain, but still exist on the SQL Server

Post Webcast’s Notes: Securing SQL Server 2005 for Developers

This morning was a jammed filled session covering off a lot of changes made to Microsoft SQL Server 2005. Over the last few weeks we talk exclusively about

Basic SQL Server Security concepts: SIDs, orphaned users, and loginless users

I am grouping here two topics (orphaned users and loginless users) that are actually very different, but I have often seen confusion between them, so I

Most Popular

How To Group ListView Items with ListViewGroup VB2005

Publishing Reporting Services reports to MOSS

How to bind Generic Dictionary with dropdown list

Parse Comma Delimited TextFile with Visual Basic 2005 TextFieldParser

Using the Active Directory Membership Provider with Forms Authentication in MOSS 2007

Using a parameterized SSIS package as a data source for SQL Reporting Services