Here's a way to get a distinct list of the server's registered in your CMS (Central Management Server).

--dbo.sysmanagement_shared_registered_servers_internal
--unique list
SELECT DISTINCT s.[server_name] as [server]
FROM	[msdb].[dbo].[sysmanagement_shared_server_groups_internal] g
JOIN	[msdb].[dbo].[sysmanagement_shared_registered_servers_internal] s
	ON	g.[server_group_id] = s.[server_group_id]
WHERE	g.[NAME] LIKE '%'

To detect orphaned users in a given database, simply run the following.

USE [MyDB]
GO
EXEC sp_change_users_login 'report'

If you want to check all databases on a given SQL Server at the same time, just wrap it in sp_msforeachdb.

EXEC sp_msforeachdb "exec [?]..sp_change_users_login 'report'"

Finally to resolve an orphaned user, run the following script to resync the SID of the user to map to the appropriate login. Note that a user does not need to map to a login of the same name just as the login 'sa' maps to the user 'dbo'.

USE [MyDB]
GO

Here are several techniques for changing a bit field to its opposite value (flipping the bit). The simple SELECT demonstrates a BIT field and its opposite. You can adjust this easily to switch to an UPDATE statement.

DECLARE @BitTable TABLE ( BitField bit NOT NULL )
INSERT INTO @BitTable VALUES (0), (1)
SELECT	BitField,
	BitFlipped = ~BitField
	--BitFlipped = BitField ^ 1
	--BitFlipped = 1 - BitField
	--BitFlipped = CASE BitField WHEN 0 THEN 1 ELSE 0 END
	--BitFlipped = ABS(Bitfield - 1)
	--BitFlipped = (BitField + 1) % 2
FROM @BitTable
GO

In order to get a final database backup, you need for the users to not be doing any more transactions against the database. The best way to guarantee this is to place the database in READ ONLY mode. But if there are existing connections, you probably won't be able to do this. First set the database to SINGLE USER mode and then change it right back to MULTI USER. This will drop the existing connections to the database.

USE [master]
GO
--kill existing connections and set to single user
ALTER DATABASE [MyDatabase] SET  SINGLE_USER WITH ROLLBACK IMMEDIATE
GO

As long as you keep your statistics updated, you can use this technique to calculate a quick rowcount of all tables.

SELECT	o.name AS [TableName],
	i.rows AS [RowCount]
FROM	sysobjects o
JOIN	sysindexes i	ON o.id = i.id
WHERE	xtype='u'
	AND	indid < 2 --heap or clustered
ORDER BY [RowCount] DESC

When you have fields that are common across multiple tables, you probably want them to be defined identically. Are they? Are you sure? Use this script to check things like exact case spelling, NULLability and field length/precision.

WITH UniqueColumnDefinitions AS (
SELECT
	o.[name] AS [Table], 
	c.[name] AS [Column],
	t.[name] AS [Data Type],
	c.[prec] AS [Precision],
	c.[scale] AS [Scale], 
	c.[isnullable] AS [Nullable],
	[check_sum] = binary_checksum(c.[name], t.[name], c.[prec], c.[scale], c.[isnullable])
FROM	[dbo].[sysobjects] o 

If you need to bring a copy of the database from production to another environment, you may want to disable all the triggers for all tables. Here is a simple syntax you can use to accomplish this.

First you could specify the specific table(s) for which you want to disable triggers.

ALTER TABLE [dbo].[MyTable] DISABLE TRIGGER ALL

ALTER TABLE [dbo].[MyTable] ENABLE TRIGGER ALL

If you have triggers running against your database tables then you probably want to make sure they are turned on or off at the right times. Here's a script to check the status of your triggers.

SELECT	db_name() AS [Database Name],
	T.[name] AS [TableName],
	TR.[Name] AS [TriggerName],
	[Status] = CASE WHEN OBJECTPROPERTY(TR.[id], 'ExecIsTriggerDisabled') = 1
		THEN 'Disabled' ELSE 'Enabled' END
FROM	sysobjects T
JOIN	sysobjects TR ON t.[ID] = TR.[parent_obj]
WHERE	T.[xtype] = 'U'
	AND TR.[xtype] = 'TR'