You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
Home > Access It! Universal.NET > Access It! Universal.NET Regional Server Overview
Access It! Universal.NET Regional Server Overview
print icon


Access It! Universal.NET regional Server is a multi-site data synchronization solution. Using Microsoft SQL Server Transactional Replication, the Access It! Universal.NET databases are kept in sync across multiple separate regional servers. Regional servers communicate among themselves, as well as client workstation via a TCP/IP connection.

Prior to implementing Access It! Universal.NET Regional Servers, Microsoft SQL Server must be already installed and configured to allow for transactional replication as outlined in

The installation of SQL replication requires two separate SQL scripts to be executed. To request these scripts, please contact RS2 Technical support. 

Access It! Universal.NET Licensing

The following licensing option must be enabled within the Access It! Universal.NET dongle and is a system wide license.

  • Regional Server Support - Yes

Deployment Decisions

Access It! Universal.NET Regional Server is typically deployed in situations where there are concerns for uninterrupted network availability between sites. In the case of a network outage between sites, the respective regional server will continue to support their local system controllers and client workstations with full functionality. All updates or deletes made to the local database during the network outage will be replicated between all regional servers once connectivity has been restored.

How Transactional Replication Works

Microsoft SQL Server hosts the Access It! Universal.NET database on a publisher machine. Separate Microsoft SQL Servers connect via TCP to the Publisher as Subscribers. Database changes are then replicated back and forth between Publisher and Subscriber.


The Publisher is a server that makes data available for replication to other servers. In addition to being the server where you specify which data is to be replicated, the Publisher also detects which data has changed and maintains information about all publications at that site. Usually, any data element that is replicated has a single Publisher, even if it may be updated by several Subscribers or republished by a Subscriber. The publication database is the database on the Publisher that is the source of Access It! Universal.NET data and database objects to be replicated.


Subscribers are servers that receive replicated data. Subscribers subscribe to publications, not to individual articles within a publication, and they subscribe only to the publications that they need, not necessarily all of the publications available on a Publisher.

Snapshot Folder

The snapshot folder is a directory that stores snapshot files; it is recommended that you dedicate the directory for snapshot storage. It is required a UNC Share name is created that is accessible by both Publisher and all Subscribers. Ensure the SQL Agent account running on both Publisher and Subscriber has read/write access to this UNC Share.

Configuring Access It! Regional Servers


Prior to configuring the SQL Server publication, there must already be an existing installation of Access It! Universal.NET.

  1. Open SQL Server Management Studio
  2. Open the Create_Publication.sql script
  3. Adjust the SQL Snapshot UNC path as needed
  4. Adjust the logins assigned as needed
  5. Execute the Create_Publication.sql script
  6. Within SQL Server Management Studio, navigate to Replication | Local Publications
  7. Right click the AIUniversal Publication and select View Snapshot Agent Staus
  8. Select Start
  9. Wait until completed before configuring Subscriptions


The following steps should be completed on each Regional Server acting as the SQL Subscriber.
Prior to configuring the SQL Server subscriber, there must already be an existing installation of Access It! Universal.NET.

  1. Open SQL Server Management Studio
  2. Open the Create_Subscription.sql script
  3. Adjust the SQL Snapshot UNC path as needed
  4. Adjust the SQL Server Publisher name as needed
  5. Adjust the SQL Server Subscriber name as needed
  6. Execute the Create_Subscription.sql script

Replication Monitor

Replication Monitor is a tool accessed through SQL Management Studio to monitor and troubleshoot replication related issues. To access this tool:

  1. Open SQL Server Management Studio
  2. Right click the Replication Folder 
  3. Select Launch Replication Monitoring

Replicated Data

The following Access It! Universal.NET tables are replicated between Publisher and Subscriber(s):

AccessLevelDetail Cards Maps TimezoneIntervals
AccessLevelElevatorDetail CardUsage Outputs Timezones
AccessLevels Channels PagingServices UserGroupAccessLevels
AlarmResponses Companies PrecisionDetail UserGroupBadgeTypes
AlarmZoneDetail DeviceControllers Readers UserGroupMacros
AlarmZones DeviceControllerTypes ReaderTypes UserGroupMaps
Areas Devices Recipients UserGroupReports
Attachments EmailServices Reports UserGroups
BadgeInfo FloorCodeDetail SCPs UserGroupSites
BadgeTypes FloorCodes SCPCardformats UserLabels
CardAccessLevels Holidays Servers Users
CardDeletes Images SIOs Workstations
CardFormats Inputs Sites  
CardGroups Intervals Servers  
Cardholders MacroDetail TaskDetail
CardholderSites Macros Tasks

Graphical Representation


Access It! Universal Regional Server

scroll to top icon