transactional replication between non-domain servers

Yes, transactional replication can be configured between two SQL Server instances that are not joined to an Active Directory domain, as long as they can communicate over the network and meet the usual replication prerequisites.

Key points and approach:

1. Prerequisites
   • Both servers must be supported SQL Server editions for replication (not SQL Server Express as Publisher, and not SQL Server Compact as Publisher or Subscriber).
   • SQL Server versions must not be more than two versions apart.
   • SQL Server Management Studio (SSMS) must be installed.
   • A login that is a member of the sysadmin fixed server role is required on both instances when configuring replication.
2. Workgroup / non-domain environment
   • In a non-domain environment, replication typically uses local Windows accounts with identical names and passwords on each server, or SQL logins, depending on the security model chosen when configuring the agents.
   • The tutorials in the documentation assume domain accounts like <Publisher_Machine_Name>\repl_distribution and <Subscriber_Machine_Name>\repl_distribution. In a workgroup, create equivalent local Windows accounts on each server and grant them the required permissions.
3. High-level configuration steps The configuration steps for transactional replication between two fully connected servers are the same whether or not there is a domain:
   1. Prepare servers for replication
      • Follow “Tutorial: Prepare SQL Server for replication (publisher, distributor, subscriber)” to:
        • Configure the Distributor.
        • Configure the Publisher.
        • Ensure required SQL Server Agent and security settings are in place.
   2. Configure transactional replication (Publisher → Subscriber)
      • Follow “Tutorial: Configure replication between two fully connected servers (transactional)”:
        • Create a transactional publication on the Publisher database (for example, AdventureWorks2025).
        • Select the articles (tables) to replicate.
        • Configure snapshot settings.
   3. Create the subscription
      • In SSMS on the Publisher:
        • Expand Replication → Local Publications.
        • Right-click the publication (for example, AdvWorksProductTrans) and select New Subscriptions.
        • Choose Run all agents at the Distributor (push subscription) or configure pull if preferred.
        • Add the Subscriber server by name or IP.
        • Create or select the subscription database on the Subscriber (for example, ProductReplica).
        • On Distribution Agent Security, specify the process account (a local Windows account with appropriate rights, or SQL authentication depending on your security choice).
   4. Set permissions on the Subscriber
      • On the Subscriber, create a login for the account used by the Distribution Agent.
      • Map it to the subscription database and grant db_owner membership, as shown in the tutorial.
   5. Initialize and verify
      • Run the Snapshot Agent if needed to initialize the subscription.
      • Use View Synchronization Status in SSMS or Replication Monitor to verify that changes are flowing.
      • Use tracer tokens to measure latency if required.
4. Documentation to follow
   • Use the replication tutorials as step-by-step guides; they apply to non-domain environments as well, with the main difference being how the Windows accounts are created and referenced:
     • “Tutorial: Prepare SQL Server for replication (publisher, distributor, subscriber)”
     • “Tutorial: Configure replication between two fully connected servers (transactional)”

These tutorials cover creating the Publisher, creating the Subscriber, setting security, and validating synchronization and latency.

References:

• Tutorial: Configure replication between two fully connected servers (transactional)
• Replication tutorials