Deployment Procedure
--------------------

ANALYSISDB folder
-----------------

- Run script "SCOM_Blocking_tables.sql" to deploy tables to your centralized "ANALYSIS" database used to analyze the data gathered by SCOM.

- Run scripts dbo.SCOM_InsertBlockingInfo.PRC and dbo.SCOM_InsertBlockingInfo_2000.PRC to deploy the 2 stored procedures in your "ANALYSIS" db.


MP folder
---------

- Import "SQL.Blocks.SSC.Custom.xml" management pack to your SCOM environment to create the following 3 custom rules:
(1) _Custom - Blocking detected in a SQL Server 2000 database - Write Evt Log
(2) _Custom - Blocking detected in a SQL Server 2005 database - Write Evt Log
(3) _Custom - Blocking Detected in SQL Server Database - Generate Alert

- Edit the first 2 rules - Configuration tab, Edit Script Event Provider, Script tab - so that the following lines in the vbs script are modified 
to reflect settings in your environment:

...
sAnalysisInstance = "server\instance"
sAnalysisDB = "dbName"
...
...
sConnString = "Server=" & sAnalysisInstance & ";Database=" & sAnalysisDB & ";UID=xxx;PWD=xxx"
...


VBscripts folder
----------------

- "Custom_SQL2000_Blocking.vbs" and "Custom_SQL2005_Blocking.vbs" are the 2 vbs scripts used in the first 2 rules above, respectively.


SQL-scripts folder
------------------

- "BlockingSPIDS_2000.sql" and "BlockingSPIDs_2005.sql" are the 2 SQL scripts used for gathering blocking information in the 2 rules, respectively.
   Each of the 2 scripts is embedded in the corresponding vbs script.


