SQL Server Guidelines

Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B

Envision for BACtalk

2
Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B
User agreement and limited warranty
IMPORTANT - PURCHASE OF ALERTON PRODUCTS OR USE OF SOFTWARE, FIRMWARE AND / OR ACCOMPANYING DOCUMENTATION (DEFINED BELOW) IS
SUBJECT TO LICENSE RESTRICTIONS AND LIMITED WARRANTY. CAREFULLY READ THIS AGREEMENT BEFORE USING ALERTON PRODUCTS, SOFTWARE,
FIRMWARE AND/OR DOCUMENTATION.
This is a legal "Agreement," concerning the purchase of Products and use of Software, Firmware and/or Documentation, between you, the "User" (either individually or as an
authorized representative of the company that is purchasing, has purchased, or is using the Products, Software, Firmware or Documentation) and Honeywell, 6670 - 185th
Avenue NE, Redmond, Washington 98052 USA. ("Honeywell").
PURCHASE OF ALERTON PRODUCTS OR USE OF SOFTWARE, FIRMWARE AND / OR ACCOMPANYING DOCUMENTATION INDICATES USER'S COMPLETE AND
UNCONDITIONAL ACCEPTANCE OF THE TERMS AND CONDITIONS SET FORTH IN THIS AGREEMENT.
Honeywell provides Alerton products ("Products"), software programs ("Software"), firmware, e.g., protocols, software program code, device drivers and related hardware
("Firmware") and accompanying documentation ("Documentation") and grants a non-exclusive and non-transferable license ("License") to User to use the Software and the
Firmware only on the following terms and conditions. Taken together, Products, licensed Software, licensed Firmware and accompanying Documentation are collectively
defined as "Alerton Product(s)" in this Agreement.
1. Copyright. The Software, Firmware and Documentation are copyrighted and protected by United States copyright laws and international treaty provisions and laws, contain
valuable proprietary products, information and trade secrets, and shall remain the property of Honeywell. User may not and shall not copy or otherwise reproduce or make
available to any other party any part or all of the Software, Firmware or Documentation nor decompile, disassemble, reverse engineer, manufacture or modify any portion of
the Products, Software, Firmware, Documentation or any portion of the same for any purpose or otherwise attempt to determine the underlying source code of the Software or
Firmware or permit any such action; provided however, User may either (a) make one (1) copy of the Software solely for backup or archival purposes, or (b) transfer one (1)
image of the Software to a single hard disk, CD or other comparable media, provided User keeps the original solely for backup or archival purposes.
2. License. User is hereby licensed to use one (1) copy of the Software for User's own use in operating the Products. User may not rent, lease or otherwise assign or transfer
all or any part of the Software, Firmware or Documentation. In addition, User may not sublicense, assign or transfer this License or Agreement, or any part thereof. Any
attempt to do so shall terminate this License and User's right to use the Software and Firmware and shall subject User to liability for damages to Honeywell. LICENSING TO
USER OF THE SOFTWARE AND FIRMWARE COMMENCES WHEN USER USES THE SOFTWARE, FIRMWARE AND / OR ACCOMPANYING DOCUMENTATION.
3. Copies, Modification or Merger. Except as specifically set forth in Paragraph 1, User may not copy, modify, transfer all or any portion of the Software, Firmware or Documen-
tation or merge it or them into another program, unless expressly authorized in advance in writing by Honeywell. User must, as a condition of this License, reproduce and
include the identifying marks, copyright and proprietary notices on any permitted copy of the Software, Firmware and Documentation. "Copies" shall include, without limitation,
any complete or partial duplication on any media, adaptations, translations, compilations, partial copies within modifications, mergers with other material from whatever source
and updated works. User will use its best efforts to prevent any unauthorized copying or other activity with respect to the Software, Firmware and Documentation.
4. Third-Party Beneficiary. For any software or other technology under this Agreement licensed by Honeywell from Microsoft( or other licensors, Microsoft or the applicable
licensor is a third party beneficiary of this Agreement with the right to enforce the obligations set forth in this Agreement.
5. Warranty. Honeywell warrants Honeywell manufactured or produced Alerton Products to be materially free from defects and to substantially conform to Honeywell's pub-
lished specifications for a period of twenty-four (24) months from date of shipment from Honeywell (the "Product Warranty Period"). This entire Section 5 is defined as the
"Warranty."
Honeywell also warrants Alerton Products that it has previously repaired or replaced for the greater of ninety (90) days from the date of their shipment from Honeywell or the
remainder of the Product Warranty Period of the originally shipped Alerton Product (the "Repair/Replacement Warranty Period").
During the Product Warranty or Repair/Replacement Warranty Period, Honeywell will repair or replace the applicable Alerton Products without charge and will add applicable
engineering changes and upgrades.
This Warranty only applies to defective materials and workmanship of Alerton Products and excludes defects that result from misuse, neglect, improper installation, unauthor-
ized repair or alteration, damage during or after shipping, accident and/or misapplication of such products. This Warranty does not apply to parts, equipment, software, firm-
ware, components, documentation or any other item that Honeywell does not manufacture or produce. This Warranty is also voided by removal or alteration of Alerton Product
identification labels.
Honeywell's sole responsibility with respect to Alerton Products shall be, within the applicable Product Warranty Period, to furnish a replacement Alerton Product (FOB fac-
tory) or, at the option of Honeywell, to repair and return (FOB Factory) the defective Alerton Product. HONEYWELL HEREBY EXCLUDES ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND ALL OTHER EXPRESS OR IMPLIED WARRANTIES WHATSOEVER WITH RESPECT TO
ALERTON PRODUCTS. In no event shall Honeywell be liable for personal injury, loss of profit, loss of production, loss of business or goodwill, business interruption, loss of
business information or data, loss due to delays, any other pecuniary loss, any cost or liability of Users or any other parties, to themselves or to others, increased or uncovered
operating or fixed costs, inefficiency, or any other special, exemplary, consequential, incidental, indirect or remote damages in any manner, directly or indirectly, related to
design, manufacturing, supply, installation or use of, or inability to use, Alerton Products, or any other act or failure to act by Honeywell or its agents or contractors.
HONEYWELL MAKES NO CLAIMS OR WARRANTIES WITH RESPECT TO THE SOFTWARE OR THE FIRMWARE AND SPECIFICALLY DISCLAIMS ANY IMPLIED WAR-
RANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE AND EXPRESS OR IMPLIED WARRANTIES THAT THE OPERATION OF THE SOFT-
WARE OR FIRMWARE OR ANY PORTION THEREOF WILL BE INTERRUPTION OR ERROR FREE. Notwithstanding anything to the contrary contained in this Warranty,
Honeywell shall not be liable to Users or any other parties for any damages, including, but not limited to consequential, incidental, indirect, special, exemplary remote or pecu-
niary damages and any stated or express warranties set forth in this warranty are in lieu of all obligations or liability for any damages arising out of or in connection with the use
or performance of, or inability to use, Alerton Products and the licensed Software and Firmware.
User's exclusive remedy and Honeywell's entire liability arising from or in connection with the Alerton Products, Software, Firmware, Documentation and/or this License and
Agreement (including, without limitation, any breach of any warranty, express or implied) shall be, at Honeywell's option, the repair or replacement of the Products or Software
or Firmware as applicable, as stated above. ACCORDINGLY, HONEYWELL AND ITS DESIGNATED DEALERS AND THEIR DESIGNATED ASSOCIATE DEALERS HAVE
EXCLUDED AND DISCLAIM ANY AND ALL IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE AND ALL OTHER WARRAN-
TIES, EXPRESS OR IMPLIED, WHATSOEVER, WITH RESPECT TO THE PRODUCTS, THE SOFTWARE, THE FIRMWARE, THE DOCUMENTATION AND/OR THE
LICENSE. USER HEREBY ACKNOWLEDGES THE SAME.
6. Remedies of Honeywell. IF USER BREACHES THIS AGREEMENT, USER'S LICENSE HEREUNDER SHALL BE AUTOMATICALLY TERMINATED. Upon termination,
User shall return the Software, Firmware and all Documentation to Honeywell and destroy any copies of the Software, Firmware and the Documentation or any portions
thereof which have not been returned to Honeywell, including copies resident on electronic or digital media. If User breaches this Agreement, Honeywell shall be entitled to all
damages suffered by Honeywell resulting from such breach and Honeywell shall be entitled to equitable and injunctive relief in addition to all other remedies at law. In this
regard, User acknowledges that its breach of any provision of this Agreement will cause Honeywell immediate and irreparable injury for which there are inadequate remedies
at law. The prevailing party in any dispute concerning this Agreement shall be entitled to the costs of collection and enforcement, including but not limited to reasonable attor-
neys' fees, court costs and all necessary expenses, regardless of whether litigation is commenced.
7. Export. Alerton Products are subject to regulation by local laws and United States government agencies, which prohibit export or diversion of certain products, information
about the products, and direct products of the products to certain countries and certain persons. User agrees that User will not export in any manner any Alerton Product or
direct product of Alerton Product, without first obtaining all necessary approval from appropriate local and United States government agencies.
8. RESTRICTED RIGHTS NOTICE. Alerton Products, Software, Firmware and Documentation have been developed entirely at private expense and are commercially pro-
vided with RESTRICTED RIGHTS. Use, duplication or disclosure by the U.S. Government or a U.S. Government subcontractor is subject to the restrictions pursuant to
DFARS 227.72013 (October 1988) and DFARS 52.227-19 (June 1987), as amended and as applicable. Manufacturer, licensor and publisher is Honeywell, 6670 - 185th Ave-
nue NE, Redmond, Washington 98052 USA.
9. Statute of Limitations. No action for any breach of a warranty, if any, deemed or actual, may be commenced more than one (1) year following the expiration of such warranty.
10. Other. User further agrees that this Agreement is the complete and exclusive statement of the agreement between User and Honeywell and supersedes any proposal or
prior agreement or any other communications between Honeywell or any of its representatives and User relating to the use of the Software, Firmware, Documentation and
purchase of the Products. This Agreement may only be modified by a physically signed writing between User and Honeywell. Waiver of terms or excuse of breach must be in
writing and shall not constitute subsequent consent, waiver or excuse. If any provision of this Agreement is finally determined to be unenforceable, the remaining provisions
shall remain in effect. The laws of the State of Washington and the United States, including U.S. copyright laws, shall govern this Agreement. Venue in the event of any suit,
proceeding or claim shall be in the courts located in King County, Washington, USA. If User has any questions regarding this Agreement, User may contact Honeywell by writ-
ing Honeywell at the above address.
This Agreement shall inure to the benefit of and be binding upon the parties and their successors, administrators, heirs and permitted assigns. Notwithstanding any termina-
tion of this Agreement and not in limitation of any other provision of this Agreement, User shall specifically continue to be fully obligated to comply with all of the requirements
of paragraphs one (1) through four (4), as if the Agreement were not terminated and all remedy provisions hereunder shall apply to any breach of such obligations.
SQL Server Guidelines
|
Contents
Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B
3
Contents
About this guide 5
Before you begin 5
MS Access or SQL Server? 6
SQL Server benefits 6
Supported SQL Server versions 6
Envision for BACtalk resources 7
SQL Server resources 8
SQL Server documentation 8
Local courses 8
Books 8
Online Help 9
Online papers and courses 9
Setting up Envision for BACtalk to use SQL Server 10
Repairing and compacting BACtalk job data 10
Backing up BACtalk job data 11
Installing SQL Server 2005 11
Installing Envision for BACtalk 11
Setting up the Enterprise options in Envision for BACtalk 12
Restoring BACtalk job data 13
General SQL Server guidelines for Envision for BACtalk 14
Envision for BACtalk v2.x system requirements 16
Recommended system requirements 16
Minimum system requirements 17
Hardware keys 18
SQL Server Guidelines
|
Envision for BACtalk
4
Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B
SQL Server Guidelines
|
About this guide
Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B
5
About this guide
SQL Server support is supported in Envision for BACtalk v2.5 and later. This
guide provides critical information and general guidelines for those users
responsible for designing, configuring, converting, troubleshooting and
maintaining BACtalk databases using SQL server databases. This document will
help you decide which database structure is appropriate for your job, guide you
through setting up Envision for BACtalk to connect to a SQL Server, and
provide guidelines for using SQL Server with Envision for BACtalk. This
document is Alertons primary SQL Server information resource. It does not tell
you how to use SQL Server; rather it points you to other training resources
created by SQL Server experts.
Before you begin
As with all upgrades, reading and following these instructions will substantially
ease the upgrade. You will also find detailed BACtalk installation information in
the Envision for BACtalk Installation and Startup Guide
(LTBT-TM-ADMIN26).
MPORTANT! Choose the right database structure for your BACtalk job. If you
choose to use SQL Server 2005 instead of MS Access, understand how to use
SQL Server 2005 before you begin. See SQL Server resources on page 8.
IMPORTANT! Understand how to use Windows Authentication before you
begin. See your Windows documentation for more information about Windows
Authentication.
IMPORTANT! Understand the system requirements before you begin. See
Recommended system requirements on page 16 and the documentation
included on your SQL Server 2005 CD.
SQL Server Guidelines
|
Envision for BACtalk
6
Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B
MS Access or SQL Server?
Envision for BACtalk v2.5 and later supports both MS Access and SQL Server
databases, so which database structure is right for your BACtalk job?
SQL Server benefits
All Envision for BACtalk versions prior to 2.5 use the MS Access database
structure. If you upgrade to 2.5 or later and convert the database structure to SQL
Server, your jobs can grow to Enterprise size while experiencing the following
additional benefits:
Enhanced overall performance
Faster execution time
Reliable data backups using off-the-shelf SQL Server tools
Secure data replication using off-the-shelf SQL Server tools
Supported SQL Server versions
Envision for BACtalk v2.5 and later supports the following SQL Server
versions:
SQL Server 2005
SQL Server 2000
SQL Server Express *
SQL Server 2005
Recommended version.
SQL Server 2000
Compatible starting with Envision for BACtalk v2.5.
SQL Server Express
IMPORTANT! *Use as a design tool ONLY to save time and money. SQL Server
Express is limited to a database size of 4GB.
You can design a new SQL job in SQL Server Express and then import it into a
full SQL Server 2005 job. You may also want to use SQL Server Express to
learn about SQL, but the database cannot grow large enough to successfully run
a BACtalk job. Smaller BACtalk jobs can use MS Access.
SQL Server Guidelines
|
Envision for BACtalk resources
Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B
7
Envision for BACtalk resources
Several other documents are available for information about Envision for
BACtalk and BACtalk system architecture.
Installation & Startup
Guide
(LTBT-TM-ADMIN26)
Operators
Manual
(LTBT-OP-EBT26)
Online Help
Programmers Guide
& Reference
(LTBT-TM-PRGRMR)
Display
Developers Guide
(LTBT-TM-DSPDV)
How do I install the
Envision for BACtalk
software?
What does a
particular feature do?
Why would I use this
feature?
I need detailed
information about
using the Envision for
BACtalk software.
I need an overview of the
concepts behind DDC
programming.
How do I get started
designing data
displays?
How do I configure the
Envision for BACtalk
software?
What do I need to
know before I set up
and use this feature?
I need detailed
information about a
specific dialog box or
window.
What are some of the
considerations I need to
think about before I start
creating a DDC program?
Are there some general
guidelines or tips on
good data display
design?
How do I set up and
engineer a job?
How do I change the
settings for a feature
if its not working as I
expected?
I need some help
figuring out what to
enter in this field in a
dialog box.
What do I need to know
before I begin using
VisualLogic?
What are the steps for
creating a new data
display?
How do I enter or change
information in Device
Manager?
I need an example of
how I might use this
feature.
What are the steps
for using a particular
feature?
What are BACnet objects
and properties?
How do I use Alerton
templates when
creating new displays?
How do I send
information or a DDC
program to a controller?
What calculations is
the system making
when I use this
feature?
What does this term
mean?
I need detailed
information about a
specific DDC function.
How do I edit an
existing display?
Tabl e 1 Envision for BACtalk documentation set resources
SQL Server Guidelines
|
Envision for BACtalk
8
Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B
SQL Server resources
Many resources are available for information about installing, configuring and
working with SQL Server 2005: product documentation included on the SQL
CD, local school courses, printed books, online Help, and online white papers
and courses.
SQL Server documentation
Included with your SQL Server 2005 installation CD:
Microsoft SQL Server 2005 Readme
Installation Requirements for SQL Server 2005
Local courses
Check with your local technical school, community college or university for
SQL Server training courses or certification programs. Particularly, SQL Server
courses about:
database administration
database security
database clustering
backing up data
data replication
Books
Envision for BACtalk v2.5 and later already has the SQL Server database design
in place so you will benefit more from book titles that cover SQL Server
operation and performance topics. Particularly, study SQL Server books about:
database administration
database security
database clustering
backing up data
data replication
Several titles include:
SQL Server 2005 Practical Troubleshooting Edited by Ken
Henderson, Slava Oks, Wei Xiao, Bart Duncan and Bob Ward
Data Modeling Made Simple by Steve Hoberman
Microsoft SQL Server 2005: Database Essentials by Solid Quality
Learning
Programming Microsoft SQL Server 2005 by Andrew J. Burst and
Stephen Forte
SQL Server Guidelines
|
SQL Server resources
Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B
9
Online Help
SQL Server online Help is a valuable resource and it is included on the SQL
Server installation CD. Just click the [?] Help button while installing or working
in SQL Server.
Online papers and courses
SQL Server Online Books: A Primer For New Users
http://www.sql-server-performance.com/index.aspx
SQL Server 2005 Management Tools Overview
http://www.microsoft.com/sql/techinfo/whitepapers/mngmttools.mspx
Affordable online courses available through Honeywells partner,
SkillSoft. Enrollment information is posted to the ASN, or email
Training@alerton.com for assistance. Here is a sample lit of titles:
The SQL Server 2000 Logical Data Model ID: 31901_eng 145 mins
To describe SQL Server data entries and their normalization
Installing SQL Server 2005 ID: 234620_eng 180 mins
To install SQL Server 2005 and upgrade to SQL Server 2005 from previous versions.
Designing an Application Solution for SQL Server 2005 ID: 256066_eng 175 mins
Recognize how to design and build a database model and a physical database, and how to
secure it.
Configuring SQL Server 2005 ID: 234633_eng 180 mins
To configure a SQL Server instance and create a database, configure logins, users, and schemas
for a database, and set up a linked server configuration.
SQL Server 2005 High Availability and Disaster Recovery ID: 234771_eng 180 mins
To implement database mirroring, log shipping, database snapshots, and data replication in SQL
Server 2005.
Managing and Maintaining SQL Server 2005 Databases ID: 234704_eng 195 mins
To manage and maintain SQL Server 2005 databases.
Designing a SQL Server 2005 Transaction Strategy ID: 256872_eng 115 mins
Recognize the different levels of isolation and granularity to manage concurrency and execute a
transaction strategy in SQL Server 2005.
Managing Database Data in a SQL Server 2005 Environment ID: 237888_eng 195 mins
To recognize how to create and deploy SSIS packages, and enforce data quality and data
integrity in a SQL Server 2005 database.
Creating/Implementing Database Objects in SQL Server 2005 ID: 234647_eng 190 mins
To create and implement key database objects in SQL Server 2005.
Retrieving Data and Running Queries in SQL Server 2005 ID: 234661_eng 180 mins
To perform relational data and XML data management tasks, and work with assemblies and
transactions in SQL Server 2005.
Designing a Database Server Infrastructure for SQL Server 2005 ID: 236740_eng 130 mins
To specify the appropriate requirements for implementing SQL Server 2005, identify suitable
instance and physical storage strategies, and determine the appropriate way to design a
database consolidation plan, given a SQL Server scenario.
SQL Server Guidelines
|
Envision for BACtalk
10
Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B
Setting up Envision for BACtalk to use SQL Server
The key steps for successfully setting up Envision for BACtalk to work with
SQL Server 2005 include:
IMPORTANT! See the Envision for BACtalk Installation and Startup Guide
(LTBT-TM-ADMIN26) for information about merging a previous BACtalk job
with a v2.6 job. This merge information applies to both Conventional and SQL
BACtalk jobs.
1. Install SQL Server 2005
(See page 11)
2. If applicable, back up the legacy job using the legacy version of
Envision for BACtalk.
(See page 11)
3. Install Envision for BACtalk, the network driver and the hardware key
driver.
(See page 11)
4. If this computer is a server, install the hardware key.
(See page 18)
5. Start Envision for BACtalk as an Administrator, enter the
LocalAdministrator credentials, and then close Envision for BACtalk.
6. Restore the backed up job in Envision for BACtalk (Tools > Restore
BACtalk Job > Restore Entire Backup).
(See page 13)
7. Start Envision for BACtalk as a normal user and log into the restored
job.
Envision for BACtalk automatically converts the restored legacy data to
v2.5 or later conventional format (Access/Jet) during the startup
process. The progress monitor tracks the installation and conversion
process.
Not e The installation and conversion process from a legacy to a v2.5
or later BACtalk job may take several hours, depending on job size.
8. Set the Enterprise options (General System Setup > Network tab > Site
Configuration) and then test the SQL Server connection. If prompted,
click Yes to allow BACtalk to build any missing databases.
9. Shut down, restart Envision for BACtalk, and then log into the job.
10. Back up your new Envision for BACtalk SQL Server job and retain it
for future use, if needed.
(See page 11)
Repairing and compacting BACtalk job data
IMPORTANT! Always repair and back up your job before you convert from
MS Access to SQL Server because once converted, you cannot convert your
SQL Server databases back to Access due to the new and improved database
structure introduced for SQL support.
SQL Server Guidelines
|
Setting up Envision for BACtalk to use SQL Server
Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B
11
To reduce database size, a job database should be repaired and compacted after
backing it up. BACtalk operator workstation software includes a tool you can
use to compact and repair all the database files associated with your site.
Operating conditions may cause database file performance to degrade over time
and the compact and repair tool can help improve performance.
About the repair operation
The repair operation repairs a database that was marked as possibly corrupt by
an incomplete write operation. This can occur if an application closes
unexpectedly due to a power outage or computer hardware problem. The repair
operation validates all system tables and indexes.
About the compact operation
Compacting your database is similar to defragmenting. It consolidates database
files on the hard disk, rearranging how the files are stored so they use disk space
more efficiently.
See the Envision for BACtalk Installation and Startup Guide
(LTBT-TM-ADMIN26) for more information about repairing and compacting a
BACtalk job.
Backing up BACtalk job data
Backing up a BACtalk job creates a zip file of all job information, which can be
restored later if necessary. If you are upgrading from an earlier version and will
install Envision for BACtalk on a new computer, use the Backup utility to move
existing job files to the new computer. You can copy the zip file(s) to a CD or
any media, and then use the Restore utility on the new computer. See General
SQL Server guidelines for Envision for BACtalk on page 14 for more
information.
See the Envision for BACtalk Installation and Startup Guide
(LTBT-TM-ADMIN26) for more information about backing up a BACtalk job.
Installing SQL Server 2005
Install SQL Server 2005 according to the documentation set included with your
SQL Server 2005 CD. See SQL Server resources on page 8 for product
documentation and training information.
Installing Envision for BACtalk
By default, Envision for BACtalk 2.x is installed in C:\Alerton\BACtalk\2.x,
which is a different default directory from BACtalk for Windows.
CAUTI ON Do not install Envision for BACtalk to the same directory where
BACtalk for Windows or other Envision for BACtalk versions are installed if
you plan to continue using them on this operator workstation. If installed in the
same directory, Envision for BACtalk v2.x will fully replace earlier BACtalk
versions.
1. Insert the CD-ROM into an available CD-ROM drive.
SQL Server Guidelines
|
Envision for BACtalk
12
Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B
The setup program launches automatically. Some computers may have
auto-start disabled. In this case, open Windows Explorer and double-
click the Setup.exe program on the CD-ROM.
2. Follow the instructions that display on your screen.
SQL Server support was first supported by Envision for BACtalk v2.5. This
guide is focused on the SQL Server portion of the Envision for BACtalk 2.6 or
later installation process. See the Envision for BACtalk Installation and Startup
Guide (LTBT-TM-ADMIN26) for more information about installing BACtalk.
Setting up the Enterprise options in Envision for BACtalk
After you install SQL Server and then Envision for BACtalk, configure the
system to support SQL Server. Connect the BACtalk server to the SQL Server
database and then test the connection.
To set up the Enterprise options in BACtalk
1. Start Envision for BACtalk and log in with a valid username and
password.
2. On the Tools menu, select General System Setup, click the Network tab
and then click Site Configuration.
SQL Server Guidelines
|
Setting up Envision for BACtalk to use SQL Server
Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B
13
3. Select This Computer is the BACtalk Server and then select This
Computer is an Enterprise Server.
4. Click Database Configuration.
5. Type in the name of the SQL Server.
Enter the exact name of the SQL Server or the BACtalk server and the
SQL Server will not be able to find each other.
NOTE If several instances of SQL Server are installed on the same
computer, you may also need to include the instance name.
6. Click Test Connection to verify that the BACtalk server can connect to
the SQL Server database.
If the server connection test is successful but the database does not yet
exist, create the database if you have the privilege to create it.
Otherwise, contact your database administrator.
Restoring BACtalk job data
Once you have installed Envision for BACtalk and successfully connected it to
the SQL Server, restore your backed up BACtalk data. The next time Envision
for BACtalk is started, BACtalk will detect the SQL database structure and
automatically convert the imported job data into the new SQL database structure.
Larger Access databases have been separated into smaller SQL databases to
improve performance and data reliability. For example, BACtalk trendlogs are
now stored in their own SQL database.
See the Envision for BACtalk Installation and Startup Guide
(LTBT-TM-ADMIN26) for more information about restoring BACtalk job data.
SQL Server Guidelines
|
Envision for BACtalk
14
Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B
General SQL Server guidelines for Envision for BACtalk
See official Microsoft SQL Server documentation to learn how to use SQL
Server, but review these Alerton guidelines for using SQL Server with Envision
for BACtalk v2.5 or later.
If using Windows Authentication, understand how it works before you
begin.
Use SQL Server 2005 and understand how it works before you begin.
Envision for BACtalk v2.x installs by default to a directory that does not
conflict with previous versions (C:Alerton\BACtalk\v2.x).
Once the Envision for BACtalk 2.5 installation is complete and SQL
Server support is running correctly, back it up. Save this backed up job
in case you run into problems later.
Do not restore BACtalk data to a mapped location. Restore to a local
location only. For example, do not use REP.INI to point to a shared
drive.
During installation of SQL Server 2005, do not leave the SQL Server
Database field blank. Enter a name for the SQL Server.
You must know the exact SQL Server name when connecting to the
BACtalk server; otherwise, BACtalk cannot find it. You may also use an
IP address.
Upgrade a BACtalk MS Access database to SQL Server once. The data
cannot be converted back to Access. Back up your job before upgrading
to Envision for BACtalk 2.5 or later. Once you have successfully
installed BACtalk and converted to SQL Server, immediately back up
the new SQL job and use it to restore the job if something goes wrong.
Envision for BACtalk does not back up the SQL Server database itself.
Use standard off-the-shelf SQL Server administration tools to back up
the database.
Use the SQL Server tools included with the SQL Server Install CD to
locate BACtalk server data:

SQL Server Surface Area Configurator
This tool provides extra security for your data. These features are
disabled by default until the SQL DBA decides to enable them.

SQL Server Configuration Manager
Use this tool to configure general server service settings.

SQL Server Management Studio (SSMS)
Designed after Visual Studio, this tool is a unified database
administration and database development environment.
Use Simple not Full Recovery mode when not running periodic SQL
Server backups.

When the database is set up to use the Full Recovery model, the SQL
Server database transaction log (the .LDF file for that database) expands
and eventually fills up the disk. Once that happens, no more data can be
written to the database and a database administrator must fix the
SQL Server Guidelines
|
General SQL Server guidelines for Envision for BACtalk
Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B
15
problem.

In Full Recovery model, the database administrator must do periodic
backups in order to prevent unchecked growth.

Note Simply setting a maximum size limit to the transaction log file
does not fix the problem because the database stops working when the
file fills up.

If the database is created by a database administrator prior to running
Envision for BACtalk, the administrator can set it up with any options
needed to fit the backup and recovery strategy. If BACtalk creates the
database, it creates a database that is an exact copy of the SQL Server
model database. The administrator can set the options of the SQL Server
model database in any way desired so that when BACtalk uses it to
create the BACtalk database, it uses the same options as the SQL model.

Prevent the transaction log from growing without bounds by setting the
Recovery model to Simple. This limits the transaction log without
requiring constant backups or checkpoints. However, if the site requires
maximum database integrity and backup capability, you may want to
use a more robust recovery model. Remember that the transaction log
file will grow during normal BACtalk operation and the database
administrator will need to schedule regular backups or checkpoints to
control log file size and keep the database running.

You can change the Recovery model from Full to Simple at any time
after creating the database if the disk is not filled. If it is full, then it is
too late and the database administrator will have to fix it.
SQL Server Guidelines
|
Envision for BACtalk
16
Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B
Appendix
This section contains reference information and forms that may be useful during
Envision for BACtalk installations and upgrades.
Envision for BACtalk v2.x system requirements
This document applies to Envision for BACtalk v2.5 and later. Site requirements
vary widely, and the system components and recommendations made in this
section are only guidelines. Large sites with demanding data processing
requirements may place a greater demand on servers and operator workstations.
The server is the most important BACtalk component on site and should have
hardware capable of meeting these demands. Server performance depends
mostly on available RAM, processor speed, and hard disk space.
Recommended system requirements
These requirements seek a balance between cost and performance. Although
these requirements will provide sufficient performance on most sites, some sites
may benefit from a computer that exceeds these recommendations.
Install an extra, dedicated CPU to handle BACtalk auto-archiving, which is a
powerful yet processor-intensive feature. For Enterprise jobs, more processing
power is better. We recommend using two dual-core processors to enable your
system to operate at optimal performance and to provide some growing room.
Site using MS Access
Use these recommended system requirements for your Envision for BACtalk
server running MS Access:
3.0 GHz Pentium 4 with HyperThreading or better
1 GB RAM or better
USB port
40 GB hard disk or better (large jobs may require more)
High-performance graphics adapter
Network interface card (100/1000 Mbps)
Printer access
Keyboard, monitor, mouse, CD-ROM drive
Windows 2000 Professional, Windows XP Professional SP-2, Windows
Server 2003 (with SP1 is supported), or Vista
Visio 2003 (optional)
Note Installing more hardware may help a slow BACtalk conventional job to
speed up. However, the total performance is limited by reliance on the Access/
Jet database technology. Auto-archiving may slow down conventional BACtalk
jobs because Access/Jet runs auto-archiving and job operations such as
trendlogs, the user interface, the opening of lists, and client/server
communications. Auto-archiving is designed for SQL Server jobs and still
SQL Server Guidelines
|
Envision for BACtalk v2.x system requirements
Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B
17
allows SQL jobs to perform quickly. Upgrade a slow BACtalk conventional job
to SQL Server.
Site using SQL Server
Use these recommended system requirements for your Envision for BACtalk
server running SQL Server:
Pentium 4, 3.0 GHz or better
2 GB RAM or operating system requirements, whichever is greater
USB port
40 GB hard disk or better (large jobs may require more)
High-performance graphics adapter
Network interface card (100/1000 Mbps)
Printer access
Keyboard, monitor, mouse, CD-ROM drive
Windows 2000 Professional, Windows XP Professional SP-2, Windows
Server 2003 (with SP1 is supported), or Vista
Visio 2003 (optional)
Note You may use multiple computers to achieve the processor requirement on
jobs running SQL Server. This ensures optimal performance and prevents
database access from becoming the throughput bottleneck.
Minimum system requirements
These requirements reflect the absolute minimum threshold for running Envision
for BACtalk v2.5 and later and even then, performance will be limited and may
be noticeably poor. If your computer does not meet these minimum
requirements, you must upgrade it to run Envision for BACtalk v2.5 or later.
CAUTI ON Windows 95 and Windows ME are not supported operating systems
for running Envision for BACtalk v2.5 or later. Upgrade to one of the supported
operating systems listed.
Site using MS Access
Pentium 4, 3.0 GHz or better
1 GB RAM or operating system requirements, whichever is greater
40 GB hard disk
USB port
16-bit SVGA adapter with 2MB RAM
Network interface card (10/100 Mbps)
Printer access
Keyboard, monitor, mouse, CD-ROM drive
Windows 2000, Windows XP SP-2, Windows Server 2003 or Vista
SQL Server Guidelines
|
Envision for BACtalk
18
Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B
Note For Envision for BACtalk, use the Aler-Modem, BCM-MODEM or the
BTI-MDM to meet your modem needs.
Site using SQL Server
Pentium 4, 3.0 GHz dual core
2 GB RAM or operating system minimum requirements, whichever is
greater
USB port
40 GB hard disk
16-bit SVGA adapter with 2MB RAM
Network interface card (10/100 Mbps)
Printer access
Keyboard, monitor, mouse, CD-ROM drive
Windows 2000, Windows XP, or Windows Server 2003
Note For Envision for BACtalk, use the Aler-Modem, BCM-MODEM or the
BTI-MDM to meet your modem needs.
Hardware keys
The hardware key is a critical component of the Envision for BACtalk software
package. Envision for BACtalk uses a scaled hardware key system that enables
operator workstations to run the Envision for BACtalk software without a key
locally installed.
Depending on the key level, Envision for BACtalk supports a different number
of operator workstations and devices. Devices are defined as BACnet devices
other than the BACtalk operator workstations.
You can check which hardware key is installed and the number of devices
supported by choosing About Envision on the Help menu.
For Envision for BACtalk v2.5 or later, you must upgrade to an ENV-BT-xxxx
hardware key if you have added devices or operator workstations (or both) that
exceed what your current key supports. See Table 2 for more information.
Note If you are upgrading from an earlier version of BACtalk operator
workstation software, you can use the BTW-KEY-TECH hardware key with
Envision for BACtalk. It supports unlimited devices but times out after 8 hours
of continuous operation and Envision for BACtalk must be restarted to receive
system updates. You may also perform design work with a tech key.
Extra small (XS) Up to 11 devices: 1 server, 0 client workstations, 10 other devices.
WEBtalk and BCM-WEB do not count as workstations but each
counts as a device.
Small (SM) Small job: 1 server, 0 client workstations, 50 devices. Neither
WEBtalk nor BCM-WEB counts as a workstation but they each
count as a device.
Medium (MED) Medium job: 1 server, 2 client workstations, 150 other devices.
Neither WEBtalk nor BCM-WEB counts as a workstation but they
each count as a device.
Large (LRG) Unlimited usage: unlimited devices, unlimited client workstations
Enterprise 1 (ENT-
1)
Enterprise job: 1 server, unlimited client workstations, unlimited
other devices. Supports both MS Access and SQL Server
databases.
IMPORTANT! This is the only key that supports SQL Server.
Tech Key
(BTW-KEY-TECH)
Unlimited usage. Times out after 8 consecutive hours of operation.
SQL Server Guidelines
|
Hardware keys
Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B
19
Note USB keys have a U at the end of the part number.
Envision for BACtalk uses Device Manager to enforce key level conformance.
When Envision for BACtalk starts, it checks the number of device records in
Device Manager and compares this count with the hardware key found. If more
records than are allowed are present in Device Manager, a message displays and
the first 11, 50, or 150 devices (depending on the key) appear. Envision for
BACtalk counts devices and monitors conformance on an ongoing basis. Any
time a device is added to Device Manager, Envision for BACtalk checks for
hardware key conformance.
If the device count is greater than the key allows, a message appears that a key
upgrade is required. This upgrade message is repeated once daily. Data from
devices in excess of what the key supports return no entry in lieu of system
data.
See the Envision for BACtalk Installation and Startup Guide
(LTBT-TM-ADMIN26) for more information about hardware key behavior.
Tabl e 2 Hardware key levels and the number of devices they support
New 2.5 and 2.6
keys
Description
SQL Server Guidelines
|
Envision for BACtalk
20
Honeywell. All Rights Reserved. LTBT-TM-SQL Rev. B