If experiencing the following errors in SQL Server:

Create failed for User ‘xyz’. (Microsoft.SqlServer.Smo)

User, group, or role ‘xyz’ already exists in the current database. (Microsoft SQL Server, Error: 15023)

The above error can sometime occur when migrating a SQL Server Database from one staged environment to another. If both those environments have the same users present you can get issues when trying to add users from the new staged environments to the recently restored DB that the users are already present within.

A solution I found is to map the DB users to the accounts already within the DB. This is achieved by using the stored procedure sp_change_users_login

USE AdventureWorks
GO
EXEC sp_change_users_login 'Update_One', 'xyz', 'xyz'
GO

The above will take the specified user {parameter 2} and map to the login user {parameter 3}.
Further information and other actions are available here: http://msdn.microsoft.com/en-us/library/ms174378(v=sql.105).aspx

Note: MSDN state this feature will be removed in a “future version”.

Good little query to find modified dates of SQL Server stored procedures.
The following example will find stored procs that have been modified in the last 7 days.

SELECT name, modify_date
FROM sys.objects
WHERE type = 'P'
AND DATEDIFF(D,modify_date, GETDATE()) < 7 ORDER BY modify_date desc