Technical Notes. ClearWeigh on SQL Server

Transcription

1 Newcastle Weighing Services Pty. Ltd. Newcastle Weighing Services Pty. Ltd. Phone (02) Hannell Street, Wickham, NSW Web Technical Notes on SQL Server Introduction This document outlines server and database requirements when running on Microsoft SQL Server. It also explains the methods used by to connect to the database. This information is intended to help system administrators plan for an installation of. Network The diagram below describes a typical setup. Database Touch Administrator Reports Touch, Administrator and Reporting Applications all connect to a single database via a LAN or similar network with comparable speeds to a LAN. Connection Protocols client applications connect to the database using ADO.NET, with the Microsoft ADO.NET Provider for SQL Server. can connect using any protocol supported by SQL Server. The connection protocol used is not set explicitly when client applications are installed. Tech Notes Page 1 of 6

2 Database Configuration There are no special requirements for the configuration of the database. The size of the combined database and log files is not expected to exceed 100GB in the majority of cases. Backup of the database is the organisation s responsibility. does not create backups of the database. Database Installation Creation of the physical database files will typically be carried out by the organisation s IT staff. NWS technicians will then run scripts to create the required database objects and configure the database for. Technicians will require sysadmin access in order to run these scripts. Tech Notes Page 2 of 6

3 SQL Server Requirements Supported Versions Microsoft SQL Server 2012 Microsoft SQL Server 2014 NOTE: In a replicating scenario, SQL Server Express Edition is supported only for replication subscribers. The publisher server must be running SQL Server Standard Edition or greater. Security Both Windows Integrated Security and SQL Server security is supported. NWS technicians will configure the application to connect using the organisation s preferred security method. If SQL Server security is chosen, the application will connect to the database using a single user ID. NOTE: If replication is to be configured, the Central Server (see below) must be configured to allow SQL Server logins in addition to Windows logins. Users connecting to the database should be granted the db_owner role within the database, as the application must be able to create database objects. The VIEW SERVER STATE server privilege is also required. Tech Notes Page 3 of 6

4 Replication Configuration Replication of data between a central database and one or more remote databases may be required in some cases. When configured, SQL Server replication will perform data synchronisation at regular intervals. If required, replication will be configured by NWS in consultation with IT staff during system installation. SQL Server replication is highly flexible and allows for many different configurations. This section provides an overview of the preferred replication configuration for. This configuration uses Merge Replication as the replication method. The diagram below illustrates a typical replicating scenario. The top of the diagram shows a Central Server which contains the master database in the system. The Central Server is known as a Publisher and is typically located at a central administration site. The lower section of the diagram shows a Remote Server, which exists at another location. A Remote Server is also known as a replication Subscriber. There may be many Remote Servers but only one Central Server. NOTE: A dedicated site server is not necessarily required at the remote site. In some cases, a weighbridge PC may be used, especially if SQL Server Express Edition is being used. Weighbridge PC Weighbridge PC Admin PCs Driver Control Station Driver Control Station LAN Central Server Network Link Remote Server LAN Weighbridge PC Admin PC Driver Control Station Tech Notes Page 4 of 6

5 The diagram below shows the replication layout with respect to general data movement between the sites. Central Database (Publisher) Customers, Products, etc. Transactions This diagram illustrates the following: Remote Database (Subscriber) The Subscriber enters transactions. Transactions entered at the Publisher on behalf of the remote site will also replicate out to the remote database. Each remote database typically contains only its own transactions. The Publisher enters and modifies non-transaction data, e.g. customers, products or vehicles. The Subscriber may also create or modify these, although this is less common. Synchronisation At a preset interval, the Remote Server will initiate synchronisation with the Central Server. This results in data changes being transferred between the remote database and the central database. Transaction data and non-transaction data are synchronised separately. The remote subscription will be configured as a Pull Subscription. This results in the Remote Server performing the synchronisation work, which reduces the load on the Central Server. It also allows a application to initiate synchronisation if required, without needing to connect directly to the Central Server. Windows User Account Requirements When replication is required, SQL Server must be configured to run under the context of user accounts with network permissions. User accounts are at the organisation s discretion, but in the absence of any special requirements the following domain user IDs are requested: User Account Name NWS_SqlServer NWS_SqlRepAgent Intended Purpose SQL Server / SQL Server Agent service account Replication agents Passwords for the user accounts are at the organisation s discretion but will be recorded by NWS for support purposes. The user accounts created should not force the passwords to be changed regularly as this may cause replication to stop. If passwords need to be changed for audit purposes this should be carried out manually in a co-ordinated fashion. Tech Notes Page 5 of 6

6 SQL Server Service Account (NWS_SqlServer) Permissions Ideally, the SQL Server service account should be added to groups that are created by the SQL Server installation. This will ensure that the user account has the required access to local resources as the access required for each group is configured during the MSSQL installation. The groups will be domain-wide groups if the server running SQL Server is a domain controller, or local groups otherwise. There is no requirement for the user account to have Administrative privileges on any server. Replication Agent User Account (NWS_SqlRepAgent) Permissions The Replication Agent user account should be a member of the standard Domain Users group. There is no requirement for the user account to have Administrative privileges on any server. The configuration of replication will require a snapshot folder to be set up. This will typically be a shared folder somewhere on the network. The Windows account under which the snapshot agent runs must have write access to the share, and the Windows account under which the merge agent runs must have read access to the share. As the Replication Agent user account will be used for both agents, granting these permissions to the Replication Agent user account will be sufficient. SQL Server User Account Requirements By default, the partitioning of data between remote subscribers is performed by running the merge agent under a SQL Server user account created for each site. This will require the Central Server (Publisher) to be configured to allow SQL Server User Accounts in addition to Windows User Accounts. The SQL Server User Account names are typically based on the remote sites configured in during system installation. The accounts required will be created by NWS during the installation, in consultation with IT staff. END OF DOCUMENT Tech Notes Page 6 of 6