Fix for Issue #3

This fixes issue #3 : When running the removeAllUsersFromDB proc, it will throw an error if it tries to remove a user that is the owner of a schema.
This was fixed by resetting any "non-dbo" schema owner back to "dbo".  Since all users are going to be dropped anyway, this is necessary to 1) prevent the error, and 2) ensure that the schema and any database objects (tables, procs, etc...) possibly assigned to the schema remain intact.

Author: ericcobb

permissions-manager-install.sql

@@ -1223,6 +1223,31 @@ BEGIN
 			PRINT ''Server:   '' + @@servername
 			PRINT ''Database: '' + DB_NAME()
 			
+			--clean up schemas before trying to drop users			
+			DECLARE SchemaResetCursor CURSOR LOCAL FAST_FORWARD FOR
+			SELECT name 
+			FROM sys.schemas
+			WHERE SCHEMA_ID BETWEEN 5 AND 1000
+			AND principal_id <> 1
+
+
+			OPEN SchemaResetCursor
+			FETCH NEXT FROM SchemaResetCursor INTO @UserID
+			WHILE @@FETCH_STATUS = 0
+				BEGIN
+					IF EXISTS (SELECT * FROM sys.schemas WHERE name = @UserID)
+					BEGIN
+						SELECT @SQLstmt = ''ALTER AUTHORIZATION ON SCHEMA:: ['' + @UserID + ''] TO dbo;''
+						PRINT @SQLstmt
+						EXEC (@SQLstmt)
+					END
+				FETCH NEXT FROM SchemaResetCursor INTO @UserID
+				END
+
+			CLOSE SchemaResetCursor
+			DEALLOCATE SchemaResetCursor
+
+
 			--avoid dropping users that were creating using certificates
 			DECLARE DropUserCursor CURSOR LOCAL FAST_FORWARD FOR
 			SELECT p.name FROM sys.database_principals p