Remove ANSI_PADDING statements in SQL scripts.

Remove ANSI_PADDING statements in SQL scripts.

book

Article ID: KB0090666

calendar_today

Updated On:

Products Versions
TIBCO BPM Enterprise (formerly TIBCO ActiveMatrix BPM) -
Not Applicable -

Description

Description:
Description:
============
Users should remove ANSI_PADDING_ON / ANSI_PADDING_OFF statements before
running SQL scripts when configuring TIBCO ActiveMatrix BPM.

Environment:
==========
TIBCO ActiveMatrix BPM, any version, using a Microsoft SQL Server database.

Symptoms:
=========
BPM's Event Collector scripts change the ANSI_PADDING setting for SQL Server.
This means that all tables created subsequently during the same query session
have the wrong setting.

Running any SQL scripts manually may produce the same problem, caused by
misuse of ANSI_PADDING_ON / ANSI_PADDING_OFF statements.

Resolution:
==========
If you are running SQL scripts for ActiveMatrix BPM manually, whether they are
generated from TIBCO Configuration Tool (TCT) or from Microsoft SQL tools
(including running the WorkManagerCreate.sql script as described in
"ActiveMatrix BPM Database Creation Scripts" in the "TIBCO ActiveMatrix BPM
Installation and Configuration" guide for TIBCO ActiveMatrix BPM 2.0), ensure
that you:

1. Find the two SET ANSI_PADDING ON and SET ANSI_PADDING OFF statements
in the script and delete them.

2. Check the database query session settings and ensure that ANSI_PADDING is
turned ON. To do this, right click the query window and select Query Options,
Select the Execution-&gtANSI section and ensure that SET ANSI_PADDING is checked.

   For example, the following:

   SET QUOTED_IDENTIFIER ON
   GO

   SET ANSI_PADDING ON
   GO

   CREATE TABLE [amxbpm].[PVM_MSG_WAITING_RECEIVER](
       [ID] [numeric](19, 0) IDENTITY(1,1) NOT NULL,
    [OPERATION_ID] [numeric](19, 0) NOT NULL,
    [EVAL_CORRELATION_ID] [numeric](19, 0) NULL,
    [PROCESS_ID] [numeric](19, 0) NOT NULL,
    [TASK_INST_ID] [numeric](19, 0) NOT NULL,
    [EVAL_CORRELATION_DATA] [varchar](256) NULL,
    [BLOB_VALUE] [image] NULL,
   PRIMARY KEY CLUSTERED
   (
    [ID] ASC
   )WITH (PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, IGNORE_DUP_KEY = OFF,
   )ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON) ON [PRIMARY]
   ) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]

   GO

   SET ANSI_PADDING OFF
   GO

   should be changed to:

   SET QUOTED_IDENTIFIER ON
   GO

   CREATE TABLE [amxbpm].[PVM_MSG_WAITING_RECEIVER](
    [ID] [numeric](19, 0) IDENTITY(1,1) NOT NULL,
    [OPERATION_ID] [numeric](19, 0) NOT NULL,
    [EVAL_CORRELATION_ID] [numeric](19, 0) NULL,
    [PROCESS_ID] [numeric](19, 0) NOT NULL,
    [TASK_INST_ID] [numeric](19, 0) NOT NULL,
    [EVAL_CORRELATION_DATA] [varchar](256) NULL,
    [BLOB_VALUE] [image] NULL,
   PRIMARY KEY CLUSTERED
   (
    [ID] ASC
   )WITH (PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, IGNORE_DUP_KEY = OFF,
   )ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON) ON [PRIMARY]
   ) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]

   GO

The problem does not occur if scripts are both generated and run by TCT.
Symptoms:

Cause:

Issue/Introduction

Remove ANSI_PADDING statements in SQL scripts.

Attachments

Remove ANSI_PADDING statements in SQL scripts. get_app