Infor SyteLine4 min readNetray Engineering TeamUpdated March 4, 2025

How to Configure SyteLine SQL Replication

SQL Server replication for SyteLine databases enables real-time or near-real-time data synchronization to reporting servers, data warehouses, and disaster recovery instances. Transactional replication is the most common approach for SyteLine, providing continuous change propagation with minimal performance impact on the production database. This guide covers publisher configuration, article selection, subscriber setup, and monitoring for SyteLine database replication.

Configuring the Publisher and Distribution Database

Open SQL Server Management Studio and connect to the SyteLine production server. Right-click the Replication node and select Configure Distribution to set up the distribution database. The distributor can run on the same server (local) or a dedicated distribution server (remote) for better performance. Configure the distribution database retention period, typically 72 hours for transaction retention and 48 hours for history retention. Enable the SyteLine database as a publisher by right-clicking Local Publications and selecting New Publication, then choose the SyteLine database as the publication source.

Configure a remote distributor on a dedicated SQL Server instance for production environments with over 500 transactions per minute
Set distribution database transaction retention to 72 hours minimum to allow recovery from subscriber outages without full reinitialize
Create a dedicated SQL Server Agent service account with db_owner permissions on both publisher and distribution databases
Enable the SyteLine database for transactional replication by selecting Transactional Publication type in the New Publication wizard

Selecting Articles and Configuring Filters

In the publication wizard, select the SyteLine tables (articles) to replicate. For reporting databases, include transaction tables like co, coitem, po, poitem, item, customer, and vendor. Avoid replicating system configuration tables (SLForms, SLIDOs, SLMenus) and temporary work tables. Configure article properties including column filters to exclude sensitive fields like cost or pricing from non-authorized subscriber databases. Row filters can limit replication to specific site codes or date ranges for multi-site SyteLine deployments.

Select core transaction tables (co, coitem, po, poitem, ap_trx, ar_trx) and master data tables (item, customer, vendor, wh)
Exclude SyteLine system tables (SL-prefixed tables like SLIDOs, SLForms, SLScripts) from replication to reduce overhead
Configure column filters to exclude cost fields (unit_cost, matl_cost) from subscriber databases used by external departments
Apply row filters using site_ref column for multi-site deployments to replicate only site-specific data to regional subscribers

Managing Subscribers and Monitoring Replication Health

Add subscriber databases through the publication properties in SSMS. Configure the subscription as push (publisher initiates) or pull (subscriber initiates) based on network topology. For SyteLine reporting databases, push subscriptions provide more consistent latency. Monitor replication health using the Replication Monitor accessible from SSMS or the Distribution Agent job history. Set up alerts on the SQL Server Agent for replication latency exceeding thresholds, typically 5 minutes for critical systems and 30 minutes for reporting workloads.

Configure push subscriptions for LAN-connected reporting servers and pull subscriptions for remote site or cloud subscribers
Set the Distribution Agent schedule to Continuously for near-real-time replication or every 5-15 minutes for reporting databases
Monitor replication latency in Replication Monitor > Tracer Tokens with alerts configured for latency exceeding 5 minutes
Create SQL Server Agent alerts for replication error codes 20598 (subscriber not found) and 20011 (distribution agent failed)

Frequently Asked Questions

Does SQL replication impact SyteLine production performance?

Transactional replication adds minimal overhead to the SyteLine production database. The Log Reader Agent reads the transaction log asynchronously, typically consuming 2-5% of CPU resources. Write performance impact is negligible as replication reads committed transactions from the log rather than intercepting write operations. For high-volume environments processing over 1,000 transactions per minute, use a remote distributor to offload distribution processing.

How do I handle SyteLine schema changes with active replication?

Schema changes (DDL) on replicated tables require careful coordination. SyteLine updates and service packs may alter table structures. Before applying SyteLine updates, pause replication by disabling the Distribution Agent job. Apply the update, then use sp_refreshsubscriptions to synchronize schema changes to subscribers. For adding columns, use sp_articlecolumn to include new columns in the publication. Plan 15-30 minutes downtime for schema synchronization.

Can I replicate SyteLine data to a different SQL Server version?

Yes, SQL Server supports replication between different versions with the subscriber running the same or up to two major versions behind the publisher. For example, a SQL Server 2019 publisher can replicate to SQL Server 2017 or 2016 subscribers. Cross-version replication supports all SyteLine table types. The subscriber must use the same or compatible collation as the publisher database, typically SQL_Latin1_General_CP1_CI_AS.

Key Takeaways

1Configuring the Publisher and Distribution Database: Open SQL Server Management Studio and connect to the SyteLine production server. Right-click the Replication node and select Configure Distribution to set up the distribution database.
2Selecting Articles and Configuring Filters: In the publication wizard, select the SyteLine tables (articles) to replicate. For reporting databases, include transaction tables like co, coitem, po, poitem, item, customer, and vendor.
3Managing Subscribers and Monitoring Replication Health: Add subscriber databases through the publication properties in SSMS. Configure the subscription as push (publisher initiates) or pull (subscriber initiates) based on network topology.

Need help setting up SQL replication for your SyteLine environment? Netray's database experts ensure reliable, performant replication configurations.

Talk to an Expert See a Demo

Related Resources

Infor SyteLine