System Administration Guide
Novar
6.0.x
March 2015
Delivering the Moment
Publication Information
© 2015 Imagine Communications Corp. Proprietary and Confidential.
Imagine Communications considers this document and its contents to be proprietary and confidential. Except
for making a reasonable number of copies for your own internal use, you may not reproduce this publication,
or any part thereof, in any form, by any method, for any purpose, or in any language other than English
without the written consent of Imagine Communications. All others uses are illegal.
This publication is designed to assist in the use of the product as it exists on the date of publication of this
manual, and may not reflect the product at the current time or an unknown time in the future. This
publication does not in any way warrant description accuracy or guarantee the use for the product to which it
refers. Imagine Communications reserves the right, without notice to make such changes in equipment,
design, specifications, components, or documentation as progress may warrant to improve the performance
of the product.
Trademarks
Product names and other brands are trademarks or trade names of Imagine Communications or its
subsidiaries. Microsoft® and Windows® are registered trademarks of Microsoft Corporation. All other
trademarks and trade names are the property of their respective companies.
Contact Information
Imagine Communications has office locations around the world. For locations and contact information see:
http://www.imaginecommunications.com/contact-us/.
Support Contact Information
For support contact information see:


Support Contacts: http://www.imaginecommunications.com/services/technical-support/
eCustomer Portal: http://support.imaginecommunications.com
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Novar™ 6.0.x
System Administration Guide
Contents
Contents
Administration .......................................................................................................... 6
Overview.................................................................................................................6
Technical Support ...................................................................................................6
Reporting Incidents via Client Extranet .....................................................6
Hardware Administration........................................................................................... 7
Hardware Prerequisites ..........................................................................................7
External Communication ...........................................................................7
Backup Unit ...............................................................................................8
Disk Drives .................................................................................................8
Network Resources ...................................................................................9
Computer (PC) Hardware ..........................................................................9
Insertion Hardware and Control Software ...........................................................10
System Sizing Metrics .............................................................................................. 10
Supported Software Systems ................................................................................... 11
Supported Operating Systems..............................................................................11
Workstations, ZIP Stations and Novar Services Platforms ......................11
Application/SQL Servers ..........................................................................12
Supported Database Systems ...............................................................................13
Novar Database Systems .........................................................................13
Report Management System (RMS) Database Systems..........................14
SQL Server Hardware Limitations .........................................................................14
SQL Server 2008 Maximums for Editions by Operating System..............14
Hardware Requirements and Recommendations ...................................................... 15
Interaction Diagram..............................................................................................16
Novar High Availability .........................................................................................17
Limitations ...............................................................................................18
Facts about SQL Server on a Failover Clustered Environment ................18
User Workstations ................................................................................................19
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page i of 67
Novar™ 6.0.x
System Administration Guide
Contents
ZIP Stations and Novar Services Platforms ...........................................................19
ZIP Station................................................................................................19
Novar Services Platform ..........................................................................19
Virtualization ...........................................................................................20
Application/SQL Server.........................................................................................21
Virtualization ...........................................................................................21
Web/Reporting Servers ........................................................................................22
Novar Report Management System (RMS) Server ..................................22
Gatekeeper™ eBusiness Order Exchange™ (eBOX) Web Server .............23
Novar Remote Office Systems (RSS/RAS) Servers ...................................23
Services / Applications Compatible with Same Server / Hardware ........25
Software Administration .......................................................................................... 27
Client (PC) Installation ..........................................................................................27
Existing Environment...............................................................................27
New Environment....................................................................................27
SQL Server (DB) Installation..................................................................................28
Single-User Implementations ..................................................................28
Standard (Multi-user) Novar Implementations .......................................28
Novar Database Installation / Upgrade ................................................................28
Database Administration ......................................................................................... 29
Overview...............................................................................................................29
Pre-Implementation Tasks ...................................................................................29
System Configuration ..............................................................................30
Perform Backups ..................................................................................................30
Run Integrity Checks .............................................................................................31
Maintain Indexes ..................................................................................................31
Review Error Logs .................................................................................................32
Manage SQL Server Agent Jobs ............................................................................33
Test Backups .........................................................................................................34
Monitor Performance ...........................................................................................34
Document SOP Processes .....................................................................................35
Create and Test Disaster Recovery Plans .............................................................36
Manage Security ...................................................................................................36
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page ii of 67
Novar™ 6.0.x
System Administration Guide
Contents
Test Connectivity and Availability ........................................................................37
Conclusion ............................................................................................................38
Database Tuning ...................................................................................................... 38
TempDB Tuning ....................................................................................................38
Novar Archive Database ..........................................................................39
Creating Multiple TempDB Data Files .....................................................39
Implementing Trace Flag 1118 ................................................................43
Implementing Trace Flag 1222 ................................................................44
For More Information..............................................................................46
Database Contention Settings for Sql Server 2008 R2 .........................................46
Memory Management .........................................................................................47
Disk I/O Tuning ........................................................................................48
Torn Page Detection ................................................................................48
Novar Database Maintenance Tasks ......................................................................... 49
Overview...............................................................................................................49
Database Backups.................................................................................................49
Novar Database Backup - Full, Daily ........................................................49
Novar Log Backup - Incremental, Current ...............................................50
Table (and Calculated Values) Maintenance ........................................................63
(Novar) Conline Projection Update - Periodic .........................................63
(Novar) Table Maintenance - Nightly ......................................................63
(Novar) Table Maintenance - Weekly......................................................64
Acronyms ................................................................................................................ 65
Glossary .................................................................................................................. 66
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page iii of 67
Novar™ 6.0.x
System Administration Guide
Administration
Administration
Overview
This document contains information on the administration of Novar™ systems, which encompasses
Add-On products such as the Report Management System™ (RMS), etc. This information is intended
as a guide. For additional assistance please contact Technical Support.
Technical Support
Please contact Imagine Communications Technical Support for information regarding this release:

Phone Number: 303.476.5066

Fax Number: 303.390.8100

Email Address: broadbandsupport@imaginecommunications.com
Reporting Incidents via Client Extranet
The Imagine Communications Customer Portal allows sites to create and track service requests.
Organizations can also access support issues related to their products. For complete registration and
usage instructions, please refer to the document “eCustomer Portal Registration Help”
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 6 of 67
Novar™ 6.0.x
System Administration Guide
Hardware Administration
Hardware Administration
NOTE
This document is updated as needed to reflect changes in technology – and other information –
as it becomes available, and is therefore subject to change without notice.
Hardware Prerequisites
Prior to the arrival of an Imagine Communications Client Services representative to install the
Novar™ system or Add-On software, the following prerequisites must be completed.

It is expected that all required computer hardware items will be in place, properly located,
fully tested, and completely functional before the Imagine Communications trainer arrives
on site.

Designate and train a person in your organization as the Network Operating System
Administrator for the Microsoft Windows operating system, and also as the Microsoft SQL
Server System Administrator.
RECOMMENDATION
Purchase service maintenance agreement(s) for the network and computer systems from the
hardware supplier(s). Imagine Communications does not operationally support computer or
network hardware or software.
External Communication
On occasion, Imagine Communications technical support will need to connect remotely to your
Novar system to troubleshoot and help resolve an issue.

Imagine Communications Technical Support uses remote web conference tools for support
and troubleshooting.

Imagine Communications Technical Support can also connect to your network over VPN, if
your environment and policies support those types of connections for vendors.
Regardless of the method of connectivity employed, it is important that a workstation is configured
for troubleshooting with both Novar and SQL Server tools (see SQL Server (DB) Installation, in this
document). This troubleshooting environment can be a ZIP Station or Novar Services Platform, but
should not be a daily user’s primary machine. Tool installation and required configuration should be
completed prior to initiating a support request.
Setting up a Novar troubleshooting environment and the SQL Server tools in advance enables
Imagine Communications Technical Support to focus on identifying and resolving your issue quickly,
without having to spend time configuring communications and tools before troubleshooting can
begin.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 7 of 67
Novar™ 6.0.x
System Administration Guide
Hardware Administration
Finally, a user account with Local Administrator privileges is required. Please contact Imagine
Communications Technical Support, if you have questions concerning remote connectivity and
administrator privileges.
Backup Unit
A backup unit is a safety net. Daily data backup is critical, and periodic verification of the data on
the backup medium must be performed. Imagine Communications will not accept responsibility,
financial or otherwise, for: the proper installation and configuration of your backup unit; backup
procedures related to, and the actual performance of, the daily backup; or the verification and
integrity of the data on your backup medium.
An external USB 2.0 Hard Drive of sufficient size to hold a copy of your SQL backup is a readily
available and relatively inexpensive device to keep on hand. This device can be used for a variety of
purposes, to include transferring a copy of your database to Imagine Communications for
troubleshooting or testing.
RECOMMENDATIONS

Purchase of the most appropriate, reliable, data backup unit you can afford for performing
daily backups.

Purchase an External USB 2.0 Hard Drive large enough to hold a copy of your Novar DB.
NOTE
Imagine Communications does not support receiving copies of data in any tape formats.
Disk Drives
Drive-space requirements are based on general usage and size of operation. Unless otherwise
specified, the drive size specified is the minimum requirement. RAID Level recommendations are
determined by the relative size and type of operation. RAID Levels are described as follows:

RAID 1: This level uses mirrored drives and provides fault tolerance. Data is duplicated on
the paired drives. Reads are made from either drive in a pair.

RAID 5: Data as well as parity information is distributed (striped) across several drives. This
level is used primarily for the main SQL data storage for improved fault tolerance. The SQL
Data and SQL Log files should be on their own RAID arrays with separate controllers
whenever possible.

RAID 10: Data as well as parity information is distributed (striped) across several mirrored
drives. This level is used primarily for the main SQL data storage and provides fault tolerance
and improved performance. The SQL Data and SQL Log files should be on their own RAID
arrays with separate controllers whenever possible.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 8 of 67
Novar™ 6.0.x
System Administration Guide
Hardware Administration
Network Resources
The following requirements assume dedicated use of all resources. This includes servers and
network bandwidth. If other computers will share the same network, a router or switch must be
used to segment that traffic, and a separate server provided for their use.
For Novar, a bandwidth of 100Mb is required covering the entire path from workstation(s) to the
database server (a 1 Gb backbone is recommended between the SQL Server and Switches, and on to
Novar Services platforms).
Any necessary Network Operating System training for your operators must be accomplished prior to
our arrival. If training delays occur as a result of discrepancies related to the above, Imagine
Communications will bill you for any additional time required on site by the trainer, and additional
transportation expenses if applicable.
Please contact Technical Support with any questions regarding this requirement.
Network and Workstation Printers
A Print Server is typically a computer or server on the network with printers attached to it and
generally facilitates printing for the entire network.

Color inkjet printers and / or dot-matrix printers are not recommended for primary print
tasks.

A color printer however can be used for printing inventory graphs associated with Novar and
some of its related products.

Always check with the hardware vendor to ensure that the printer is compatible with your
Windows operating system’s printer drivers.
NOTE
Intel, Hewlett-Packard, and numerous other corporations manufacture single-purpose Print
Servers, which eliminate the need for a separate computer or server on the network to provide
this functionality.
RECOMMENDATIONS

A dedicated Print Server is recommended for network printing.

Imagine Communications strongly recommends using laser printers for Novar print jobs.
Computer (PC) Hardware
To help ensure compatibility, please review specific models and characteristics with Imagine
Communications prior to purchase.
The decision to purchase a particular brand or type of computer rests entirely with you.
In all instances, regardless of computer brand or type, Imagine Communications will not accept
responsibility, financial or otherwise, for any occurrence of computer hardware or software failure.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 9 of 67
Novar™ 6.0.x
System Administration Guide
System Sizing Metrics
Insertion Hardware and Control Software
Imagine Communications cannot and will not assume responsibility:

For any failures relating to insertion hardware at the head end

For the inability of that vendor's control software to properly function within the computer
system selected to operate the Novar System.
NOTE
The selection process for the purchase of computer hardware must always include confirmation
by the insertion hardware vendor that full compatibility exists with their control software.
System Sizing Metrics
There are varying computer hardware and software requirements for Novar operations. The primary
metric used to scale the hardware is active channel count. Your account representative may modify
these base recommendations to help you achieve optimal performance. Basic sizing categories
include:

Single User (Very few active channels with a single T/B operator)
WARNING
Single-user systems are permitted to use versions of Microsoft SQL Server that come
with significant restrictions. Clients should review those restrictions and ensure they
are comfortable with them prior to implementation.

Multi-User (refer to table)
Active Channel
Count
System Size
SQL 2008 / 2012
Extra Small
Less than 200
Small
200 to 900
Medium
900 to 2400
Large
2400 to 4800
Extra Large
4800 to 7200
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 10 of 67
Novar™ 6.0.x
System Administration Guide
Supported Software Systems
Supported Software Systems
Supported Operating Systems
Workstations, ZIP Stations and Novar Services Platforms
6.0.x
WARNING
Imagine Communications Software Systems supports 64-bit Operating System for use with client
workstations, ZIP or Novar Services Platforms (such as Adaptive Scheduling (AdS)).
Novar requires Microsoft Windows 7 or Windows 8 for all workstations, ZIP Stations and Novar
Services Platforms. Windows 95, 98, ME, XP Home, XP Professional, and Vista are not acceptable for
use with any part of the Novar system.
NOTE

As XP is no longer supported by Microsoft, troubleshooting of Novar issues on XP will be
supported although enhancements or bug fixes for problems caused by Windows XP will
no longer be issued
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 11 of 67
Novar™ 6.0.x
System Administration Guide
Supported Software Systems
Application/SQL Servers
SQL Servers should be run on the Microsoft Windows Server operating system. Specific version/
edition requirements vary, see the table, below.
6.0.x
System
Size1
Operating System reference:
4
Required
Single User
2008 R2 SE
Extra Small
2008 R2 SE
Small
2008 R2
SE/2012
Medium
2008 R2
SE/2012
Large
2008 R2
EE/2012
Extra Large
2008 R2
EE/2012

2008 R2 SE – Microsoft Windows Server 2008 R2
Standard Edition SP2 (64 bit; match SQL)

2008 R2 EE – Microsoft Windows Server 2008 R2
Enterprise Edition SP2 (64 bit; match SQL)

2008 R2 SE/2012 –
o

Application Server : Microsoft Windows Server
2008 R2 Standard Edition SP2 (64 bit; match
SQL)
2008 R2 EE/2012 –
o
Application Server : Microsoft Windows Server
2008 R2 Enterprise Edition SP2 (64 bit; match
SQL)
NOTES
1. Refer to System Sizing Metrics
2. A higher edition, but not a higher version is acceptable.

Microsoft Extended Support is available for Windows 2003 R2 through July 2015
3. SQL 2008 R2 or 2012 is required for Novar versions 6.0 and higher. You should coordinate
your migration from Windows Server 2003 to 2008 with the migration from SQL Server 2000
to 2008.
4. Novar plans to test new versions of Microsoft Windows Server as they become available and
will announce compatibility for such subsequent to appropriate testing.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 12 of 67
Novar™ 6.0.x
System Administration Guide
Supported Software Systems
Supported Database Systems
Microsoft SQL Server is the only supported database system for Novar. Due to processor and
memory requirements, specific version/edition requirements vary, see the table, below.
Novar Database Systems
6.0.x
System Size1
Required2,4
Single User
2008 R2
WE/2012
Small
2008 R2
SE/2012
Medium
2008 R2
EE/2012
Large
2008 R2
EE/2012
Extra Large
2008 R2
EE/2012
Database System reference:

2008 SE – Microsoft SQL Server 2008 Standard Edition (64 bit; match OS)

2008 EE – Microsoft SQL Server 2008 Enterprise Edition (64 bit; match OS)

2008 WE – Microsoft SQL Server 2008 Workgroup Edition (64 bit; match OS)

2012 - Microsoft SQL Server 2012 (64 bit; match OS)
NOTES
1. Refer to System Sizing Metrics
2. A higher edition, but not a higher version is acceptable.
3. While running Novar 5.14.1 and 5.15, you will have the opportunity to upgrade your
database system to SQL 2008 R2 prior to upgrading to Novar 6.0; this will allow for
managed, stepped migration planning.
4. Novar plans to test new versions of Microsoft SQL Server as they become available and will
announce compatibility for such subsequent to appropriate testing.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 13 of 67
Novar™ 6.0.x
System Administration Guide
Supported Software Systems
Report Management System (RMS) Database Systems
The Report Management System™ (RMS) requires Microsoft SQL Server 2008 R2. Enterprise Edition
is required to support subscriptions.
SQL Server Hardware Limitations
Various editions of Microsoft SQL Server have different hardware-utilization limits:

CPU Utilization (Max)

RAM (Memory) Utilization (Max)
The tables below provide a cross-reference of Microsoft-provided data for the various versions and
editions of SQL Server and Windows Server operating systems.
SQL Server supports the specified number of processor sockets (Physical CPUs – “P”) multiplied by
the number of logical CPUs (L) in each socket. For example, each of the following is considered a
single physical processor for purposes of this table:

A single-core, hyper-threaded processor with 2 logical CPUs.

A quad-core processor with 4 logical CPUs.
SQL Server 2008 Maximums for Editions by Operating System
OS Edition
Windows Server
2008 R2 Standard
Workgroup
Standard
2 P1,2
4 P1
4 P1
4 P1
4 GB
32 GB
32 GB
32 GB
4P
8P
8P
64 GB
2 TB
2 TB
-N/A-
-N/A-
Windows Server
2008 R2 Enterprise
-N/A-
Windows Server
2008 R2 Data Center
-N/A-
Enterprise Data Center
64 P
2 TB
NOTES
1. P = Physical CPU; Logical CPUs (“Cores”) are no longer the controlling metric.
2. Limits apply to all operating systems; desktop operating systems are permitted
-N/A- = OS exceeds the capability of the selected SQL Server edition
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 14 of 67
Novar™ 6.0.x
System Administration Guide
Hardware Requirements and Recommendations
Hardware Requirements and
Recommendations
The requirements for Novar are divided into seven components:

User Workstations

ZIP Stations and Novar Services Platforms

Application/SQL Server

Report Management System (RMS)

Gatekeeper eBusiness Order Exchange (eBOX)

Novar Remote Office Systems (RSS/RAS)

Novar Provider/Client (MIS)
The recommended minimum configurations are listed for each, as well as any preferences based on
knowledge and experience with various operations.

All machines should support color monitors with a minimum resolution of 1024 x 768.

All machines should have mouse / keyboard / monitor access – KVMs are acceptable.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 15 of 67
Novar™ 6.0.x
System Administration Guide
Hardware Requirements and Recommendations
Interaction Diagram
Illustration of the Novar System hardware
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 16 of 67
Novar™ 6.0.x
System Administration Guide
Hardware Requirements and Recommendations
Novar High Availability
SQL Server includes many technologies that can be used to minimize downtime and maximize data
protection to ensure smooth operation, continuous access to business critical data, and meet almost
zero downtime availability levels.
To provide High Availability for Novar application, the SQL SEVER Failover Clustering was chosen.
Failover Clustering is a technology that allows an entire SQL Server instance to be made highly
available – either at the local data center or possibly at a remote site or data center. An SQL Server
failover cluster is implemented on a Windows Server failover cluster. The following is the high level
architecture diagram of Failover Cluster.
Cluster
Node 1
Cluster Service – SQL
Instance, MSDTC
Node 2
Shared Storage /
Clustered Disk
NOTE
Imagine Communications is not responsible for supporting either Windows or SQL clustering;
assistance will be available only for the NOVAR installation on an existing clustered
environment.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 17 of 67
Novar™ 6.0.x
System Administration Guide
Hardware Requirements and Recommendations
Limitations
The Novar High Availability solution is limited to the database clustering and is certified for SQL
Server 2008 R2 and above versions only. The Database and Server requirements will be the same as
for standalone installations of NOVAR, subject to any additional requirements on which Clustering is
dependent. Installation of Windows Clustering services, SQL Server Database Clustering, and
combining other High Availability/Disaster Recovery solutions is beyond the scope of this document.
Facts about SQL Server on a Failover Clustered Environment

Clustering is designed to boost the availability of physical hardware, the Operating System,
and the SQL Server service (or any other clustered service)

Clustering can help reduce the downtime to a minimum during the maintenance of cluster
nodes like change of hardware, apply new service pack to the operating system, etc.

Clustering will not provide data redundancy in case of shared disk failure

Clustering will not reduce the downtime to zero. It can mitigate the downtime but cannot
eliminate it. For example, the failover itself can cause an outage of thirty seconds to a few
minutes. With that said, clustering is one of the best High Availability technologies

Clustering is not designed to protect data. Data should be protected using other SQL Server
technologies like Backup

Failover Clustering is not load balancing
NOTE
Additional information for SQL Server Cluster setup:


http://msdn.microsoft.com/en-us/library/ms179410(v=sql.105).aspx
http://download.microsoft.com/download/6/9/D/69D1FEA7-5B42-437A-B3BAA4AD13E34EF6/SQLServer2008FailoverCluster.docx
SQL scripts to validate the cluster and participating nodes
1. Confirm if the SQL Instance is Clustered and get the Active Node name
SELECT SERVERPROPERTY('Edition') Edition
,SERVERPROPERTY('ProductVersion') ProductVersion
,SERVERPROPERTY('IsClustered') IsClustered
,SERVERPROPERTY('ComputerNamePhysicalNetBIOS') ActiveNode;
2. Show the participating Node name of the cluster.
SELECT NodeName
FROM sys.dm_os_cluster_nodes;
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 18 of 67
Novar™ 6.0.x
System Administration Guide
Hardware Requirements and Recommendations
User Workstations
This section specifies the workstation requirements for each person using the Novar application.
User Workstation Requirements
Unit
1
1
1
1
1
Description
CPU - Multi-Core
20GB Free Space on Hard (Drive Minimum)
2GB RAM Minimum; 4 GB Recommended
Windows 7/8 Professional Edition
Network Interface Card – 1 Gb Ethernet
ZIP Stations and Novar Services Platforms
The same hardware can serve as either a ZIP Station or Novar Service Host (such as an Adaptive
Scheduling (AdS) Plotter platform).
ZIP Station
The intended function of the ZIP Station is to distribute processing loads from the application server
to less expensive workstation hardware.
NOTE
Although ZIP Stations run Novar applications in a non-interactive mode; an active login session is
required (Console or RDP).
Novar Services Platform
Novar Services Platforms run Windows Services including:

Enhanced Network Programming (ENP) Sync Service

Novar/MIS Integration Service

Adaptive Scheduling (AdS) services.
Adaptive Scheduling (AdS) systems require additional computer hardware – specifically set up to
continuously monitor contract activity and update the Novar schedule as needed. These AdS
Services computers are in addition to the Novar hardware specified previously.

Plotter Services

Channel Status Service
While Imagine Communications recommends using one computer for each AdS Service that is
installed; other factors can be considered when determining the system’s hardware needs.

Scaling – Imagine Communications recommends installing one AdS Plotter (machine) for
each 300 active channels. (Channel = one network in one zone.)
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 19 of 67
Novar™ 6.0.x
System Administration Guide
Hardware Requirements and Recommendations

A minimum of two AdS Plotters is recommended – regardless of system size.

The maximum number of AdS Plotters should not exceed the number of logical
processors on the SQL Server.
WARNING
Sites have experienced performance degradation when the number of AdS Plotters
exceeded the number of logical processors on the SQL Server. Therefore, it is strongly
recommended that the number of active AdS Plotters never exceed the total number of
SQL Server logical processors.

Co-locating – Several of the AdS services may be co-located on the same computer. The
following co-location combinations (or sharing of a single machine/instance) are currently
supported:
o
AdS Plotter and ENP Sync (not recommended for large/extra-large systems)
o
AdS Plotter and Channel Status (not recommended for large/extra-large
systems)
Virtualization
ZIP Stations and Novar Services Platforms may be virtualized. There will be no impact on support for
Novar issues for virtualized ZIP Stations and/or Novar Services Platforms. Please feel free to
consolidate hardware utilized for these purposes; however, the minimum hardware requirements
listed below still apply, on a per instance basis.
The minimum requirements for each machine/instance are:
Requirements for a ZIP Station or Novar Services Platform
Unit
1
1
1
1
1
Description
CPU - Multi-Core
20GB Free Space on Hard (Drive Minimum)
2GB RAM Minimum; 4 GB Recommended
Windows 7/8 Professional Edition or Windows Server
Network Interface Card – 1 Gb Ethernet
NOTES

When ZIP Stations or Novar Services Platforms are run on Blade or Virtual Servers the
requirements listed above are per Blade/VM.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 20 of 67
Novar™ 6.0.x
System Administration Guide
Hardware Requirements and Recommendations
Application/SQL Server
SQL Server is very disk input/output (I/O) intense. To achieve the optimum performance, set up
separate disk/array controllers and separate disk arrays for the Operating System, the SQL Data file,
the SQL Log file, and TempDB (Data and Log together).

None of the database files should be co-located with the Operating System.

A distinct I/O channel should exist for each of the storage areas listed above.

In non-AdS environments, limit each server to a maximum of 2000 channels.

The use of Ultra-320 SCSI drives is recommended for all Large and Extra Large systems.
To avoid potential confusion regarding physical CPUs, logical CPUs, and hyper-threaded (HT) CPUs,
we will use the word cores. This is intended to represent the sum total of elements capable of
independent processing. For example:

2 dual-core CPUs = 4 cores

4 quad-core CPUs = 16 cores, etc.
Novar Minimum Database Server Requirements
Max
Channel
Count
Min
Core
Count
Min
RAM
GB2
Min
Disk
GB3
Operating
System
Single-User
200
2
4
400
2008 SE
2008 R2
WE/2012
Small
900
4
16
800
2008 SE
2008 R2
SE/2012
Medium
2400
8
32
2400
2008 SE
2008 R2
SE/2012
Large
4800
16
64
4200
2008 EE
2008 R2
EE/2012
Extra-Large
7200
24
128
6000
2008 EE
2008 R2
EE/2012
System
Size1
SQL Server
Novar 6.0 and Later
NOTES
1.
Refer to System Sizing Metrics
2.
Edition assumes quad-core physical CPUs; see also SQL Server Hardware Limitations
3.
Minimum Disk Space for the SQL Server Data and Log Files only; based on client averages
Virtualization
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 21 of 67
Novar™ 6.0.x
System Administration Guide
Hardware Requirements and Recommendations
SQL Server 2008 R2 / 2012 database servers may be virtualized. There will be no impact on support
for Novar issues for virtualized SQL 2008 R2 / 2012 servers. Please feel free to conduct testing and
migrate your servers to virtualized hardware; however, the minimum hardware requirements listed
above still apply, on a per instance basis.
Web/Reporting Servers
Novar Report Management System (RMS) Server
This section covers hardware requirements for a Novar Report Management System (RMS). RMS is
based on Microsoft SQL Server Reporting Services and requires:

SQL 2008 R2

Microsoft Windows Server 2008 R2 with IIS Web Server 7.5.
RMS Server Requirements
Unit
1
1
1
1
1
1
Description
Quad Processor - P4 3.0Ghz
200GB Free Space on Hard Drive Minimum, Net of RAID
4GB RAM Minimum
Microsoft Windows Server 2008 R2 with IIS 7.5
Microsoft SQL Server 2008 R2
Network Interface Card - Gigabit Ethernet
NOTE

The use of the word processor is not intended to be interpreted as meaning a physical CPU.
Multi-core CPUs are acceptable (for example, 2 dual-core CPUs = 4 processors).

RMS Server is certified on SQL 2008 and not on SQL 2012

RMS will no longer support SQL 2005 from 6.0.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 22 of 67
Novar™ 6.0.x
System Administration Guide
Hardware Requirements and Recommendations
Gatekeeper™ eBusiness Order Exchange™ (eBOX) Web Server
This section covers hardware requirements for Novar’s Gatekeeper eBusiness Order Exchange
(eBOX)™ application. The eBOX application is based on Microsoft IIS and requires:

Microsoft Windows Server 2008 R2 with IIS 7.5

Microsoft .Net Framework 2.0 (SP 2)
eBOX Server Requirements
Unit
1
1
1
1
1
Description
Quad processor* P4 3.0GHz
50MB Free Space on Hard Drive Minimum, Net of RAID
4GB RAM Minimum
Microsoft Windows Server 2008 R2 with IIS 7.5
Network Interface Card - Gigabit Ethernet
NOTE
The use of the word processor is not intended to be interpreted as meaning a physical CPU.
Multi-core CPUs are acceptable (for example, 2 dual-core CPUs = 4 processors).
Novar Remote Office Systems (RSS/RAS) Servers
This section covers hardware requirements for sites that are self-hosting web servers for the Novar
Remote Office systems: Remote Sales System (RSS) and Remote Accounting System (RAS).
Remote Office applications are based on Microsoft IIS and require:

Software FX – Chart FX 2000 IE Graphics Software (single CPU license)

Crystal Reports Professional V 9.0 or higher (for RAS only)
There are varying computer hardware requirements for remote-office operations. The primary
metric used to scale the hardware is the user count. Your account representative may modify these
base recommendations to help you achieve optimal performance.
Basic remote-office sizing categories include:

Small (Less than 20 users)
Small Remote Office Server Requirements
Unit
1
1
1
1
1
Description
2 Processor 3.0GHz
10GB Free Space on Hard Drive Minimum, Net of RAID
1GB RAM Minimum
Microsoft Windows Server 2008 SP2 IIS 7.5
Software FX – Chart FX 2000 IE Graphics Software
(single CPU license)
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 23 of 67
Novar™ 6.0.x
System Administration Guide
Hardware Requirements and Recommendations
Small Remote Office Server Requirements
Unit
1

Description
Network Interface Card - Gigabit Ethernet
Large (20 or more users)
Large Remote Office Server Requirements
Unit
1
1
1
1
1
1
Description
4 processor 3.0GHz
10GB Free Space on Hard Drive Minimum, Net of RAID
2GB RAM Minimum
Microsoft Windows Server 2008 R2 with IIS 7.5
Software FX – Chart FX 2000 IE Graphics Software
(multiple CPU license)
Network Interface Card - Gigabit Ethernet
NOTE
The use of the word processor is not intended to be interpreted as meaning strictly physical
CPUs. Multi-core CPUs are acceptable (for example, 2 dual-core CPUs = 4 processors).
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 24 of 67
Novar™ 6.0.x
System Administration Guide
Hardware Requirements and Recommendations
Services / Applications Compatible with Same Server / Hardware
The table below lists the combination of services and applications that can run on the same server
or hardware:
Services / Applications that can run on the same
Server / Hardware
File
Server
SQL
Server
eBOX
Plotter
Channel
Status
Enp RMS
Sync
Service
RO
Zip
Station
N/A








SQL
Server

N/A







eBOX


N/A






Plotter
Service



N/A





Channel
Status
Service




N/A




ENP Sync
Service





N/A



RMS






N/A


RO







N/A

Zip
Station








N/A
File Server
NOTE
The values in the grid denote the following:
 – Valid
 – Invalid
NA – Not Applicable

The SQL Server and file server can be shared, but only on small systems.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 25 of 67
Novar™ 6.0.x
System Administration Guide
Hardware Requirements and Recommendations

Medium and larger systems should use a separate piece of hardware, so that the database
engine has full access to the network interface.

Medium and larger systems cannot be shared with any other services listed in the preceding
grid.

Please click the following link to refer to the server requirements:
Novar Minimum Database Server Requirements
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 26 of 67
Novar™ 6.0.x
System Administration Guide
Software Administration
Software Administration
Client (PC) Installation
For complete client installation instructions, please refer to the “Install Instructions 6.0” document
that is appropriate for your site.
Existing Environment
The following steps will need to be performed on each workstation:
1. Log on as the Administrator.
2. Use Add/Remove programs to uninstall the Novar Core Components.
3. Use Add/Remove programs to uninstall Novar.
4. Go to the New Client\Workstation Setup subfolder:

Double click on setup.exe to install Novar workstation files.

Double click on UIBlock.Windows.msi to repair the Imagine Communications UI
Block (Window Forms) files.
5. Go to the New Client\Novar subfolder.

Double click on NovarCore.msi to install Novar Core Components.

Double click on SecuritySetup.bat to install components for .Net applications.
6. Verify access to Novar by double clicking on the novexec.exe in the New Client\Novar
subfolder.
7. (Optional) Create a Novar shortcut on the desktop for the novexec.exe file.
a. Right click and select Send To
b. Select Desktop
New Environment
The following steps will need to be performed on each workstation:
1. Log on as the Administrator.
2. Map a shared drive to the New Client folder.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 27 of 67
Novar™ 6.0.x
System Administration Guide
Software Administration
3. Go to the New Client\Workstation Setup subfolder:

Double click on setup.exe to install Novar workstation files.

Double click on UIBlock.Windows.msi to install the Imagine Communications UI
Block (Window Forms) files.
4. Go to the New Client\Novar subfolder.

Double click on NovarCore.msi to install Novar Core Components.

Double click on SecuritySetup.bat to install components for .Net applications.
5. Create a Novar shortcut on the desktop for the novexec.exe file.
a. Right click and select Send To
b. Select Desktop
6. Verify Access to Novar by double clicking on the Novar icon on the workstation desktop
SQL Server (DB) Installation
NOTE
With the release of Novar version 6.0, SQL Server 2008 R2 / 2012 will be required.
Single-User Implementations
Novar Version 6.0 and Later
You will need Microsoft SQL Server 2008 (R2 recommended) Workstation Edition. Be certain you
select the correct version (64-bit) to match your operating system.
Standard (Multi-user) Novar Implementations
Novar Version 6.0 and Later
You will need Microsoft SQL Server 2008 (R2 recommended). Be certain you select the correct
version (64-bit) to match your operating system. The correct edition can be found in Novar
Minimum Database Server Requirements.
Novar Database Installation / Upgrade
For complete client installation instructions, please refer to the most current “Install Instructions
6.0.x” document.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 28 of 67
Novar 6.0.x
System Administration Guide
Database Administration
Database Administration
The administration and operation of Microsoft SQL Server database applications is a partnership
between Imagine Communications and our clients. The administration of the database is critical to
the performance of the Novar application and is, as always, an on-going effort. Imagine
Communications provides the following information as a service to help our clients better capitalize
on their investment. This information has been:

Culled from multiple public sources;

Gleaned from the varied experiences of our employees and;

Gathered from the many different operating practices of our business partners.
The items contained in this section are considered to be the responsibility of our client partners.
Imagine Communications provides this supplemental information to assist in the planning and
successful operation of the Novar database.
Overview
For both new and experienced database administrators (DBAs), there are fundamental procedures
that will need to be addressed. Proper processes should be implemented to handle various areas of
database management for SQL Server. Whether the organization employs a full-time DBA or assigns
this role to the IT staff, the same basic steps should be implemented, and adhered to, in order to
ensure a healthy running SQL Server environment.
For experienced DBAs these items should be a “no-brainer”. This information can therefore serve as
a checklist (or a good reminder to make sure everything is in place). For newer DBAs, some of these
basic items may not be readily apparent – as some of the most basic DBA 101 items are sometimes
overlooked.
The following checklist items should be in place for all of your SQL Server database servers. Some of
these items are very basic and easy to implement, while others require a higher level of effort to
think through what is needed and then to implement the process.
These items are not written in any priority order, and should not be considered a comprehensive
database-management plan for your site. Use this document as a guide for determining, addressing
and implementing a plan that is appropriate for the specific needs of your system.
Pre-Implementation Tasks
Prior to installing a database on a new server, take advantage of the opportunity to properly
configure the system, establish backup and maintenance plans, and document the system. Physical
systems should be reviewed and tested as well.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 29 of 67
Novar 6.0.x
System Administration Guide
Database Administration
System Configuration

Install and Configure SQL Mail.


Automate Maintenance and Logging


Create SQL Server email alerts to notify administrators of potential problems, which
enable them to take the needed actions quickly.
Set up SQL Server Agent to process all possible maintenance and logging tasks.
Document the System

Create paper or electronic documentation on the system state, and check it into the
change-control management system.

Install latest Service pack

Set Cost Threshold for Parallelism to 25

Place Log and Data files on separate drives.

Make sure Anti-virus scan skips DB files

Power saver is set to high in boot.ini, to take advantage of maximum computing power
of the server.

Set compatibility level to 100 (SQL Server 2008 R2)
Perform Backups
This is one of the most basic items to be addressed. Everyone knows that a good solid backup plan
should be in place for all databases. Imagine Communications staff members have however
encountered the situation (time and time again) where the wrong or no backup plan was in place for
the servers.
To determine which type of backup is needed, answer the following questions:

What are you trying to recover from when a failure occurs?

How much data can be lost? A day, one hour, a week, none.

What kind of processing occurs, transaction-based, batch-loading, a combination?

Can the data be easily recreated if there is a failure or is this the only source of the data?
While this is just a short list of questions to ask; once answered, the administrators can better
determine; 1) the recovery model for the database; and 2) the backup needs.
Depending on the answers, the backup plan may look like one of the following:

Daily full backups, or

Daily full backups and transaction-log backups every hour, or

Daily full backups, transaction log backups every 15 minutes and differential backups every
four hours, etc.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 30 of 67
Novar 6.0.x
System Administration Guide
Database Administration
RECOMMENDATIONS



Start with at least full daily backups.
If data is very important and cannot be easily recreated, change the database recovery
model to Full and implement both full and transaction-log backups.
Daily Task – Confirm backups have been made and successfully saved to a secure
location.
Run Integrity Checks
Integrity of the data is another area that should be addressed. SQL Server offers a few options to
address this that include DBCC CHECKDB, DBCC CHECKTABLE, DBCC CHECKALLOC, etc.
These commands check the allocation, structure and logical integrity of all objects in the database.
In addition to running these commands either through maintenance plans, maintenance jobs or via
a query window, system administrators also need to analyze the data for any integrity issues that
need to be addressed. Once again, Imagine Communications staff members have encountered the
situation where the commands are run via maintenance jobs, but no one ever reviews the reports to
see if there are any issues that need to be addressed.
While, for the most part, these integrity issues pop up a lot less than they did with earlier versions of
SQL Server; this is an item that should still be part of the DBA checklist.
RECOMMENDATIONS
One-Time Task – Create scheduled task(s) to execute DBCC commands that output to text file.
Periodic Tasks –



In off-peak hours, run the database consistency checker commands.
(Many options are available that provide varying degrees of automation.)
Review the output. If more than the usual messages appear, research the error(s) in
Books Online or your favorite search engine.
Run the SQL Server Best Practices Analyzer on each of the server’s instances.
Maintain Indexes
Indexes are those helpful pointers that allow quick access to data pages in the database. When
indexes are first created, the structure is nice and clean and everything works efficiently because the
data is accessed via the index instead of having to scan the entire table.
Over time however these helpful indexes become fragmented and take up unnecessary space.
Accessing the data pages is not as efficient as it was when the indexes were first created. This is
when periodic index maintenance becomes a critical DBA process.
Novar installs nightly and weekly index maintenance tasks to the Sql Agent service that must be
active.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 31 of 67
Novar 6.0.x
System Administration Guide
Database Administration
Administrators also have the option of doing index maintenance along with the back-up plan.
Based on how the index was created and how data is applied to the table or index, some indexes will
become fragmented while others may never have an issue. Therefore, implementing an across-theboard methodology of index management may waste time and server resources by needlessly
indexing tables that do not need it.
Review Error Logs
There are several logging mechanisms that SQL Server uses to record errors and other system
information. The most commonly used is the SQL Server Error Log. This error log provides startup
information, integrity-check information, backup information, etc., as well as information on any
SQL Server errors that occur. The SQL Server Agent log is another SQL Server logging mechanism
that is available to system administrators.
In addition to these internal SQL Server logs, the Windows Event Log provides errors and other
information that is not recorded to the SQL Server logs.
Reviewing the logs should be part of a daily routine for checking the health of the system. There are
tools available to automate the alert process when an error occurs, or administrators can add it as a
daily (manual) checklist item. Either way, the error logs should be reviewed each day.
RECOMMENDATIONS
Daily Tasks –

Check SQL Server Logs for unusual events. Options include:

Using SSEM:

Select <ServerName> | Management | SQL Server Logs | Current

Double click entry in right panel for more information
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 32 of 67
Novar 6.0.x
System Administration Guide


Database Administration
Using SSMS:

Select <ServerName> | Management | SQL Server Logs

Double click Current in right panel

Select entry in Log File Summary for more information
Check Windows Event and Application Logs for unusual events. Options include:
 Using Control Panel:

Select Administrative Tools | Event Viewer

Click Log to review

Double click entry in right panel for more information
Manage SQL Server Agent Jobs
SQL Server's built-in, job scheduling tool is a great tool for automating backups, index rebuilds,
integrity checks, etc. This tool gives administrators the ability to schedule the running of these jobs
during off hours.
Administrators are still responsible for monitoring job success and failure, which can always be
automated by setting up SQL Mail to have failure messages sent to operators.
Take the time on a daily basis to check for job failures and address any issues in a timely manner.
RECOMMENDATIONS
Daily Tasks –

Verify that all scheduled jobs have run successfully. Options include:
 Using SSEM:
 Select <ServerName> | Management | SQL Server Agent | Jobs
 Select failed job; right click and select View Job History…
 Select the Show Step Details check box for more information
 Using SSMS:
 Select <ServerName> | SQL Server Agent | Jobs
 Right click Jobs; Select View History
 Expand failed job in Log File Summary for more information
Note:
Please refer to the Database Mail Setup Guidelines document to setup email
notifications regarding job execution status.

Review SQL Agent
 Using SSMS:
 Select <ServerName> | SQL Server Agent | Error Logs
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 33 of 67
Novar 6.0.x
System Administration Guide
Database Administration

Double click Current in right panel

Select entry in Log File Summary for more information
Test Backups
A SQL Server backup is only good if the restore works. The only way to determine that the backup /
restore process works is to periodically test on another server. This test restore serves two
purposes:

To verify the backup can be successfully restored and

To provide information on how long the entire process takes.
(This knowledge may prove useful, if the production server’s backup needs to be restored as
part of a recovery operation, etc.)
Administrators should use the Restore Verify option when creating the backups. It doesn't
guarantee that the restore will not have issues, but it does verify SQL Server can read the entire
backup file without a problem.
RECOMMENDATIONS
Periodic Tasks – Use the Restore Verify option when creating the backups. While it does not
guarantee the restore will not have any issues; it does verify SQL Server can read the entire
backup file without a problem.
Daily Task – Verify the Backups and Backup file size
Monthly Task – Verify Backup’s validity


Run a database restore with the VERIFYONLY statement.
Run a database restore to the test environment, and then run DBCC checks.
Monitor Performance
This task should also be a “no-brainer” for administrators responsible for monitoring the SQL Server
environment. The database is usually the last thing people think about when working on an
application. But, when the application is slow, the database is usually the first thing that is blamed
for poor (slow) performance.
Without good performance data it can be very difficult to distinguish true performance issues from
other types of software or hardware issues. Without good data, it can also be difficult to know
which changes will make the biggest impact on system performance and which will not.
Monitoring database performance offers some unique challenges and many administrators are not
always sure how to best tackle it. Windows and SQL Server offer built-in tools such as:

Performance Monitor

Profiler
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 34 of 67
Novar 6.0.x
System Administration Guide
Database Administration

Execution Plans

Index Tuning Wizard

Database Engine Tuning Advisor, etc.
In addition to these, there is a whole array of third-party tools that offer the ability to trend
performance issues and to alert administrators when there are issues.
RECOMMENDATIONS
Daily Task – Monitor disk space to ensure SQL Servers are not running out of disk space.

Using Windows Explorer:
 Check drive properties
 Using SSEM:
 Check database devices, even if automatic.
 Using T-SQL:
 Create stored procedure or batch file, using xp_fixeddrives for
each server.
Periodic Tasks –


Monitor performance using (at least) System Monitor and Profiler.
Use Enterprise Manager or SQL Server Management Studio (SSMS) to monitor
and identify blocking issues.
Document SOP Processes
A good set of Standard Operating Procedures (SOPs) should be established, so that everyone who
works on the SQL Servers understands the SOP processes that have been put in place and where to
find the documents. Implement a documentation process to document:

Procedures

Priority lists

Escalation lists

Disaster Recovery Plan

Production changes

Roll out procedures, etc
All changes should be documented as they occur, so if a problem does arise, administrators can
easily pinpoint when a change was made. A simple text file could be used to track changes or use
SQL Server to document and track the changes.
This should be one of the simplest processes to adopt and can usually be implemented immediately.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 35 of 67
Novar 6.0.x
System Administration Guide
Database Administration
RECOMMENDATIONS
On-Demand Tasks –


Keep a log of any changes made to servers, including documentation of any
performance issues that have been identified and corrected.
Script server and database changes back into the change-control management system
as soon as they occur.
Create and Test Disaster Recovery Plans
Disasters don’t happen often, but they do happen. Therefore, developing – and testing – a disasterrecovery plan is essential for returning operations to normal after a disaster – with as little
disruption in the day to day activities as possible.
As the DBA, take the time to determine the various kinds of problems that may arise, and then
formulate a plan for resolving them when / if they do happen. Think about this from: a server level,
a database level and also down to a table level. Once the plan has been formulated, test it. Although
it is not necessary to test every server in the environment; it is recommended that each type of
failure – identified in the recovery plan – get tested.
Consider this:

More than just the database backup will be needed to rebuild a SQL server. Having a copy of
the site’s server configuration information can vastly improve the efficiency and speed of
installing a new server after a disaster.

The disaster may involve multiple failures. Having a Priority List of servers and databases will
clarify the order (priority) for restoring systems after a multiple-system failure. The Priority
List should document the order in which devices / systems need to be recovered.
RECOMMENDATIONS
Periodic Tasks –
 Review and revise the Disaster Recovery document to keep it current
 Review the Disaster Recovery Plan with the staff
 Test the Disaster Recovery Plan.
Weekly Task – Save all server-configuration information

Using T-SQL:
 Create stored procedures to get configuration information, etc.
 Output to a .txt files.
Manage Security
Managing security is another area of responsibility for the designated DBA. Security exists at the:
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 36 of 67
Novar 6.0.x
System Administration Guide

Windows Server level

SQL Server (Server) level

Database level

Object level, etc
Database Administration
There are also SQL Server (server) level roles, database roles and user-defined roles. Take the time
to analyze the permission structure and make the necessary adjustments to ensure the staff has all
the appropriate rights needed for their role(s). Remove or add permissions for each user as needed.
In addition to securing the database servers, make sure database backups and any external
programs are also secure. Also, verify no unauthorized personnel can gain backdoor access to
servers or data. Check the surface area of the server – which means check any entry points for
network access, check who has failed logins, and review the security logs for any issues.
RECOMMENDATIONS
Weekly Task – Check Windows Security Logs for login failures and unusual events.

Using Control Panel:
 Select Administrative Tools | Event Viewer.
 Click Log to review.
 Double click entry in right panel for more information.
Test Connectivity and Availability
Unless the organization has a dedicated networking staff that is responsible for ensuring
connectivity, it is the responsibility of the DBA to ensure users can connect to and use the SQL
Server to complete their daily tasks.
Testing network connectivity is straightforward and provides multiple benefits. Testing connectivity:

Verifies hardware and servers are up and running

Verifies IP address and name have not been changed

Provides early warning if server has failed

Verifies IP address and name resolution
(Sometimes a problem with WINS, DNS, LMHOSTS)
RECOMMENDATIONS
Daily Task – Check network connectivity of SQL Servers.




Ping SQL Servers every X minutes with IP Sentry.
Use batch file to ping SQL Servers.
Use a server monitoring tool.
Using SSEM:
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 37 of 67
Novar 6.0.x
System Administration Guide

Database Tuning
 Click the “+” next to the server to confirm connectivity.
Using SSMS:
 Click File menu and select Connect Object Explorer.
 Provide connection information and click OK to confirm connectivity.
Conclusion
It is the responsibility of every DBA to work with their organizational leadership to plan and
implement database operational procedures consistent with organizational goals, risk tolerance, and
resources.
Database Tuning
In order to get the best possible performance from Novar, the SQL Server 2000 database must be
tuned to meet Novar’s particular needs. This section details the database-tuning recommendations
to help ensure that the Novar™ applications run as efficiently as possible.
TempDB Tuning
Novar uses TempDB extensively. TempDB is used by SQL Server to store intermediate-result sets,
arbitrate object allocation, and to contain temporary tables. It is therefore very important to
optimize the performance of this critical resource.
One of the most important functions of TempDB is to arbitrate object management. By default,
TempDB contains a single file and all SQL Server Object creation is serialized through that file (using
the SGAM block).
Database operations that heavily use TempDB:

Repeated creating and dropping of temporary tables (local or global)

Table variables that use TempDB for storage purposes

Work tables associated with cursors

Work tables associated with an Order By Clause

Work tables associated with a Group By Clause

Work files associated with Hash Plans
TempDB tuning is easy to accomplish. By adding files to the database – one per processor or
processor-core (but not hyper threads) – significant parallelism is introduced. In ultra-high
performance environments, these additional files can be placed on separate physical drives
(LUNs in clustered environments, local drives in non-clustered systems).
In fact, a large benefit can be achieved even when all of the files reside on the same drive.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 38 of 67
Novar 6.0.x
System Administration Guide
Database Tuning
Another TempDB optimization step that can improve database efficiency is to turn on the 1118 trace
flag. This flag enables (off) or disables (on) mixed extent objects, that is, objects of different
allocation sizes. When set, the amount of memory-management arbitration is greatly reduced.
There will however be an increase in the amount of memory consumed by SQL Server.
RECOMMENDATIONS


Create multiple TempDB data files
o For non-NUMA systems
 Create a TempDB data file for each logical processor (core).
o For NUMA systems
 Create a TempDB data file for each NUMA node
Turn on the 1118 Trace Flag.
Novar Archive Database
Novar versions 6.0 and above create a new Database “Novar Archive” during the upgrade process.
This database is created as a future enhancement for Data Archival. This initial size of the Novar
Archival will be based on the Model Database which gets created as part of SQL Server installation.
In order to minimize empty disk space allocation, no additional space is recommended for the Novar
Archive Database but will be based on the size of the Model Database as it is the standard
functionally of SQL Server to create any new user Database based on the size of the Model
Database. The Novar Archive will be set to Auto Grow to accommodate data storage as and when
new functionality is added to the Archival process.
Creating Multiple TempDB Data Files
To create multiple TempDB data files:
1. Calculate the minimum size for each TempDB data file.
Number of Temp file based on cores, maximum 8 files with initial size 10% of DB. To
calculate the minimum recommended size for the TempDB data files, use the following
formula:
<Min File Size> = RoundUp(RoundUp(<NovarDB GB> * 10%,0)/<Core Count>,0)
<Total TempDB Size> = <Min File Size> * <Core Count>
Make sure the Temp DB recovery mode - Simple
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 39 of 67
Novar 6.0.x
System Administration Guide
Database Tuning
The worksheet below can be used to assist in calculating the minimum file size:
Item
Detail
Calculated Round up
Value
to next GB
Novar DB Size (GB)
Minimum TempDB Size (GB)
10%
Number of Cores
Minimum Size of Each TempDB File (GB)
Total TempDB Size
For example: If the Novar DB is 84 GB and the SQL Server has four processor cores:
Item
Detail
Novar DB Size (GB)
84
Minimum TempDB Size (GB)
10%
Number of Cores
4
Calculated Round up
Value
to next GB
8.40
9
Minimum Size of Each TempDB File (GB)
2.25
3
Total TempDB Size
12.00
2. Open the Sql Server Management tool and navigate to the database server, then to TempDB
database.
3. Right-click TempDB, select Properties, click to open the Data Files tab, and set the Space
allocated (MB) value as 10.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 40 of 67
Novar 6.0.x
System Administration Guide
Database Tuning
RECOMMENDATIONS
Configure automatic notifications if low-on-space conditions are encountered, or set up other
processes to monitor the utilization of TempDB to ensure the system never runs out of space.




Set Auto growth ON, can be set to 200 MB (assuming sufficient Disk space is
available).
Not recommended to set growth by percentage.
Place all files on the same drive, if possible on a local drive.
Every time SQL Server is started, the TempDB file is re-created with the
default size. While TempDB can grow, it does take resources to perform this
task. To reduce this overhead of TempDB growing, you may want to
permanently increase the default size of TempDB after carefully monitoring
its growth.
4. Create a series of new data files (example above) with the following characteristics:

Set each to the exact same size – ideally in multiples of 1024 MB
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 41 of 67
Novar 6.0.x
System Administration Guide
Database Tuning

Set Automatically grow file to Off for all (must be cleared individually)

Set the Location value, as documented in the site’s database plan.
NOTE
RAID is not recommended for TempDB due to performance considerations.
5. Click OK to create the files and close TempDB Properties dialog box.
(Building the files may take several minutes.)
6. Navigate to the Model database.
7. Set the Space Allocated (MB) value as 10.
8. Set up one Model data file (do not create more) to match exactly the size of one TempDB
data file and set Automatically grow file to Off (not selected).
9. Click OK to create the file and close Model Properties dialog box.
(Building the file may take several minutes.)
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 42 of 67
Novar 6.0.x
System Administration Guide
Database Tuning
NOTE
Because of the need to build the TempDB files at startup, the time from restart of the server to
ready for connections may need to be increased.
Implementing Trace Flag 1118
To implement this trace flag:
1. Open the management tool and navigate to the database server.
2. Right-click the server and select Properties.
3. Click the Startup Parameters… button.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 43 of 67
Novar 6.0.x
System Administration Guide
Database Tuning
4. Enter -T1118 in the Parameter textbox and click Add button.
(Example shown next)
5. Click OK to close the Startup Parameters dialog box.
6. Click OK to close the SQL Server Properties dialog box.
The change will take effect at the next startup of the SQL Server.
Implementing Trace Flag 1222
The trace 1222 is for dead lock detection. When deadlocks occur, trace flags return dead lock details
that is captured in the SQL Server error log. Trace Flags output provides information on the type of
locks participating in the deadlock and current command affected.
1. Open SQL Server Configuration Manager and navigate to the SQL Server Services.
2. In the right pane, right-click SQL Server (<instance_name>), and click Properties.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 44 of 67
Novar 6.0.x
System Administration Guide
Database Tuning
3. Go to the Advanced tab.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 45 of 67
Novar 6.0.x
System Administration Guide
Database Tuning
4. In the Startup Parameters box, enter the parameter -T1222 separated by semicolons (;).
5. Click OK to close the Properties dialog box.
6. Restart the Database Engine.
For More Information
Use the following links to go to specific Microsoft articles, or search for TempDB articles at:

Concurrency Enhancements for the TempDB Database
Database Contention Settings for Sql Server 2008 R2
Performance issues such as slow query execution and deadlocks are often due to contention for table
records by multiple processes. The following settings are available with Sql Server 2008 R2.
Snapshot Isolation
Using the query analyzer execute the following statements, replacing <databasename>.
--View current settings:
SELECT name, snapshot_isolation_state
FROM sys.databases
WHERE name = N'<databasename>'
--Effect the setting change:
ALTER DATABASE <databasename>
SET ALLOW_SNAPSHOT_ISOLATION ON
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 46 of 67
Novar 6.0.x
System Administration Guide
Database Tuning
--View changed settings (this will persist even after Sql
Server re-start)
SELECT name, snapshot_isolation_state
FROM sys.databases
WHERE name = N'<databasename>'
Auto-Update Statistics
Using the query analyzer execute the following statements, replacing <databasename>.
--View current settings:
SELECT name, is_auto_update_stats_on,
is_auto_update_stats_async_on
FROM sys.databases
WHERE name = N'<databasename>'
--Effect the setting change:
ALTER DATABASE <databasename> SET AUTO_UPDATE_STATISTICS ON
ALTER DATABASE <databasename> SET AUTO_UPDATE_STATISTICS_ASYNC
ON
--View changed settings (this will persist even after Sql
Server re-start)
SELECT name, is_auto_update_stats_on,
is_auto_update_stats_async_on
FROM sys.databases
WHERE name = N'<databasename>'
Memory Management
With Sql Server 2008 R2 and 2012, manual optimization of memory management settings is no
longer required.
Please refer to this Microsoft article on memory management settings.
Max Degree of Parallelism
If SQL Server chooses to use a serial plan, it will only use one (1) processor. However, if SQL Server
chooses to use parallelism, it must use all the configured processors (as determined by the MAXDOP
query hint or configuration value) for the execution of a parallel plan. For example, if you use
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 47 of 67
Novar 6.0.x
System Administration Guide
Database Tuning
MAXDOP=0 (the default value) on a 32-way server, SQL Server tries to use all 32 processors even if
seven processors might perform the job more efficiently as compared to a serial plan that only uses
one processor. Because of this all-or-nothing behavior, if SQL Server chooses the parallel plan and
you do not restrict the MAXDOP query hint to a maximum value of 8, the time that it takes SQL
Server to coordinate all the processors on a high-end server outweighs the advantages of using a
parallel plan.
The MAXDOP setting applies to each step of the plan. Each step will use either one CPU or the
number of CPUs that is specified by MAXDOP and never anything in between. If steps execute in
parallel, the number of threads that are used by the query may exceed the MAXDOP setting.
Use the following guidelines when you configure the MAXDOP value:

For servers that use more than sixteen processors, MAXDOP should not exceed 8.

For servers that have less than sixteen processors, MAXDOP should not exceed one-half the
number of processors (round down).

For servers that have NUMA configured, MAXDOP should not exceed the number of CPUs
that are assigned to each NUMA node.

For servers that have hyper-threading enabled, the MAXDOP value should not exceed the
number of physical processors.
Using Query Analyzer
To set the max degree of parallelism, open Query Analyzer and execute the following:
sp_configure 'max degree of parallelism', 8
RECONFIGURE WITH OVERRIDE
GO
Disk I/O Tuning
Torn Page Detection
This option allows SQL Server to detect incomplete I/O operations caused by power failures or other
system outages. When true, it causes a bit to be flipped for each 512-byte sector in an 8-kilobyte
(KB) database page whenever the page is written to disk. If a bit is in the wrong state when the page
is later read by SQL Server, then the page was written incorrectly; a torn page is detected. Torn
pages are usually detected during recovery because any page that was written incorrectly is likely to
be read by recovery.
Using battery-backed disk controller caches can ensure that data is successfully written to disk or
not written at all. In this case, it is not necessary to set torn page detection to true, for it is not
needed.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 48 of 67
Novar 6.0.x
System Administration Guide
Novar Database Maintenance Tasks
Using Query Analyzer
To set Torn Page Detection, open Query Analyzer and execute the following:
ALTER DATABASE <database_name>
SET TORN_PAGE_DETECTION ON
GO
Novar Database Maintenance Tasks
Imagine Communications recommends all Novar clients implement daily, nightly and weekly
database maintenance tasks. It is recommended that after an install or upgrade, these maintenance
tasks are reviewed for accuracy, scheduled (activated) and then enabled as appropriate.
Once enabled, restart the SQL agent to trigger these maintenance jobs.
Overview
Novar database maintenance tasks created as Sql Server Agent jobs during the installation process.

Novar Database Backup - Full, Daily

Novar Log Backup - Incremental, Current

(Novar) Conline Projection Update – Periodic

(Novar) Table Maintenance – Nightly

(Novar) Table Maintenance – Weekly
The two backup jobs are created as shells or containers that will need to be customized for each
environment. The table maintenance jobs are created fully configured – ready for scheduling and
use.
WARNING
All jobs are created with a status of Disabled and Inactive (not scheduled). Before these jobs will
function as expected, the system administrator or a Novar Client Services consultant will need to
review them, set up the appropriate schedule times and switch each to Enabled.
Database Backups
The Maintenance Jobs script creates two backup shells (or containers) that will need to be
customized for each environment.
Novar Database Backup - Full, Daily
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 49 of 67
Novar 6.0.x
System Administration Guide
Novar Database Maintenance Tasks
A complete backup of the Novar Database (data and log files) is recommended nightly. This
maintenance job is created to serve as a container for adding the steps necessary to perform this
function in your environment.
Novar Log Backup - Incremental, Current
An incremental backup of the Novar Database log files is recommended to be run periodically. This
maintenance job is created to serve as a container for adding the steps necessary to perform this
function in your environment.
To schedule a database backup operation by using SQL Server Management Studio in SQL Server
2008:
1. Launch the SQL Server Management Studio application.
2. In the Connect to Server dialog box, select the appropriate values from the following dropdown fields:

Server type

Server name

Authentication
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 50 of 67
Novar 6.0.x
System Administration Guide
Novar Database Maintenance Tasks
NOTE
The Login and Password fields will be enabled only when SQL Server Authentication is selected.
3. Enter the login name and password, and click Connect. The Microsoft SQL Server
Management Studio application is launched.
4. In the Object Explorer pane, expand Databases.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 51 of 67
Novar 6.0.x
System Administration Guide
© 2015 Imagine Communications Corp.
Novar Database Maintenance Tasks
Proprietary and Confidential
Page 52 of 67
Novar 6.0.x
System Administration Guide
Novar Database Maintenance Tasks
5. Right-click the database that you want to back up and select Tasks -> Back Up… to navigate
to the Database Back Up window.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 53 of 67
Novar 6.0.x
System Administration Guide
Novar Database Maintenance Tasks
6. In the Back Up Database dialog box, on the right pane, under Backup set, specify the name
of the database in the Name field and click Add in the Destination section to navigate to the
Select Backup Destination dialog box.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 54 of 67
Novar 6.0.x
System Administration Guide
Novar Database Maintenance Tasks
7. In the Select Backup Destination dialog box, click the
Database Files dialog box.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
button to display the Locate
Page 55 of 67
Novar 6.0.x
System Administration Guide
Novar Database Maintenance Tasks
8. In the Locate Database Files dialog box, select the required file location and click OK to
navigate back to the Select Backup Destination dialog box.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 56 of 67
Novar 6.0.x
System Administration Guide
Novar Database Maintenance Tasks
9. In the Select Backup Destination dialog box, click OK to navigate back to the Back Up
Database dialog box.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 57 of 67
Novar 6.0.x
System Administration Guide
Novar Database Maintenance Tasks
10. In the Back Up Database dialog box, from the Script drop-down list, click Script Action to
Job. The New Job window is displayed.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 58 of 67
Novar 6.0.x
System Administration Guide
Novar Database Maintenance Tasks
11. In the Select a page pane, click Steps. Click Edit to change the job parameters, if required.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 59 of 67
Novar 6.0.x
System Administration Guide
Novar Database Maintenance Tasks
12. In the Select a page pane, click Schedules and then click New. The New Job Schedule dialog
box is displayed.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 60 of 67
Novar 6.0.x
System Administration Guide
Novar Database Maintenance Tasks
13. In the New Job Schedule dialog box, in the Name field, type the job name, and from the
Schedule type drop-down list, select a job schedule type. Click OK to navigate back to the
New Job dialog box.
NOTE
In the Select a page pane, click Alerts or Notifications to configure alerts or notifications, if
required.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 61 of 67
Novar 6.0.x
System Administration Guide
Novar Database Maintenance Tasks
14. In the New Job window, click OK to navigate back to the Back Up Database dialog box.
15. In the Back Up Database dialog box, click OK to immediately start the backup. Click Cancel
to schedule the backup, but not start the backup.
NOTE
To review the backup created, open Object Explorer (steps 1-3)ManagementSQL Server
AgentJobs. Right-click backup, and left-click Properties.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 62 of 67
Novar 6.0.x
System Administration Guide
Novar Database Maintenance Tasks
Table (and Calculated Values) Maintenance
The Maintenance Jobs script creates three standard table-maintenance jobs. These jobs should
never be modified except to activate and enable. Additional custom maintenance jobs can always be
manually created for other database maintenance tasks that are required.
WARNING
Imagine Communications reserves the (Novar) prefix as a standard naming convention.
Modifying these standard jobs or creating custom jobs that use the (Novar) prefix in the name is
not recommended. Any custom modifications made to a (Novar) standard job will be lost if
Imagine Communications changes the content of, or deletes, this maintenance job in a future
release.
(Novar) Conline Projection Update - Periodic
The Conline Projection table requires periodic updates so that reports such as the Yearly Revenue
Projection accurately reflect the changes made to contracts through the normal course of business.
This scheduled maintenance job performs all the necessary steps required to keep this important
financial summary data current. The steps of this (Novar) maintenance task include:

Execute Conline Projection Update (“current changes” mode [rolling 13 Weeks])

Execute Client History Update

Execute Client Revenue Update
Schedule recommendations: This job should run every 20 to 30 minutes on all business days.
(Novar) Table Maintenance - Nightly
Some Novar tables, and many indexes, require nightly maintenance to help ensure optimal system
performance. This scheduled task performs all the necessary steps required to keep these tables and
indexes properly organized. The steps of this (Novar) maintenance task include:

Maintenance – Reserve Table

Maintenance – Channel Status Table

Create Index Statistics

Capture Table Growth Data

Defragment Indexes

Maintenance – Event Records for Contracts

Rebuild Indexes
NOTES


Rebuilding indexes is an invasive procedure intended to maintain server
performance but will disrupt running processes.
Update Index Statistics
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 63 of 67
Novar 6.0.x
System Administration Guide
Novar Database Maintenance Tasks

Execute Conline Projection Update

Execute Client History Update

Execute Client Revenue Update
NOTES


The Table Growth information will be used in future releases to support creation of multiple
file groups (performance enhancement) and intelligent scheduled growth of the database
files.
Defragmentation of indexes is a minimally invasive procedure intended to maintain server
performance without interrupting normal overnight processes. The work is prioritized to
process key tables first and can optionally be set with a time limit on the processing.
Schedule recommendations: This job should run nightly, prior to the backup, on all business
days.
(Novar) Table Maintenance - Weekly
Some Novar tables, and many indexes, require weekly maintenance to help ensure optimal system
performance. This scheduled task performs all the necessary steps required to keep these tables and
indexes properly organized. The steps of this (Novar) maintenance task include:

Maintenance – Audit Log Table

Maintenance – Exception Table

Maintenance – Channel Status Archive Table

Maintenance – Spot Trail Table
NOTES


This step is bypassed if nro_DC_SpotTrail_Cleanup has not been successfully
executed.
For more information on the enhancement that introduced new Spot Trail system
configuration settings, please search the Cumulative Rush Pack Release Notes for
5.12 SR2B3 for work ticket 33962 or the 5.13.0 Release Notes for work ticket 33963.

Maintenance – Truncate Paging Tables

Maintenance – ebizcontractchangelog Table

Maintenance – ConImport Table (for Gatekeeper™ Import users)

Update Index Usage

Maintenance – Novar Archive Tables (for NetGain® users)
NOTES


ArchiveDatabase – Establishes the network location where Novar archives old data
that have been deleted
ArchiveAfterMonths_Deleted – Allows users to specify the number of months for
which the data in the _deleted table need to be archived
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 64 of 67
Novar 6.0.x
System Administration Guide
Acronyms
Schedule recommendations: This job should run weekly, typically in the early hours of Sunday
morning and as part of the post-install process after every upgrade.
RECOMMENDATIONS

The “(Novar) Table Maintenance – Weekly” scheduled task should be set to run during a
period of either no activity or only minimal system activity. When possible, schedule this
procedure to execute during a period when no users are working and AdS services are
shut down.
Acronyms
This document contains several commonly used acronyms. The acronym and its corresponding
name are listed next.
CPU –
DB –
DBA –
Gb –
GB –
Mb –
MB –
NUMA –
RAM –
SGAM –
SQL –
SSEM –
SSMS –
SSMSE –
T-SQL –
USB –
Central Processing Unit
Database
Database Administrator
Gigabit
Gigabyte
Megabit
Megabyte
Non-Uniform Memory Access
Random Access Memory
Shared Global Allocation Map
Structured Query Language
SQL Server Enterprise Manager
SQL Server Management Studio
SQL Server Management Studio Express
Transact-SQL
Universal Serial Bus
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 65 of 67
Novar 6.0.x
System Administration Guide
Glossary
Glossary
Non-Uniform Memory Access (NUMA) – A computer memory design used in multiprocessors,
where the memory access time depends on the memory location relative to a processor. Under
NUMA, a processor can access its own local memory faster than non-local memory, that is, memory
local to another processor or memory shared between processors.
Shared Global Allocation Map (SGAM) – Allocation pages are special pages in the data files that
track and mange extent (file page) allocations. One type is the SGAM, it tracks which extents are
being used as mixed (shared) extents. Because there is only one page per 4 GB of SQL Server data
file size, this can cause contention in the TempDB.
SQL Server Express – Specifically, SQL Server Express 2008; is a freely downloadable and
distributable version of Microsoft's SQL Server relational database management system.
WARNING
SQL Server Express is a limited capability version of SQL Server. It will utilize only one
physical processor (all cores of that one chip, but only one chip); one GB of the total
installed RAM; and has a database size limit of 4 GB (10 GB in SQL Server Express 2008 R2).
Also, it does not provide the SQL Server Agent, and cannot use scheduled tasks – therefore,
this edition is not suitable for use with Novar.
SQL Server Management Studio (SSMS) – A tool included with Microsoft SQL Server 2005 (and later
versions) for configuring, managing, and administering all components within Microsoft SQL Server.
The tool includes both script editors and graphical tools to work with objects and features of the
server.
SQL Server Management Studio Express (SSMSE) – A free version of the SQL Server Management
Studio tool available with, and designed for, Microsoft SQL Server 2005 Express (and later versions)
for configuring, managing, and administering components within the Microsoft SQL Server Database
Engine only. The tool includes both script editors and graphical tools to work with objects and
features of the database server.
WARNING
SSMSE is a limited-capability version of SSMS and can manage SQL Server databases only; it
can manage instances of the SQL Server Database Engine created by any edition of SQL
Server 2000 through 2008 R2; however, SSMSE cannot manage SQL Server Analysis Services,
Integration Services, Notification Services, or Reporting Services.
TempDB – Is a global resource that is available to all users connected to the instance of SQL Server
and is used to hold temporary user objects, Internal objects that are created by SQL Server, and
Data Row versions that are generated by data modification transactions.
Transact-SQL (T-SQL) – Microsoft's and Sybase's proprietary extension to SQL. Microsoft's version
ships in the Microsoft SQL Server product.
Workgroup Edition (WE) – Specifically, SQL Server 2008 (or 2008 R2) Workgroup Edition. This
edition of SQL Server 2008 is fully featured, but does have strict limits on the resources it can utilize
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 66 of 67
Novar 6.0.x
System Administration Guide
Glossary
(two physical processors max; 4 GB RAM max); therefore, it is suitable only to single-user of very
small Novar installations.
© 2015 Imagine Communications Corp.
Proprietary and Confidential
Page 67 of 67