
http://technet.microsoft.com/en-us/library/ms184385.aspx
http://technet.microsoft.com/en-us/library/ms176045.aspx
http://www.replicationanswers.com/FTI2005.asp
http://blogs.msdn.com/b/repltalk/archive/2010/03/17/troubleshooting-snap...
http://www.sqlserver-training.com/video-how-to-setup-replication-with-sq...
SELECT [name]
FROM syscolumns
WHERE [id] IN (SELECT [id]
FROM sysobjects
WHERE [name] = @table_name)
AND colid IN (SELECT SIK.colid
FROM sysindexkeys SIK
JOIN sysobjects SO ON SIK.[id] = SO.[id]
WHERE SIK.indid = 1
AND SO.[name] = @table_name)
If it seems ENABLE_BROKER and DISABLE_BROKER will run forever, it will be probably true. This mostly happens when you run:
ALTER DATABASE [databaseName] SET ENABLE_BROKER
and
ALTER DATABASE [databaseName] SET DISABLE_BROKER
These operations need exclusive database lock.
Keywords: MSSQL, ENABLE_PROKER, DISABLE_BROKER, indefinitely, foreverALTER DATABASE DBNAME SET RECOVERY SIMPLE;
DBCC SHRINKDATABASE (DBNAME, 5)
ALTER DATABASE DBNAME SET RECOVERY FULL;
Keywords: MSSQL, Transaction log, Truncate http://media.techtarget.com/digitalguide/images/Misc/sqlserver_ch14.pdf
Keywords: SSIS, Programming SSIS, Extending SSIS