0% found this document useful (0 votes)
20 views

Sage Estimating SQL Server Guide

Uploaded by

sam pam
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
20 views

Sage Estimating SQL Server Guide

Uploaded by

sam pam
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 45

Sage Estimating (SQL) v23.

1
SQL Server Guide

November 2023
This is a publication of Sage Software, Inc.

© 2023 The Sage Group plc or its licensors. All rights reserved. Sage, Sage logos, and Sage product and
service names mentioned herein are the trademarks of The Sage Group plc or its licensors. All other
trademarks are the property of their respective owners.

Last updated: November 14, 2023


Contents

Chapter 1: Microsoft SQL Server and Sage Estimating 1


Microsoft SQL Server and Pervasive 1
The SAGE_ESTIMATING Instance 2
Microsoft SQL Server Files 3
SQL Database Permissions and Access 4
Read the Supporting Documentation Before You Begin 4
Conventions Used in this Guide 5
Need help? 6
Submitting Enhancement Requests 9

Chapter 2: Technical Information 10


Supported Editions of SQL Server 10

Chapter 3: Installation 11
Overview 11
SQL Server Express Installation 12
Modified Installation 13

Chapter 4: FAQs 14
I already use a version of Microsoft® SQL Server® on my computer. Can I use this version with
Sage Estimating? 14
If I already have a version of SQL Server installed, does installing Sage Estimating upgrade my
existing SQL Server version? 14
What are the minimum system requirements to install SQL Server? 14
Which operating systems are supported with SQL Server? 14
Are 64-bit platforms supported? 15
Can SQL Server Express Edition installations be performed on substitute, mapped, or compressed
drives? 15
Can I use File Tools or other utilities to back up my SQL databases? 15

Sage Estimating (SQL) v23.1 SQL Server Guide iii


Contents

Will running a virus scanner on the SQL Server host machine affect performance? 15
How can I test whether SQL Server is working in Sage Estimating? 15
What do I need to be able to manage user access rights in SQL Server? 16
I can connect to a SQL Server instance on my local computer but why can't I connect to a
SQL Server instance on a remote server? 16

Chapter 5: Troubleshooting SQL Server 17


Installation Issues 17
Connection Issues 18
Determining the path to the SQL Server program 24

Chapter 6: Additional Information 25


General Information 25
Corruption 25
Security 25
Services 26

Chapter 7: Glossary 27
BOL/Books On Line 27
Instance/Named Instance 27
Microsoft Desktop Engine (MSDE) 27
sa 27
SQL 27
SQL Server Management Studio (SSMS) 27
SQL Server Management Studio Express (SSMSE/SSMS Express) 28
Stored Procedures 28
Transact-SQL 28
User Account Control (UAC) 28

Appendix A: SQL Server Instance Settings 29


Instance Configuration: SAGE_ESTIMATING Instance 29
Server Configuration: Collation Settings 30
Database Engine Configuration: Authentication Mode 32

Sage Estimating (SQL) v23.1 SQL Server Guide iv


Contents

Additional Recommendations 33
Communication protocol 33

Appendix B: Backing Up and Restoring Using SQL Management Studio 35


Backing Up SQL Server Databases 35
Backing up the SQL Database 36
Restoring the SQL Database 38

Sage Estimating (SQL) v23.1 SQL Server Guide v


Chapter 1: Microsoft SQL Server and Sage
Estimating

Sage Estimating uses SQL Server as its database platform. Previous releases used Pervasive as the
database platform for storing Sage Estimating data. This database platform change is intended to offer you
increased security, performance, and flexibility for your reports, queries, and daily operations.

This document provides information on the impact of these changes. It is important to understand these
differences so that you can effectively manage and protect your Sage Estimating data.

Although this document is current at the time of its distribution, a newer version may be available. For the most
recent version, visit Sage Estimating Product Documents, and then click Sage Estimating
(SQL) > Version 23.1 > Sage Estimating SQL Server Guide.

Microsoft SQL Server and Pervasive


Microsoft SQL Server represents a change from the Pervasive database platform used in previous Sage
Estimating releases. It is important to understand how the new SQL Server database platform is structured.

SQL Server stores database information in database (.mdf) and log (.ldf) files. Previously, Sage Timberline
Office Estimating created separate estimate files that you could store in any desired Windows file structure.
With the new SQL Server database, Sage Estimating stores all your estimates in the same .mdf database file
on a single server known as an instance.

Comparison of Pervasive and SQL Server

Sage Estimating (SQL) v23.1 SQL Server Guide 1


A Sage Estimating instance (sometimes referred to as a "server") consists of three primary components:
l An Address Book database
l An estimate database
l One or more standard databases

You configure security for the instance, and then apply it to all contents, including the Address Book, all
standard databases, and all estimates within the estimate database.

Estimates are stored entirely within the estimate database. With Sage Estimating (SQL), you can use the
Estimating Management Console to arrange your estimates in a hierarchy of tiers or "branches." The branches
you create in the Estimating Management Console are for organizational purposes only. They do not change
the structure of your database.

The location of your SQL Server database files (.mdf and .ldf files) depends in part on your operating system.
See "SQL Server Express Installation" (page 12) for more information.

SQL Server allows an unlimited database size. However, SQL Server Express limits the database size to 10
gigabytes (GB). Sage Estimating warns you if your database size nears the limit.

If you select the option to create a new SQL Server instance in the Select installation options for Sage
Estimating window, the installation process automatically configures a new Sage Estimating-compatible
instance for you. The default name for the instance is SAGE_ESTIMATING. However, you can name the
instance anything you want.

If you do not select the option to create a new SQL Server instance in the Select installation options for Sage
Estimating window, you can create your own instance using an existing SQL Server installation. The new
instance must meet the requirements stipulated in "Modified Installation" (page 13).”

The SAGE_ESTIMATING Instance


Sage Estimating allows the use of just one active SQL Server instance at a time. The active instance is a
"closed" SQL Server instance. Sage Estimating does not recognize databases (Address Book or standard
databases) transferred or copied from other SQL Server instances unless they are added by way of the Search
For feature in the Estimating Management Console.

For example, if you have two Sage Estimating installations, Install A and Install B, you cannot copy Address
Book databases by copying them from Install A's SQL Server instance to Install B's SQL Server instance alone
(using SQL Server Management Studio's built-in Copy Databases wizard, for example). You also need to open
the Estimating Management Console and use the Search For button in the Address Book
Companies/Contacts toolbar.

Sage Estimating (SQL) v23.1 SQL Server Guide 2


Copying Databases From One SQL Server Instance to Another

Any database you add to an instance must have the same Sage Estimating version as the other operating
databases.

Example: If you are using Sage Estimating 23.1, and you want to add a standard database from a
previous Sage Estimating installation, upgrade the standard database to version 23.1 before adding it to
the new instance.

Refer to the Estimating Management Console in-product Help for instructions on adding databases using the
Search For feature.

SQL Server allows an unlimited database size. However, SQL Server Express limits the database size to 10
gigabytes (GB). Sage Estimating warns you if your database size nears the limit.

If you select the option to create a new SQL Server instance in the Select installation options for Sage
Estimating window, the installation process automatically configures a new Sage Estimating-compatible
instance for you. The default name for the instance is SAGE_ESTIMATING. However, you can give the
instance any name you want, provided it is not the same as an existing SQL Server instance on the computer.

If you do not select the option to create a new SQL Server instance in the Select installation options for Sage
Estimating window, you can create your own instance using an existing SQL Server installation. The new
instance must meet the requirements stipulated in "Modified Installation" (page 13).

Microsoft SQL Server Files


Every SQL Server database has at least two files associated with it:

Sage Estimating (SQL) v23.1 SQL Server Guide 3


l A file that stores the actual data (.mdf)
l A transaction log file (.ldf)

SQL Server stores your Sage Estimating data in the database file (.mdf). For details, see "SQL Server Express
Installation" (page 12).

The transaction log (.ldf) records all changes to the data in the database. This log ensures data integrity by
keeping track of data that has changed and can be used to roll the data back to a previous state in the event of
a database failure.

It is important to make regular backups of these files. For more information, see "Backing Up SQL Server
Databases" (page 35).

Collation settings for use with Sage Estimating


Sage Estimating requires a special collation setting. Collation settings in SQL Server must be set to:
l Latin1_General
l Case-sensitive
l Accent-sensitive

See "Server Configuration: Collation Settings" (page 30) for more information.

SQL Database Permissions and Access


You need to give each Sage Estimating operator permissions to the Sage Estimating features that they are
expected to use. Assign database and feature permissions using the security feature of the Estimating
Management Console. For more information, see the Estimating Management Console in-product Help.

Caution! Do not change the owner of any databases in the Sage Estimating instance.

Read the Supporting Documentation Before You Begin


Be sure to read the supporting documentation before you begin. The following guides are available at
http://cdn.na.sage.com/Docs/en/customer/estimating/SageEstimatingDocs.htm for each supported version:
l This SQL Server Guide gives you an overview of the significant differences between the new
SQL Server databases and the Pervasive databases used in previous Sage Estimating releases.
l The Installation and Administration Guide includes an overview of this release, installation instructions,
and contact information.
l The Release Notes provide details about new features, database changes, known issues, and fixes.
l The Getting Started Guide provides an operational overview of the Sage Estimating software.

Sage Estimating (SQL) v23.1 SQL Server Guide 4


l The Options Guide provides installation, setup, and operating instructions for each of the available Sage
Estimating options, such as the OnScreen Takeoff Integrator or License Manager.
l The Sage 100 Contractor Integration Guide describes how to integrate Sage Estimating with Sage 100
Contractor, making certain data in that program available in Sage Estimating, and it explains how to use
the interface wizards to send proposals, budgets, and change orders you create in Sage Estimating to
Sage 100 Contractor.

Important! For current information about supported operating systems, Internet browsers, Microsoft®
SQL Server®, and other software, and about system requirements for servers and client workstations,
refer to our Knowledgebase article System Requirements for Estimating v23.1.The system requirements
are the minimum for a computer running Estimating with one SQL Server instance. Running several
other business programs with multiple SQL Server instances may affect the performance of your system.

Conventions Used in this Guide


This guide uses the following conventions:
l Information you type into the software is shown in bold font. For example: Type Miscellaneous in the
box.
l The names of screens, windows, fields, and other features displayed by the software are shown in bold
font.
l Names of keys are also shown in bold font. For example: Enter or Tab. A plus sign (+) between two key
names indicates you should press the keys simultaneously.
l The names of buttons you can click are shown in bold font and enclosed in brackets. For example: [OK]
or [Post].
l Variable names or names that are specific to your installation may appear in italics and brackets. For
example: [Drive]\\[Server].

Notes, Tips, and Cautions


Note: A Note indicates that the information supplements the adjacent text.

Tip: A Tip indicates helpful points about using the software.

Caution! A Caution indicates important information to help you avoid a loss of critical data.

Important! An Important note indicates critical information that you need to understand or important
steps you need to take.

Sage Estimating (SQL) v23.1 SQL Server Guide 5


Menu Paths
In this document, menu paths show you the steps required to start a task. Menu paths appear in bold font with
square brackets around buttons. For example:

"If the program does not automatically start, click [Start] > Run."

Need help?
Use Sage Estimating Help or a variety of self-help resources to get answers to your questions.

The Help System


Sage Estimating Help provides more efficient access to information than most manuals. With a click of the
mouse or a keystroke, you can easily get Help for a command, a field, a window, or a procedure.

Sage Estimating displays Help in your default browser. If you have an Internet connection, it displays the most
current Help for your version of Sage Estimating available from a hosted Help server. If you have no
connection (you are working offline), it displays Help that was current when the software was released, and is
installed on your computer when you install Sage Estimating.

Important! Because the Microsoft Edge browser does not display locally installed help properly, we
recommend that you select a different default browser when working offline.

To get Help on a window option


To display Help for an option in a window, do one of the following:
l Click What's This? on the toolbar or on the title bar, and then click the option.
l Select What’s This? from the Help menu, and then click the option.
l Select the option, and then press F1.

To get Help for the whole window


For information about the window, such as the window's purpose and what tasks you can perform in it, click
[Help] at the bottom of the window.

To use Help to learn how to do tasks


1. Click [Help] on the toolbar, or select the Home tab > Help group > Help (or select Help menu > Help
topics in classic view).

Sage Estimating (SQL) v23.1 SQL Server Guide 6


The Help Window

2. Use the navigation pane to begin looking for a topic.

l Help subjects are organized under headings. Select the heading for the type of task you want to
perform to view a list of topics.

When you see the topic you want, double-click it to display it.
l Select the Glossary heading to view an alphabetical list of definitions of terms used throughout the
Sage Estimating software.
3. Use the Search box to find articles that match the keywords you enter.

Additional self-help resources


The Help menu available from on the ribbon also provides convenient links to a variety of self-help resources.

Sage Estimating (SQL) v23.1 SQL Server Guide 7


The Help menu in Ribbon view

How to Get Additional Help


Get help by: Recommendation* To access:
Reading product View documents and reference material from the Visit the Sage Estimating
documentation Estimating Product Documents website. Product Documents page.
Search the Sage Knowledgebase, which provides
Searching the Visit the Knowledgebase at
24/7 access to support articles as well as the latest
Knowledgebase Sage Knowledgebase.
software downloads and updates.
Join industry peers, certified partners, and Sage
Asking the pros online 24/7 at the Sage Community Hub—the Visit the Sage Estimating
community best place to ask questions and share product General Discussion forum.
experiences, tips, and tricks.
Checking the Keep up with the latest product information with
See Sage Estimating
latest product Sage Estimating Announcements at the Sage
Announcements.
alerts Community Hub forum.
Submitting a Submit your issue directly to our support team using
Visit the Sage Customer Portal.
web ticket Online Case submission.
Visit Sage University.
You can also get access to Sage
Exploring Learn how to harness the full power of your software
University from the Estimating
training options through videos and classes at Sage University.
File menu by selecting Help >
Sage University.
* Customer Service hours vary by product line. Access to some resources require an active Sage
Business Care support plan.

Sage Estimating (SQL) v23.1 SQL Server Guide 8


Submitting Enhancement Requests
We want to hear your suggestions for improving the software. To send us your comments, click the File menu
button and then select Help > Submit Product Idea.

Sage Estimating (SQL) v23.1 SQL Server Guide 9


Chapter 2: Technical Information

Supported Editions of SQL Server


For current information about supported operating systems, Internet browsers, Microsoft® SQL Server®,
and other software, and about system requirements for servers and client workstations, refer to our
Knowledgebase article System Requirements for Estimating v23.1.

Note: The system requirements are the minimum for a computer running Estimating with one SQL
Server instance. Running several other business programs with multiple SQL Server instances
may affect the performance of your system.

A copy of SQL Server Express Edition is provided free of charge with Sage Estimating. This edition is
sufficient for most Sage Estimating customers. However, customers with large databases may need to
upgrade to the Standard Edition. For information on Microsoft SQL Server editions, visit
www.microsoft.com.

Sage Estimating (SQL) v23.1 10


Chapter 3: Installation

Overview
Before installing Sage Estimating, you have two primary SQL Server scenarios to consider:
l SQL Server Express Installation. Installing Sage Estimating also installs SQL Server Express
when you select certain installation options. Follow this scenario for these conditions:
l You are installing Sage Estimating on a standalone workstation or a workgroup server.

l You are installing to a server on a domain and you want to use the copy of SQL Server
Express that comes with the Sage Estimating install package.

The Sage Estimating installation package installs and configures a new SQL Server
instance of SQL Server Express whenever you select the option to create a new instance.
You can operate the new SQL Server instance alongside an existing SQL Server instance.

l Modified Installation. You have already installed a supported version of SQL Server (or plan to
install one), and you want to manually create a new instance to use with that version.

Important! If you are using Sage Estimating in a multi-user environment, Sage recommends that
you use the standard SQL Server product. Although SQL Server Express is a reasonable choice
for smaller-scale implementations, it does not support databases larger than 10 GB and can only
use 1 GB of RAM (among other limitations), so we do not recommend that you use it for a shared
SQL Server instance.

Use the Security feature in the Estimating Management Console to assign database permissions to each
operator after installing your SQL Server instance.

For more information on setting up SQL Server security for Sage Estimating, see the Installation
and Administration Guide.

Note: You can install an approved instance of SQL Server side by side on a computer where
SQL Server 2012 is also installed. Be aware that installing Sage Estimating may then result in an
"Install completed with errors" message. However, the resulting Sage Estimating installation
operates correctly.

Sage Estimating (SQL) v23.1 11


Chapter 3

SQL Server Express Installation


Microsoft SQL Server Express comes as an optional component with the Sage Estimating install
package. It installs automatically when you select certain Sage Estimating installation options.

Note: If you are operating in a workstation/server environment, you do not need to install SQL
Server on the workstations. However, you can install SQL Server locally if you want to maintain a
copy of your estimating data.

Follow the instructions below to install SQL Server Express from the install package.

1. Open the Select Installation Options for Sage Estimating window by double-clicking SetMeUp.exe
in your local install folder.

2. The install folder is created wherever you download the Sage Estimating install files. For example,
if you download the install files to C:\Users\Public\Public Documents, look in this folder for the
SetMeUp.exe file.

The Select Installation Options for Sage Estimating window

3. In the Select installation options for Sage Estimating window, select Create a new local SQL
Server instance.

4. In the Enter new instance name box, type a name for the new SQL Server instance (database
server) in the box and click [OK].

12 Sage Estimating (SQL) v23.1


SQL Server Guide

5. The default name for the instance is SAGE_ESTIMATING. However, you can give the instance
any name you want, provided it is not the same as an existing SQL Server instance on the
computer.

6. Click [Next], and then follow the on-screen instructions for installing Sage Estimating or Sage
Estimating server.

The software installer creates the new instance, and notifies you when the process is finished.

Note: Be sure to elevate your privileges at the prompt within two minutes of its appearance or the
installation will quit.

Installing SQL Server Express also installs SQL Server Management Studio Express, a tool for
performing database back up and restoration procedures and for assigning database
permissions.

Modified Installation
You may use a version of SQL Server that already exists on your computer, but it must be a supported
version. (For current information about supported operating systems, Internet browsers, Microsoft®
SQL Server®, and other software, and about system requirements for servers and client workstations,
refer to our Knowledgebase article System Requirements for Estimating v23.1.The system requirements
are the minimum for a computer running Estimating with one SQL Server instance. Running several
other business programs with multiple SQL Server instances may affect the performance of your
system.)

If you want to use your existing installation of SQL Server, create a new instance to operate alongside
your existing SQL Server instances. You can give the new instance any name you want. However, Sage
recommends naming the new instance an easily identified name such as SAGE_ESTIMATING.

After creating your new instance, ensure you assign the appropriate database permissions as outlined in
the Installation and Administration Guide.

Notes:
l If you plan to migrate existing data from a Pervasive-based version of Sage Estimating, you
need to install SQL Server or SQL Server Express on the destination computer or server.
l Restart your server or workstation after creating the new instance

Caution! Do not change the owner of any databases in the Sage Estimating instance.

Sage Estimating (SQL) v23.1 13


Chapter 4: FAQs

I already use a version of Microsoft® SQL Server® on my computer. Can I use this
version with Sage Estimating?
You need to use a version of SQL Server that Sage Estimating supports, and you need to create a new
instance for Sage Estimating that conforms to our recommended security settings. See "The SAGE_
ESTIMATING Instance" (page 2) for more information.

Note: You can install an approved instance of SQL Server side by side on a computer where
SQL Server 2012 is also installed. Be aware that installing Sage Estimating may then result in an
"Install completed with errors" message. However, the resulting Sage Estimating install operates
correctly.

If I already have a version of SQL Server installed, does installing Sage Estimating
upgrade my existing SQL Server version?
No. However, you can install SQL Server Express from the Sage Estimating setup and installation files
for use with Sage Estimating. You can then use both SQL Server versions in a side-by-side configuration
(meaning both versions are installed).

What are the minimum system requirements to install SQL Server?


For current information about supported operating systems, Internet browsers, Microsoft® SQL Server®,
and other software, and about system requirements for servers and client workstations, refer to our
Knowledgebase article System Requirements for Estimating v23.1.The system requirements are the
minimum for a computer running Estimating with one SQL Server instance. Running several other
business programs with multiple SQL Server instances may affect the performance of your system.

Which operating systems are supported with SQL Server?


For current information about supported operating systems, Internet browsers, Microsoft® SQL Server®,
and other software, and about system requirements for servers and client workstations, refer to our
Knowledgebase article System Requirements for Estimating v23.1.The system requirements are the

Sage Estimating (SQL) v23.1 14


Chapter 4

minimum for a computer running Estimating with one SQL Server instance. Running several other
business programs with multiple SQL Server instances may affect the performance of your system.

Are 64-bit platforms supported?


Yes, you can install SQL Server Express on the several 64-bit Windows platforms.

For current information about supported operating systems, Internet browsers, Microsoft® SQL Server®,
and other software, and about system requirements for servers and client workstations, refer to our
Knowledgebase article System Requirements for Estimating v23.1.

Note: The system requirements are the minimum for a computer running Estimating with one SQL
Server instance. Running several other business programs with multiple SQL Server instances
may affect the performance of your system.

Can SQL Server Express Edition installations be performed on substitute, mapped, or


compressed drives?
No, installations cannot be used on any of these configurations.

Can I use File Tools or other utilities to back up my SQL databases?


No. You need to detach your databases and then back them up after the process is complete. File Tools
and other utilities do not perform this function.

Use SQL Server Management Studio or SQL Server Management Studio Express to back up your SQL
data. Microsoft SQL Server Management Studio Express attaches and detaches the database
automatically during back up and restore procedures. For more information, see "Backing Up SQL
Server Databases" (page 35).

Will running a virus scanner on the SQL Server host machine affect performance?

Important! For performance reasons, if you plan to run a virus scanner on the machine that hosts
the SQL Server instance, you should exclude files that have MDF, LDF, NDF, BAK, TRN, and TRC
extensions. You should also exclude additional processes for the version of SQL Server that you
are running. For more information about the files and processes to exclude, see Microsoft
Knowledgebase article 309422 at http://support2.microsoft.com/kb/309422.

How can I test whether SQL Server is working in Sage Estimating?


The first time you start Sage Estimating or the Estimating Management Console after installing the Sage
Estimating software, you should be able to use the Configuration wizard to locate your SQL Server
instance. If you are able to use the Configuration wizard to successfully locate at least one SQL Server
instance, your installation of SQL Server is operating correctly.

15 Sage Estimating (SQL) v23.1


SQL Server Guide

If you are able to open or create estimates and databases in the Sage Estimating software, SQL Server
is operating correctly.

What do I need to be able to manage user access rights in SQL Server?


For Sage Estimating, security is managed entirely from within the Security feature of the Estimating
Management Console. You can create roles and their corresponding permissions to access various
Sage Estimating tasks and features.

You need to be belong to the Sage Estimating administrator role to create roles and assign them to other
operators. For more information about creating roles and permissions, refer to the Sage Estimating
Installation & Administration Guide or the Estimating Management Console in-product Help.

I can connect to a SQL Server instance on my local computer but why can't I connect
to a SQL Server instance on a remote server?
You may need to reconfigure your firewall settings. See "Firewall settings" (page 19).

Sage Estimating (SQL) v23.1 16


Chapter 5: Troubleshooting SQL Server

This section provides additional information if you have any difficulty installing or connecting to a
® ®
supported version of Microsoft SQL Server .

Installation Issues
The following paragraphs provide troubleshooting tips for installation issues.

Collation
Sage Estimating requires a special collation setting. Collation settings in SQL Server must be set to:
l Latin1_General
l Case-sensitive
l Accent-sensitive

These settings are configured automatically when you create the SQL Server Express instance from the
Sage Estimating install. You may sometimes see this listed in SQL Server as SQL_Latin1_General_CS_
AS.

Note: If you upgraded to SQL Server Express 2017, your collation settings may not correctly match
the settings required by Sage Estimating.

Compatibility
Sage Estimating requires SQL Server 2012, or higher.

SQL Server is designed so that multiple instances may exist on a single computer. Each instance is
independent of the others, and may use different versions or service packs.

You may need to remove the existing version to resolve any compatibility issues. However, be aware
that other software may be using the incompatible version. Contact your system administrator before
attempting to remove any incompatible version.

If you determine that the version can be removed safely, use Windows' Add or Remove Programs to
remove it (note that you may have to remove several entries to completely remove the version).

Sage Estimating (SQL) v23.1 17


Chapter 5

Connection Issues
The following paragraphs provide troubleshooting tips for connection issues.

Authentication mode
The authentication mode for the SQL Server instance you create for Sage Estimating must be set to
Windows Authentication and SQL Server Authentication (also referred to as "Mixed Mode") to work with
Sage Estimating. In this mode, SQL Server creates and maintains your login information. See
"Troubleshooting SQL Server" (page 17) for more information.

Changing the authentication mode


If the authentication mode is not set correctly, you can resolve this issue in SQL Server Management
Studio Express, as follows:

1. Start Microsoft SQL Server Management Studio Express.

Click Start > All apps > Microsoft SQL Server Express > SQL Server Management Studio.

2. Confirm that the correct Server type, Server name, and Authentication settings are correct, and
then click [Connect]. For example:
l Server type: Database Engine.
l Server name: Machine_name\instance_name
l Authentication: Windows Authentication

Note: If Windows Authentication does not work, try SQL Server Authentication. You need
to have security permission in SQL Server to access the database using this
authentication.

3. In the Object Explorer pane, right-click on the server name and select Properties.

You need to select the server name, not the folders below it, to see the Security option in the next
step.

4. Select Security.

5. Select SQL Server and Windows Authentication.

6. Click [OK] twice.

If the authentication mode is set correctly and you are still experiencing problems, contact your
system administrator to review your permission settings in Windows or SQL Server. See "Security
Administration" (page 23) for more information.

18 Sage Estimating (SQL) v23.1


SQL Server Guide

Database location
Your default database location may not be set correctly in the system registry. See "SQL Server Instance
Settings" (page 29) for verification instructions.

Firewall settings
If you experience communication issues with a remote SQL Server instance, you may be using a firewall
that is set up to block network traffic between your computer and the SQL Server instance. To allow
communication, you need to set two firewall exceptions:
l The SQL Server Database Engine service
l The SQL Server browser service

Notes:
l The following instructions are for use with Windows Firewall. If you are using another
firewall for your system, contact the firewall manufacturer for instructions on setting service
exceptions.
l Sage recommends contacting your system administrator if you need to change firewall
settings.
l This procedure does not cover setting firewall exceptions for installations on a workgroup. If
you are using SQL Server on a workgroup server, you need to set separate firewall
exceptions to allow your workstations to communicate with the SQL Server instance. Refer
to the Installation & Administration Guide for instructions.

Setting the SQL Server Database Engine exception


Set up a SQL Server Database Engine exception for each instance of SQL Server you use with Sage
Estimating.

1. Determine the path to your SQL Server computer.


2. On the computer or server where SQL Server is installed, open the SQL Server Configuration
Manager.
3. Start the SQL Server Configuration Manager.

Click Start > All apps > Microsoft SQL Server > SQL Server Configuration Manager.

The SQL Server Configuration Manager opens.

Sage Estimating (SQL) v23.1 19


Chapter 5

4. In the left-hand pane of the SQL Server Configuration Manager, select SQL Server Services.
5. In the right-hand pane, right-click on SQL Server (INSTANCE), where (INSTANCE) is the
SQL Server instance for which you are creating the firewall exception, and select Properties.
6. In the SQL Server Properties window, click the Service tab.

20 Sage Estimating (SQL) v23.1


SQL Server Guide

SQL Server Properties Window—Service Tab

7. In the Binary Path entry, note or record the path described within the quotation marks. This is the
file path to the SQL Server instance binary files (the path is contained only within the quotation
marks—ignore the text outside the quotes).
8. Open Windows Firewall.

Select Start > All apps > Windows System > Control Panel > System and Security > Administrative
Tools > Windows Firewall > Advanced Settings.

a. In the left-hand pane of the Windows Firewall with Advanced Security window, right-click
Inbound Rules, and then select New Rule.
b. In the New Inbound Rule wizard, select the Program option, and then click [Next].
c. Select the This program path option.
d. Click [Browse] and locate the sqlservr.exe file at the binary file path you recorded in step 1,
and then click [Open].
e. Select the Allow the connection option, and then click [Next].
f. Select the Domain, Public, and Private checkboxes, and then click [Next].
g. Type the name of your SQL Server instance in the Name box.
h. Click [Finish] to create the firewall exception for the SQL Server Database Engine service.

Sage Estimating (SQL) v23.1 21


Chapter 5

The Windows Firewall with Advanced Security window opens.

Setting the SQL Server browser service exception


1. Open Windows Firewall.

Select Start > All apps > Windows System > Control Panel > System and Security > Administrative
Tools > Windows Firewall > Advanced Settings.

2. In the left-hand pane of the Windows Firewall with Advanced Security window, right-click Inbound
Rules, and then select New Rule.
3. In the New Inbound Rule wizard, select the Port option, and then click [Next].
4. Select UDP as the protocol type.
5. Select the Specific local ports option, and then type 1434 in the corresponding box.
6. Click [Next].
7. Select the Allow the connection option, and then click [Next].
8. Select the Domain, Public, and Private checkboxes, and then click [Next].
9. Type SQL Server Browser Exception in the Name box.
10. Click [Finish] to create the firewall exception for the SQL Server browser service.

Network configuration
To connect with SQL Server, you need to have TCP/IP enabled.

22 Sage Estimating (SQL) v23.1


SQL Server Guide

Enable TCP/IP
If you are receiving network configuration errors, make sure that TCP/IP is enabled, as follows:

1. Select Start > Control Panel > Administrative Tools > Windows Firewall with Advanced
Security.
2. Start the SQL Server Configuration Manager.

Click Start > All apps > Microsoft SQL Server > SQL Server Configuration Manager.

3. Expand SQL Server Network Configuration.


4. Select Protocols for SAGE_ESTIMATING (or the name of your instance).
5. Right-click on TCP/IP and select Enable.
6. Click [OK].

Note: You need to stop and restart the SQL Server services for this change to take effect. See
"SQL Server services" (page 23) for more information.

Running a virus scanner on the SQL Server host machine


For performance reasons, if you plan to run a virus scanner on the machine that hosts the SQL Server
instance, you should exclude files that have MDF, LDF, NDF, BAK, TRN, and TRC extensions. You
should also exclude additional processes for the version of SQL Server that you are running. For more
information about the files and processes to exclude, see Microsoft Knowledgebase article 309422 at
http://support2.microsoft.com/kb/309422.

Security Administration
Operators using Sage Estimating require SQL Server permissions to the databases they are expected to
use. You assign permissions using the Roles and Permissions features in the Estimating Management
Console. For more information, see the Installation & Administration Guide.

If an operator is experiencing connection issues with a database, verify the operator belongs to a role
with the appropriate permissions.

SQL Server services


You may have several SQL Server services or instances, depending on the version of SQL Server you
are using. For SQL Server Express, the following are used:
l SQL Server (the name you assigned to the SQL Server instance)
l SQL Server Browser

If the service is not running, you can start it using SQL Server Configuration Manager.

Sage Estimating (SQL) v23.1 23


Chapter 5

To start the SQL Server Engine using SQL Server Configuration:


1. Start the SQL Server Configuration Manager.

Click Start > All apps > Microsoft SQL Server > SQL Server Configuration Manager.

2. Select SQL Server Services.


3. Right-click the service (for example, SQL Server (<instance name>)), and then click Start.

To stop the SQL Server Engine using SQL Server Configuration


Start the SQL Server Configuration Manager.

Click Start > All apps > Microsoft SQL Server > SQL Server Configuration Manager.

4. Select SQL Server Services.


5. Right-click the service (for example, SQL Server (<instance name>)), and then click Stop.

Determining the path to the SQL Server program


If you have multiple instances of SQL Server installed, each instance is independent of the others. To
determine the location of the SQL Server program for a particular instance, do the following:

1. Start Microsoft SQL Server Management Studio Express.

Click Start > All apps > Microsoft SQL Server Express > SQL Server Management Studio.

2. In the Connect to Server window, confirm that the correct Server type, Server name, and
Authentication are selected, and then click [Connect]. For example:

l Server type: Database Engine

l Server name: Computer_name\instance_name

l Authentication: Windows Authentication

If Windows Authentication does not work, try SQL Server Authentication. You require
security permission in SQL Server to access the database using this authentication.

3. Right-click the server name, and then select Properties.

The path is listed on the General page next to Root Directory. Make note of this path.

4. Click [Cancel] and then close the SQL Server Management Studio Express window to exit without
making any changes.

The program exists in the Binn directory, which is below the root directory you noted in step 4. For
example: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe. The
actual number in the path may be different depending on how many instances you have installed
on the computer.

24 Sage Estimating (SQL) v23.1


Chapter 6: Additional Information

The following is provided as additional resource material. It is included for reference only and is not
meant to imply that Sage supports, controls, or endorses any of the content. Be aware that titles, links,
and content can change and may not always be pertinent to your situation.

General Information
Instance Configuration:

http://msdn.microsoft.com/en-us/library/ms143531(v=sql.120).aspx

Microsoft SQL Server Datasheet:

http://download.microsoft.com/download/D/7/D/D7D64E12-C8E5-4A8C-A104-C945C188FA99/SQL_
Server_2014_Datasheet.pdf

Corruption
How to Rebuild the Master Database for SQL Server:

http://msdn.microsoft.com/en-us/library/dd207003(v=sql.120).aspx

Security
Password Policy:

http://msdn.microsoft.com/en-us/library/ms161959(v=sql.120).aspx

SQL Server Security White Papers:

http://social.technet.microsoft.com/wiki/contents/articles/13146.white-paper-gallery-for-sql-server.aspx

Strong Passwords:

http://msdn.microsoft.com/en-us/library/ms161962(v=sql.120).aspx

Sage Estimating (SQL) v23.1 25


Chapter 6

Services
How to Verify a Successful Installation of SQL Server Reporting Services:

http://msdn.microsoft.com/en-us/library/ms143773(v=sql.120).aspx

Managing the Database Engine Services:

http://msdn.microsoft.com/en-us/library/ms189925(v=sql.120).aspx

Managing Services Using SQL Server Management Studio:

http://msdn.microsoft.com/en-us/library/ms187478(v=sql.120).aspx

26 Sage Estimating (SQL) v23.1


Chapter 7: Glossary

BOL/Books On Line
SQL Server Books On Line. These are resource materials for SQL Server provided by Microsoft. Books
On Line is automatically installed with the Sage Estimating installation of SQL Server Express Edition.
You can also download a current copy at https://msdn.microsoft.com/en-us/library/ms130214
(v=sql.120).aspx.

Instance/Named Instance
A complete database environment, including the relational database management system software,
table structure, stored procedures, and other functionality.

Microsoft Desktop Engine (MSDE)


A database engine compatible with earlier versions of SQL Server.

sa
The system administrator for SQL Server.

SQL
Structured Query Language, the standardized language used in virtually all relational databases.

SQL Server Management Studio (SSMS)


The configuration tool used to manage all aspects of the SQL server.

Sage Estimating (SQL) v23.1 27


Chapter 7

SQL Server Management Studio Express (SSMSE/SSMS


Express)
A limited version of SQL Server Management Studio.

Stored Procedures
Database functions that allow advanced pre-compiled queries.

Transact-SQL
A robust scripting language supported by Microsoft SQL Server.

User Account Control (UAC)


A method of adding security to Windows by creating different access levels for administrators and
standard users. It also prevents standard users from changing system settings or affecting sensitive
system information.

28 Sage Estimating (SQL) v23.1


Appendix A: SQL Server Instance
Settings

® ®
If you have an existing instance of a supported version of Microsoft SQL Server installed, you can set
up another instance to work with Sage Estimating. (Options described in this section may vary slightly
depending on the edition you are installing.)

Note: If you choose to uninstall your existing instance first, restart your server before reinstalling to
avoid problems with the new installation.

Caution! Do not change the owner of any databases in the Sage Estimating instance.

Configure your new SQL Server instance using the settings outlined in the following sections.

Instance Configuration: SAGE_ESTIMATING Instance


You name your instance as part of Instance Configuration during the SQL Server installation.

Instance Configuration Settings

Sage Estimating (SQL) v23.1 29


Chapter A

You need to use a named instance. You can give the instance any name you want. However, Sage
recommends giving the instance a name that makes it easy to identify (such as SAGE_ESTIMATING).

Server Configuration: Collation Settings


You customize collation settings as part of the Server Configuration during the SQL Server installation.

30 Sage Estimating (SQL) v23.1


SQL Server Guide

In the Server Configuration dialog, on the Collation tab, click [Customize].

Collation settings must be Latin1_General, case-sensitive, and accent-sensitive (Latin1_General_CS_


AS).

Sage Estimating (SQL) v23.1 31


Chapter A

In the SQL Server collation customization window:


1. Select the Windows collation designator and sort order option (instead of SQL collation, which is
the default).

2. Select:

l Latin1_General (for the collation designator)


l Case-sensitive
l Accent-sensitive

3. Clear all other options.

Database Engine Configuration: Authentication Mode


You specify the authentication mode as part of Database Engine Configuration during the SQL Server
installation.

Authentication Mode Settings

32 Sage Estimating (SQL) v23.1


SQL Server Guide

The instance must support Mixed Mode authentication (Windows Authentication and SQL Server
Authentication). This means either Windows authentication or SQL Server authentication can be used to
access the database information.

When Windows authentication is used, the operator requires permissions to use SQL Server or be a
member of a group that has those permissions. In Windows authentication mode, SQL Server validates
the account name and password using information from the Windows operating system.

When SQL Server authentication is used, the operator requires system administrator (sysadmin) rights
in SQL Server. The SQL Server authentication is used for backward-compatibility and requires a strong
password.

Additional Recommendations
To ensure accurate performance, Sage strongly recommends making changes and verifications to the
following settings in SQL Server Management Studio and SQL Server Configuration Manager. Failure to
make these changes may result in poor Sage Estimating performance or communication issues.

Memory
Determine the amount of available memory on the server or workstation where SQL Server is installed.
To prevent SQL Server from consuming all available memory, use SQL Server Management Studio to
set the maximum amount of memory (in the instance properties) to a reasonable limit (such as 4 GB ) as
follows:

1. Right-click on the SQL Server instance and select Properties.


2. In the Server Properties window, click Memory (left-hand pane).
3. Set the Maximum server memory amount to 4000 (or whatever limit you determine).

Recovery Model
Sage recommends that you use the Simple recovery model for your Estimating database.

During the upgrade process, the program now shrinks the existing log file, which can become very large,
and it removes invalid estimates. However, it does so only if the database recovery model is set to
Simple in the SQL Server software. We do not recommend that you change the recovery model unless
your business requires features available only in a different model.

Communication protocol
Set the communication protocol settings for the Sage Estimating SQL Server instance as follows:

Sage Estimating (SQL) v23.1 33


Chapter A

1. Start the SQL Server Configuration Manager.

Click Start > All apps > Microsoft SQL Server > SQL Server Configuration Manager.

2. In the left-hand pane of the SQL Server Configuration Manager window, click the arrow next to
SQL Server Network Configuration to display all local SQL Server instances.

3. Select the instance associated with Sage Estimating (SAGE_ESTIMATING, by default).

4. In the right-hand pane right-click on a communication protocol and select Disable.

Repeat this step for all communication protocols except TCP/IP. Leave this protocol Enabled.

5. In the left-hand pane of the SQL Server Configuration Manager window, click the arrow next to
SQL Native Client 10.0 Configuration or SQL Native Client 11.0 Configuration (depending on your
SQL Server instance).

6. Click Client Protocols (left-hand pane).

7. In the right-hand pane right-click on a communication protocol and select Disable.

Repeat this step for all communication protocols except TCP/IP. Leave this protocol Enabled.

8. Close the SQL Server Configuration Manager.

9. Restart the service.

34 Sage Estimating (SQL) v23.1


Appendix B: Backing Up and Restoring
Using SQL Management Studio

Important! Sage Estimating Management Console includes Backup and Restore tools that we
recommend you use for backing up and restoring your Sage Estimating data. They are very
efficient processes that minimize the possibility of error. In addition, the Restore process
automatically upgrades databases to your current version if you backed them up using an earlier
version, which can save you time. For more information and step-by-step instructions, see the
Estimating Management Console help.

If you prefer to use SQL Server Management Studio or Management Studio Express to back up your
® ®
Microsoft SQL Server databases, follow the instructions in this appendix.

Note: To copy standard databases or address books, you need to use the Estimating Management
Console Backup and Restore tools.

Backing Up SQL Server Databases


If you choose to back up and restore your Sage Estimating data using the SQL Server tools, make sure
you include all the necessary steps in your back up procedures.

Your SQL Server database backup copy is generated in two steps:

1. Use SQL Server Management Studio (or Management Studio Express) to make a backup copy of
the database into a file folder.

The default location for this folder is C:\Program Files\Microsoft SQL Server\MSSQL10_
50.SAGE_ESTIMATING\MSSQL\Backup. (The actual number and instance name that appears in
the path may be different if you have multiple instances of SQL Server installed or if you named
your instance a different name.)

2. Make sure to include the SQL backup folder (referenced in step 1) when you perform your tape or
third-party backup.

Sage Estimating (SQL) v23.1 35


Chapter B

Notes:
l Be sure to perform regular tests of your backups to ensure they are working properly.
l You can perform backup and restore functions using SQL Server Management Studio
or Management Studio Express. Installing SQL Server Express from the Sage
Estimating setup and installation files installs a copy of SQL Server Management
Studio Express.
l SQL Server Management Studio Express automatically detaches and attaches the
database when you back up and restore.

Caution! The restore process overwrites any changes you make to the database between
creation of backup copies.

Backing up the SQL Database


1. Start Microsoft SQL Server Management Studio Express.

Click Start > All apps > Microsoft SQL Server Express > SQL Server Management Studio.

2. Select the database you want to back up from the Object Explorer pane.

3. Right-click the database, and then select Tasks > Back Up to open the Back Up Database
window.

36 Sage Estimating (SQL) v23.1


SQL Server Guide

4. Under Source (in the right-hand pane of the Back Up Database window), select the database to be
backed up from the Database list.

5. For the backup type, select Full.

6. For the backup component, select Database.

7. Under Backup Set, type a name for the database backup you are creating in the Name box.

8. If desired, also type a description for the backup in the Description box.

9. Set the desired expiration criteria for the backup in the Backup set will expire section.

10. Select the backup destination from the Destination list.

11. This list displays previously defined backup file paths and file names. The backup utility selects
the Backup folder in your SQL Server instance folder by default but you can add a new file path as
a destination by clicking [Add].

12. Click [OK]. A Backup of database completed successfully message appears when the backup
operation is finished.

13. You may now perform your normal tape or third-party back up procedures.

14. Be sure to include the SQL back up folder (or the folder where your backup copy is stored if you
selected another location in step 10). The default location for this folder is C:\Program
Files\Microsoft SQL Server\MSSQL10_50.SAGE_ESTIMATING\MSSQL\Backup. (The actual
number and the name that appears in the path may be different if you have multiple instances of

Sage Estimating (SQL) v23.1 37


Chapter B

SQL Server installed or if you named the instance a different name.)

Restoring the SQL Database


Caution! The restore process overwrites any changes you make to the database between creation
of backup copies.

1. Start Microsoft SQL Server Management Studio Express.

Click Start > All apps > Microsoft SQL Server Express > SQL Server Management Studio.

2. Select the database you want to restore from the Object Viewer pane.

3. Right-click the database, and then select Tasks > Restore > Database to open the Restore
Database window.

38 Sage Estimating (SQL) v23.1


SQL Server Guide

4. Select the database you want to restore in the To databasebox.

If you want to create a new database, type the name of the database in the To database box.

5. Under Source for restore, select From database, and then select the name of the backup
database copy you want to use for the restore operation.

6. In the Select the backup sets to restore table, select the checkbox for the database you want to
restore.

7. In the Select a page pane (in the upper left-hand corner of the window), click Options.

8. In the Restore Options area, select the Overwrite the existing database checkbox.

9. Click [OK].

A Restore of database completed successfully message appears when the restoration operation
is finished.

The restore process overwrites any changes you made to the database since the last time you
created a backup.

Sage Estimating (SQL) v23.1 39


Chapter B

After restoring a database


l If you restored an Estimates database, you need to run the security.fix procedure as follows:

1. In SQL Management Studio, locate and then expand the folder for the estimates database
that you restored.

2. Click Programmability -> Stored Procedures.

3. Scroll to the security.fix stored procedure, right click the file, and then click Execute Stored
Procedure.

4. Click [OK].

l Restored databases are automatically added to your Estimating system when you next run
Estimating, provided you have administrator privileges and your estimates and address book are
configured properly for the current version.

Note: You need to close and reopen Estimating to view the restored database.

40 Sage Estimating (SQL) v23.1

You might also like