Known Issues for Microsoft SQL Server

Cannot downgrade Replication Agent for Microsoft SQL Server 15.7.1 SP100 after upgrading.

Workaround: None.

Data inconsistency with ltl_send_only_primary_keys enabled and custom function strings.

If you have ltl_send_only_primary_keys set to true and are using custom function strings on table columns other than text or image columns, data in the replicate database may be inconsistent with data in the primary database.

Workaround: Set ltl_send_only_primary_keys to false.

WRITETEXT and UPDATETEXT are not supported.

Replication Agent for Microsoft SQL Server does not support use of the Microsoft SQL Server WRITETEXT and UPDATETEXT statements. Data inserted or updated with these statements may therefore be replicated as null.

Workaround: The WRITETEXT and UPDATETEXT have been deprecated as of Microsoft SQL Server 2005. Microsoft recommends using the large-value datatypes and the WRITE clause of the UPDATE statement instead.

Cannot use a database replication definition and database subscription with dsi_alt_writetext set to dcany.

Workaround: Use table replication definition and table subscriptions.

pdb_xlog init fails when Microsoft SQL Server 2008 is upgraded to the developer version.

pdb_xlog init fails when a SQL Server instance is upgraded from Microsoft SQL Server 2008 standard version to the developer version. This is a limitation of Microsoft SQL Server—during SQL Server upgrading, the “Agent XPs” component is turned off, which prevents pdb_xlog init from succeeding.

Incorrect LTL generated.

Incorrect LTL may be generated in a partition schema for an update transaction that affects the primary-key column of a table referenced by the cascading foreign-key column of another table. For example, two tables are created, one with a primary-key column referenced by the foreign-key column of the other table. This causes updates to cascade to the primary-key column of the first table:

create table table1 (id int constraint PK_1 PRIMARY KEY 
CLUSTERED WITH FILLFACTOR=90 on myRangePS1(id), 
value1 varchar(8) null); 

create table table2 (id int constraint FK_1 FOREIGN KEY 
REFERENCES table1(id) ON UPDATE CASCADE, 
value1 varchar(8) null); 

Data is inserted into both tables:

insert into table1 values(3,'aaa'); 
insert into table2 values(3,'aaa');

The primary-key column of the first table is subsequently updated:

update table1 set id =4

The resulting update transaction results in the following logged commands:

LOP_BEGIN_XACT NULL 
LOP_BEGIN_UPDATE NULL 
LOP_DELETE_ROWS dbo.table1.PK_1 
LOP_INSERT_ROWS dbo.table1.PK_1 
LOP_DELETE_ROWS dbo.table2 
LOP_INSERT_ROWS dbo.table2 
LOP_END_UPDATE NULL 
LOP_COMMIT_XACT NULL

The LTL generated for this transaction does not identify that the delete operations are grouped with insert operations as part of an overall update operation. Consequently, Replication Server is suspended.

Workaround: Drop the foreign key constraint in your replicate database. This will not result in data loss because both the original delete and the cascade delete commands are sent to the replicate database.

An error occurs when applying service patch.

When you run the SQL Server 2008 service patch, the Replication Agent system tables sys.sp_SybSetLogforLOBCol and sys.sp_SybSetLogforReplTable are deleted from the resource database, triggering error 29537:

MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client]
[SQL Server]Could not find stored procedure 'sys.sp_SybSetLogforLOBCol'.. To continue, correct the
problem, and then run SQL Server Setup again.

Workaround: Before you apply the service patch, disable the database triggers that Replication Agent created:

1. Log in to the primary database.
2. Disable the automark trigger if it is enabled. For example:

   DISABLE TRIGGER ra_createtable_trig_ ON DATABASE

   where ra_createtable_trig_ is the automark trigger created by Replication Agent.

3. Disable the data definition language (DDL) trigger. For example:

   DISABLE TRIGGER ra_ddl_trig_ ON DATABASE

   where ra_ddl_trig_ is the DDL trigger created by Replication Agent.