Aveva Instrumentation Installation User Guide

AVEVA Instrumentation
Installation
User Guide
AVEVA Solutions Limited
Disclaimer
AVEVA Instrumentation provides instrument sizing calculations for estimation purposes only, end users of the
software should not rely on the calculations produced by the software for design purposes. End users should seek
the advice of certified equipment suppliers prior to specifying or purchasing equipment.
To the fullest extent permissible at law:
a) AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free from viruses;
b) AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar losses; loss of
anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of data or information; any
special, indirect, consequential or pure economic loss, costs, damages, charges or expenses which may be
suffered by the customer, including any loss suffered by the customer resulting from the inaccuracy or invalidity of
any data created by the AVEVA software, irrespective of whether such losses are suffered directly or indirectly, or
arise in contract, tort (including negligence) or otherwise;
c) AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with the
performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year in which the
customer's claim is brought.
In the event of any conflict between the above clauses and the analogous clauses in the software licence under
which the AVEVA software was purchased, the clauses in the software licence shall take precedence.
Copyright
All intellectual property rights, including but not limited to, copyright in this manual and the associated software,
(including source code, object code, and any data) belongs to or is validly licensed by AVEVA Solutions Limited or
its subsidiaries.
All rights are reserved to AVEVA Solutions Limited and its subsidiaries. The information contained in this document
is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without
the prior written permission of AVEVA Solutions Limited. Where such permission is granted, it expressly requires
that this Disclaimer and Copyright notice is prominently displayed at the beginning of every copy that is made.
The manual and associated documentation may not be adapted, reproduced, or copied, in any material or
electronic form, without the prior written permission of AVEVA Solutions Limited. The user may also not reverse
engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the product described in
this publication may be incorporated into any third-party software, product, machine, or system without the prior
written permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictly
prohibited, and may give rise to civil liabilities and criminal prosecution.
The AVEVA products described in this guide are to be installed and operated strictly in accordance with the terms
and conditions of the respective licence agreements, and in accordance with the relevant User Documentation.
Unauthorised or unlicensed use of the product is strictly prohibited.
Copyright 2000 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
The AVEVA Instrumentation user interface is based on the Microsoft® Office Fluent™ user interface.
Trademarks
AVEVA and Tribon are registered trademarks of AVEVA Group plc or its subsidiaries. AVEVA product names are
trademarks or registered trademarks of AVEVA Solutions Limited or its subsidiaries. Unauthorised use of
trademarks belonging to AVEVA Group plc or its subsidiaries is strictly forbidden.
Fluent is a trademark of Microsoft Corporation and the Fluent user interface is licensed from Microsoft Corporation.
The Microsoft Office User Interface is subject to protection under U.S. and international intellectual property laws
and is used by AVEVA Solutions Limited under license from Microsoft.
AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom.
Installation User Guide
Revision Sheet
Date Version Comments / Remarks

March 2012 Copyright added to all pages.
March 2013 12.1.SP1 Updates incorporated
Contents Page
Installation
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Database Systems Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Project Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Guide Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Client Computer Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Microsoft .NET Framework 4.0 Runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
AVEVA Instrumentation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Installing a Full Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2
Installing a Partial Release (Fix Release) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2
License Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2
Project Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1

Selecting an Existing Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1
Creating a New Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2
SQL Server Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:5
SQL Server Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:7
AVEVA Instrumentation User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:8
Hardware and Software Requirements for Installing SQL Server .A:1

SQL Server 2008 R2 (SP3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:1
Hardware and Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:2
© Copyright 2000 to current year. i 12 Series

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
Processor, Memory, and Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . A:4

Cross-Language Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:17
Extended System Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:17
Hard Disk Space Requirements (32-Bit and 64-Bit). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:17
Installing SQL Server on a Domain Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:17
Supported Clients (64-Bit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:18
SQL Server Express 2008 Remote Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:18
SQL Server 2012. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:19
Hardware and Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:20
Processor, Memory, and Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . A:23
Editions of SQL Server 2012 supported by AVEVA for use with AVEVA Instrumentation. A:24
Cross-Language Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:28
Extended System Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:29
Hard Disk Space Requirements (32-Bit and 64-Bit). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:29
Storage Types for Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:29
Installing SQL Server on a Domain Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:30
Upgrading Access Databases to SQL Server Databases . . . . . . . .B:1

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B:1
Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B:1
Migration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B:5
© Copyright 2000 to current year. ii 12 Series

Introduction
1 Introduction
AVEVA Instrumentation is a client-server application. The application modules are installed

on client (end-user) workstations and the database is installed on a server that is accessible
by all users on the network.
AVEVA Instrumentation also requires a common project folder in which templates are stored
and files such as drawings and datasheets are saved and which is accessible to all the
project users.
1.1 Database Systems Supported

AVEVA Instrumentation supports the Enterprise, Standard and Express versions of
Microsoft SQL Server 2008 R2 SP3 and SQL Server 2012.
Note: A defect in SQL Server 2008 (all editions) means that it returns too many rows when
providing a filter to the SQL statement. This can affect data returned into the grids in
AVEVA Instrumentation. This has been fixed in the SP3 release by Microsoft, hence
we support only the SP3 versions.
Express is available as a free download from the Microsoft website.
1.2 Project Folders

AVEVA Instrumentation uses a group of folders to store files per project. Ideally all these
folders should be under a single project ‘root’ folder. These folders are created by AVEVA
Instrumentation on project setup (if they do not already exist). The project folders need to be
accessible by all users that require access to AVEVA Instrumentation documents, for
example, your AVEVA Instrumentation team must have network security rights to read/write
to these folders.
1.3 Guide Structure
Introduction Introduction to the AVEVA Instrumentation application.
Installation Describes the minimum requirements for each end user PC

and the procedure for installing AVEVA Instrumentation.
Project Setup Describes how to setup an AVEVA Instrumentation project.
© Copyright 2000 to current year. 1:1 12 Series

Introduction
Hardware and Software Describes the hardware, operating systems and software
Requirements for Installing environments required for SQL Server installations.
SQL Server
Upgrading Access Describes how use the AccessMigration tool to upgrade

Databases to SQL Server Access project databases to SQL Server project database.
Databases

Installation
2 Installation
2.1 Client Computer Requirements

The minimum requirements for each end user PC are:
• Microsoft Windows XP Professional (with SP3 or above) or Windows 7 SP1
Professional and above.
• Pentium P4 3GHz min. or any Core2 2GHz+.
• RAM: 2Gb min, 4Gb min for Microsoft Windows 7.
• XGA monitor (we recommend 1280x1024 min.).
AVEVA Instrumentation requires the Microsoft .NET Framework 4.0 (runtime), a free
download from Microsoft.
If you intend creating AutoCAD drawings you are required to have AutoCAD.
Note: AutoCAD 2012 and 2013 are the supported versions.
If you intend creating and printing datasheets you are required to have Microsoft Excel
installed (Excel 2007 and 2010 supported).
Since AVEVA Instrumentation processes lots of information a faster computer with more
memory will perform better than a PC with less memory and a slower processor, particularly
when auto generating drawings and datasheets, and when loading large datasets for
equipment terminations and component layouts.
Note: If a workstation has less than 512Mb RAM or has a monitor less than 1024 x 768, the
installer will not install AVEVA Instrumentation. Furthermore, AVEVA Instrumentation
cannot be installed unless the Microsoft .NET Framework 4.0 is already installed.
2.2 Microsoft .NET Framework 4.0 Runtime

All AVEVA Instrumentation modules use Microsoft's .NET Framework 4.0, so the .NET
Framework 4.0 runtime must be installed on a client workstation. You should install the .NET
Framework 4.0 runtime before installing AVEVA Instrumentation on it. You can download the
.NET Framework 4.0 from the Microsoft website.
2.3 AVEVA Instrumentation Setup

You are required to have Windows Administrator rights on your workstation to install AVEVA
Instrumentation.
• Insert the installation disk into workstation's drive. It will run automatically.

Installation
• The Welcome to this AVEVA DVD page will then be displayed in a browser window.
Click on the Click for contents link.
• A page will then be displayed listing the products on the disk. Select the AVEVA
Instrumentation option.
• The next page will provide access to the latest user documentation and release notes.
View these as required, and then select the INSTALL option.
• Alternatively, run the setup.exe file on the installation disk, located in a sub-folder of
the “int” folder, for example “\int\t10444\ainst120SP3”.
• The AVEVA Instrumentation Setup wizard is then started.
Note: If you are running Windows 7 or Windows Server 2008 right-click on the Setup.exe
file and click Run as Administrator.
2.3.1 Installing a Full Release

If you are installing a full release the following steps will install AVEVA Instrumentation:
• Start the installation wizard as described above. On the welcome screen click the Next
button to proceed.
• Select which shortcuts you require.
• Select the products you wish to install. By default, all modules except Process
Engineer and Security Manager are selected for installation. Security Manager should
only be installed for Project Administrators who wish to manage user's access rights to
project data when using SQL Server. Click Next to proceed.
• Click Install to install the product.
• Click Finish to complete the installation.
2.3.2 Installing a Partial Release (Fix Release)

Note: A partial release must be installed over the top of the previous full release of the
product.
If you are installing a partial (Fix) release the following steps will upgrade your current
installation to the new version:
• Start the installation wizard as described above. On the welcome screen click Next to
proceed.
• Click Install to install the product.
• Click Finish to complete the installation.
2.4 License Activation

The licensing of the AVEVA Instrumentation Installation product is managed by AVEVA’s
Flexman security system.
To operate, AVEVA software must be able to access the correct Flexman license file, which
should be installed on either the Server, on your workstation, or on a networked workstation.
Flexman is a network license service handing out floating licenses to clients, which means
that licenses are not tied to a certain workstation but can be used from any workstation
where the software is installed as long as the total number of licenses in use does not
exceed the number of licenses purchased.
The Flexman guide is available on the AVEVA support site.

Installation
Note: Although the disk contains several AVEVA products, the user will only be able to use
the items that are licensed to them. The user will get an on-screen notification to
warn them when the license is due for renewal.
AVEVA Instrumentation is supported for use with Citrix for multi site working.

Installation

Project Setup
3 Project Setup
After installation you will either need to setup a new AVEVA Instrumentation project (and
database) or select an existing project Workgroup file. The Workgroup file is a data file that
holds the details of all AVEVA Instrumentation projects located on your system.
Run an AVEVA Instrumentation module. If this is the first time an AVEVA Instrumentation
application (or module) has been run on this specific workstation, the Browse For Folder
window will be displayed.
3.1 Selecting an Existing Project

To select an existing project, use the dialog to select the folder in which the project
Workgroup file is located, and click OK.

Project Setup
3.2 Creating a New Project

Before a project is created, use the dialog to make and/or select the folder in which the
project Workgroup file is to be located, and click OK.
Note: If you intend to run a project using multiple AVEVA Instrumentation users then this
Workgroup file folder should be accessible on a common network drive.
The AVEVA Instrumentation Workgroup file is a Microsoft Access database that contains a
single table which holds the names and locations of all your AVEVA Instrumentation
projects.
Note: If you need to reset a workstation’s Workgroup file (e.g. if you select the wrong
folder) you should simply delete the file ‘Inst.ini’.
If Instrumentation is installed on XP, this file will located in:
Documents and Settings\<user name of installer>\Application Data
If Instrumentation is installed on Vista or Windows 7, this file will located in:
Users\<user name of installer>\AppData\Roaming
If this does not exist, AVEVA Instrumentation will ask for the Workgroup file once
again.
Note: You must have SQL Server Administration rights to create a SQL project database.
You will also need to know the Server Name.
Refer to Hardware and Software Requirements for Installing SQL Server and SQL
Server Setup for more information.
The Create a New Project window is then displayed:

Project Setup
Project Name or No: Enter the Project Name or No.

Copy Demo Project: AVEVA Instrumentation includes a ‘Demo Project’ database which
can be copied if you are evaluating or testing AVEVA Instrumentation. Select the checkbox if
you want your new project to be a copy of the AVEVA Instrumentation Demo Project.
Share with Electrical: If project equipment and cables are to be shared with an AVEVA
Electrical project, check this checkbox.
Note: Once sharing has been selected, it cannot be deselected.
SQL Server Name: Click the [...] button to display the SQL Server login window, used to
create the new project database on a selected SQL Server. Refer to SQL Server Setup for
details.
Instrument Tag Format: AVEVA Instrumentation supports many types of instrument tag
formats. The Tag Format must be set when a project is created. Click the button next to the
Instrument Tag Number field to display the Select a Tag Number for the Project Field
window.

Project Setup
The tag formats currently supported by AVEVA Instrumentation include/exclude plant area
numbers and delimiters (‘-‘). The Tag Format list above shows examples of a typical tag
numbers based on the specific Tag Format.
Different Tag formats can be selected for Instruments and Loops.
Note: If the project’s tag format is not included in this list refer to the AVEVA
Instrumentation Engineer Help documentation to for information on how to add and
edit tag formats.
Either click on a Tag Format in the list and click Select, or double-click on the required Tag
Format.
Project Fields: Populate the other project fields such as Project Description, Plant Name,
Client Name etc.
Project Folder: This is the ‘root’ project folder. By default, once entered (or browsed to), the
other project folder names are automatically completed using this root. These can
subsequently be edited if required (see below).
Note: AVEVA Instrumentation will create all the project folders if they do not already exist
when Save is clicked.
File Locations (Folders)

Design Database: The SQL Server Database Name.
Note: If you intend to run a project using multiple AVEVA Instrumentation users then all
folders must be accessible on a common network drive for all users AND the
mapped drive letter must be the same for ALL users.
Other Folders: All other folder names are user definable but (logically) should reside under
the same root folder for ease of management. Although in theory everything could be
located in the same folder this would be difficult to manage as the number of files grows.
Therefore it is recommended that each group of files is located in a different sub-folder.
When you have completed the project details, click Save.
AVEVA Instrumentation will then create the new project database on the nominated Server.
AVEVA Instrumentation will also create all the project folders if they do not already exist.
Once created AVEVA Instrumentation will show the created project in the ‘Select a Project’
window.

Project Setup
When an AVEVA Instrumentation module is started, if only a single project has been created
(i.e. is listed in the Workgroup file), this project will be automatically selected and opened.
If more than one project has been created, then the Select a Project window is displayed,
from which the required project can be selected:
To create further projects, select the New button on the Select a Project window. The Create
a New Project window is then displayed, and should be completed as described above.
The Select a Project window can also be opened by selecting the Open Project option from
the Project tab of AVEVA Instrumentation modules.
Note: If you wish to remove a project from the list in the Select a Project window, open the
Projects.Mdb Access database located in the Workgroup folder and delete the
appropriate record. The SQL server database will not be affected on the database
server.
The project folders may be edited after the project is created from the ‘Project Edit’ option of
any AVEVA Instrumentation application (once a user has logged on to the project).
However, AVEVA Instrumentation will not move any existing files to any new folders. This
must be done manually after folder creation.
3.3 SQL Server Setup

Note: You must have SQL Server Administration rights so that AVEVA Instrumentation can
create the SQL database. You will also need to know the Server Name.
Note: Login information is not saved anywhere and is used once to connect to the Server
to create the database.
Note: Refer to Hardware and Software Requirements for Installing SQL Server.
When setting up a new project, the SQL Server login window is displayed when the button
next to the SQL Server Name field is pressed (see Creating a New Project). This is used to
create the new project database on a selected SQL Server.

Project Setup
Enter a valid Server Name.

Login using Windows Authentication or SQL Server Authentication. This login must be a
valid SQL Server Administrator account login.
Important: Do not use the AVEVA Instrumentation Admin login.
Test that the entered details are valid by clicking Test Connection.
Clicking OK will run a script to create the new AVEVA Instrumentation database.
AVEVA Instrumentation Admin Account

The AVEVA Instrumentation SQL database creation script creates a special AVEVA
Instrumentation Admin account for the database with ‘dbo’ rights on the database. This

Project Setup
account is used by AVEVA Instrumentation to enable future updates and upgrades for the
database.
Manual AVEVA Instrumentation SQL Server Database Creation

The above window runs a script named ‘EmptySQLDb.exe’ located in the AVEVA
Instrumentation program files folder ‘EmptyDbs’ (typically: ‘c:\program files\AVEVA\
Instrumentation12.1\EmptyDbs’). This file can also be run manually if a user has SQL
Admin rights. However, if this file is run manually then the SQL Administrator should ensure
the Admin account exists and has ‘dbo’ rights to the new database. You should contact
AVEVA Instrumentation to request the password for this account.
3.4 SQL Server Security

By default, AVEVA Instrumentation uses Windows Authentication to allow users access to
AVEVA Instrumentation databases on a SQL Server. To enable users to access each
AVEVA Instrumentation database the SQL Server Administrator must add each user login to
the database and allocate them to a role named ‘Users’ which gives these users
permissions to access AVEVA Instrumentation database objects.
Alternatively you can add your user’s Windows Domain name to the SQL Server database
with an ‘Users’ role.
The AVEVA Instrumentation License Manager (AVEVA.Instrumentation.Config.exe in the
AVEVA Instrumentation program folder) also contains a utility command that can be used by
a SQL Server Administrator to add named users to an existing AVEVA Instrumentation
Database using Windows Authentication.
Use the Project > Add New User to SQL Server Project command which pops up a
window enabling login as SQL Server administrator:
After adding the Server Name and Database Name (and either logging in using Windows
Authentication or logging in with admin user name and password), you will get this window:
Select the project database(s) to add the new user to.

Enter the User Domain Login Name:

Project Setup
Select desired Access/Rights (Read-Write or Read-Only)

Then click Save to add the user to the database(s)
You will need to repeat this for all new users.
3.5 AVEVA Instrumentation User Security

An AVEVA Instrumentation administrator can set security rights for users to enable/disable
access to AVEVA Instrumentation functionality including:
• Access to AVEVA Instrumentation application modules - users can be restricted from
using any module (license).
• Access to AVEVA Instrumentation objects can be restricted to read-only (e.g. a user
cannot add/edit an instrument or cable etc.) or no access (i.e. the user cannot view an
instrument or cable etc.).
AVEVA Instrumentation objects include project items such as cables, equipment and
catalogues. Functionality such as data import can also be restricted as required.
By default all new projects have the User Security Rights features disabled. If User Security
is required it must be turned on using the AVEVA Instrumentation Security Manager
application. Users must then be allocated to 'Security Groups' such as Engineers and
Designers, Read-Only Users etc. Please refer to the AVEVA Instrumentation Security
Manager documentation for more information.
Note: Once security is switched on, by default users will have no access until they are
added to a Security group.

Hardware and Software Requirements for Installing SQL Server
A Hardware and Software Requirements for

Installing SQL Server
The SQL Server Hardware and Software Requirements section describes the hardware,
operating systems and software environments required for 32-bit and 64-bit SQL Server
installations that AVEVA supports.
Please note that we ONLY support AVEVA Instrumentation running on the Enterprise,
Standard or Express versions of SQL Server 2008 R2 SP3 and SQL Server 2012.
Note: A defect in SQL Server 2008 (all editions) means that it returns too many rows when
providing a filter to the SQL statement. This can affect data returned into the grids in
AVEVA Instrumentation. This has been fixed in the SP3 release by Microsoft, hence
we support only the SP3 versions.
AVEVA believes the information in this section is correct as of its publication date. As part of
continued product development, such information is subject to change without prior notice
and is related to the current software release. AVEVA is not responsible for any inadvertent
errors. All product names mentioned are the trademarks of their respective holders.
This information has been obtained from Microsoft websites on the 31st December 2012.
Please check on Microsoft.com for the latest information.
A.1 SQL Server 2008 R2 (SP3)

• SQL Server 2008 R2
• SQL Server 2012
The following sections list the minimum hardware and software requirements to install and
run SQL Server 2008 R2.
For both 32-bit and 64-bit editions of SQL Server 2008 R2, the following apply:
• For minimum version requirements to install SQL Server 2008 R2 on Windows Server
2012 or Windows 8, see Installing SQL Server on Windows Server 2012 or Windows 8
at http://support.microsoft.com/kb/2681562.
• Microsoft recommends that you run SQL Server 2008 R2 on computers with the NTFS
file format. For upgrades to SQL Server 2008 R2, FAT32 file systems will not be
blocked.
• SQL Server Setup will block installations on read-only or compressed drives.
• For information about using SQL Server 2008 R2 tools to prepare for an upgrade to
SQL Server 2008 R2, see Using Upgrade Advisor to Prepare for Upgrades at http://
msdn.microsoft.com/en-us/library/ms144256(v=sql.105).aspx.
• Requirements to restart computers during SQL Server Setup: Installation of the .NET
Framework requires a restart of the operating system. If Windows Installer installation
© Copyright 2000 to current year. A:1 12 Series

also requires a restart, Setup will wait until the .NET Framework and Windows Installer
components have installed before restarting.
• For more information about features of SQL Server 2008 R2, see the following:
• Editions and Components of SQL Server 2008 R2 at http://msdn.microsoft.com/en-
us/library/ms144275(v=sql.105).aspx.
• Features Supported by the Editions of SQL Server 2008 R2 at http://
msdn.microsoft.com/en-us/library/cc645993(v=sql.105).aspx.
A.1.1 Hardware and Software requirements

The following requirements apply to all SQL Server 2008 R2 installations:
Component Requirement
Framework2 SQL Server Setup installs the following software components

required by the product:
• .NET Framework 3.5 SP11
• SQL Server Native Client
• SQL Server Setup support files
Software2 SQL Server Setup requires Microsoft Windows Installer 4.5 or a

later version
After installing required components, SQL Server Setup will verify
that the computer where SQL Server 2008 R2 will be installed also
meets all the other requirements for a successful installation. For
more information, see Check Parameters for the System
Configuration Checker at http://msdn.microsoft.com/en-us/library/
ms143753(v=sql.105).aspx.
Network Software Network software requirements for the 64-bit versions of SQL
Server 2008 R2 are the same as the requirements for the 32-bit
versions.
Supported operating systems have built-in network software.
Stand-alone named and default instances support the following
network protocols:
• Shared memory
• Named Pipes
• TCP/IP
• VIA
Note: Shared memory and VIA are not supported on failover
clusters.
Note: The VIA protocol is deprecated. This feature will be

removed in a future version of Microsoft SQL Server. Avoid
using this feature in new development work, and plan to
modify applications that currently use this feature.

Virtualization SQL Server 2008 R2 is supported in virtual machine environments

running on the Hyper-V role in Windows Server 2008 SP2
Standard, and Enterprise editions. The virtual machine must run
an operating system supported for the specific SQL Server 2008
R2 edition listed later in this topic.
In addition to resources required by the parent partition, each
virtual machine (child partition) must be provided with sufficient
processor resources, memory, and disk resources for its SQL
Server 2008 R2 instance. Requirements are listed later in this
topic.3
Within the Hyper-V role on Windows Server 2008 SP2, a
maximum of four virtual processors can be allocated to virtual
machines running Windows Server 2008 SP2 32-bit or 64-bit
editions. A maximum of 2 virtual processors can be allocated to
virtual computers that are running Windows Server 2003 32-bit
editions. For virtual computers that host other operating systems,
a maximum of one virtual processor can be allocated to virtual
computers. For more information about the Hyper-V role in
Windows Server 2008 SP2, see the Windows Server 2008 Web
site at http://www.microsoft.com/en-us/server-cloud/windows-
server/default.aspx.
Note: Guest failover clustering is supported in SQL Server 2008

R2. For more information about the supported versions of
SQL Server and operating systems for guest failover
clustering, and the support for virtualization, see Support
policy for Microsoft SQL Server products running in a
hardware virtual environment at http://
support.microsoft.com/?id=956893.
Internet Software Microsoft Internet Explorer 6 SP1 or a later version is required for
all installations of SQL Server 2008 R2. Internet Explorer 6 SP1 or
a later version is required for Microsoft Management Console
(MMC), SQL Server Management Studio, Business Intelligence
Development Studio, the Report Designer component of Reporting
Services, and HTML Help.
Hard Disc Disk space requirements will vary with the SQL Server 2008 R2
components you install. For more information, see Hard disk
space requirements later in this topic.
Drive A CD or DVD drive, as appropriate, is required for installation from

disc.
Display SQL Server 2008 R2 graphical tools require Super VGA or higher
resolution: at least 800x600 pixel resolution.
Other Devices Pointing device: A Microsoft mouse or compatible pointing device

is required.

Note 1
The following .NET Framework versions are required:
• SQL Server 2008 R2 on Windows Server 2003 (64-bit) IA64 - .NET Framework 2.0
SP2
• SQL Server Express - .NET Framework 2.0 SP2
• All other editions of SQL Server 2008 R2 - .NET Framework 3.5 SP1
Installation of .NET Framework requires a restart of the operating system. If Windows
Installer installation also requires a restart, Setup will wait until .NET Framework and
Windows Installer components have installed before restarting.
Note: Installing .NET Framework 2.0 SP2: .NET Framework 2.0 SP2 is not available as a
separate download. You will need to install .NET Framework 3.5 SP1 which includes
.NET Framework 2.0 SP2.
Note 2
SQL Server Setup will not install the following required components for SQL Server
Express, SQL Server Express with Tools, and SQL Server Express with Advanced Services.
You must install these components manually before you run SQL Server Setup:
• SQL Server Express - .NET Framework 2.0 SP2 and Windows installer 4.5. On
Windows Vista SP2, use .NET Framework 3.5 SP1.
• SQL Server Express with Advanced Services - .NET Framework 3.5 SP1, Windows
Installer 4.5, and Windows PowerShell 1.0.
• SQL Server Express with Tools - .NET Framework 3.5 SP1, Windows Installer 4.5, and
Windows PowerShell 1.0.
Note 3
As with all virtualization technologies, SQL Server 2008 R2 running in a Windows Server
2008 SP2 Hyper-V virtual computer will be slower than on a physical computer with the
same physical resources.
A.1.2 Processor, Memory, and Operating System Requirements

• Reporting Services
Starting in SQL Server 2008 R2, the Reporting Services component no longer supports
Itanium-based servers running Windows Server 2003 or Windows Server 2003 R2.
Reporting Services continues to support other 64-bit operating systems, including
Windows Server°2008 for Itanium-Based Systems and Windows Server°2008°R2 for
Itanium-Based Systems. To upgrade to SQL Server 2008 R2 from a SQL Server 2008
installation with Reporting Services on an Itanium-based system edition of Windows
Server 2003 or Windows Server 2003 R2, you must first upgrade the operating system.
• WOW64
WOW64 is a feature of 64-bit editions of Windows that enables 32-bit applications to
run natively in 32-bit mode. Applications function in 32-bit mode, even though the
underlying operating system is running on the 64-bit operating system. WOW64 is
supported only for stand-alone instances of SQL Server. WOW64 is not supported for
SQL Server failover cluster installations
For SQL Server 64-bit Edition installations on 64-bit supported operating systems,
Management Tools are supported in WOW64. For more information about supported
operating systems, select an edition of SQL Server 2008 R2 from the sections below.
On a supported 64-bit operating system, SQL Server 32-bit Edition installations can be
installed to the Windows on Windows (WOW64) 32-bit subsystem of a 64-bit server.

• Other operating system notes

SQL Server 2008 R2 is not supported on Windows Server 2008 SP2 Server Core or
Windows Server 2008 R2 Server Core installations.
Operating systems listed in the SQL Server Standard sections are also supported for
SQL Server Standard for Small Business
SQL Server editions that are supported on Windows Server 2008 R2 64-bit x64
Standard are also supported on Windows Small Business Server 64-bit x64.
To view system requirements, select an edition of SQL Server 2008 R2 in the sections
below.
Server Editions of SQL Server 2008 R2 supported by AVEVA for use with AVEVA
Instrumentation
• SQL Server 2008 R2 SP3 Enterprise (64-bit) x64
• SQL Server 2008 R2 SP3 Standard (64-bit) x64
• SQL Server 2008 R2 SP3 Enterprise (32-bit)
• SQL Server 2008 R2 SP3 Standard (32-bit)
Specialized Editions of SQL Server 2008 R2

• SQL Server 2008 R2 SP3 Express (64-bit) x64
• SQL Server 2008 R2 SP3 Express with Tools (64-bit) x64
• SQL Server 2008 R2 SP3 Express Advanced (64-bit) x64
SQL Server 2008 R2 Enterprise (64-bit) x64

The following table shows system requirements for SQL Server 2008 R2 Enterprise (64-bit)
x64:
Processor Processor type:

• Minimum: AMD Opteron, AMD Athlon 64, Intel Xeon with Intel
EM64T support, Intel Pentium IV with EM64T support
Processor speed:
• Minimum: 1.4 GHz
• Recommended: 2.0 GHz or faster
Operating system Windows Server 2003 SP2 64-bit x64 Datacenter

Windows Server 2003 SP2 64-bit x64 Enterprise
Windows Server 2003 SP2 64-bit x64 Standard
Windows Server 2003 R2 SP2 64-bit x64 Datacenter
Windows Server 2003 R2 SP2 64-bit x64 Enterprise
Windows Server 2003 R2 SP2 64-bit x64 Standard
Windows Server 2008 SP2 64-bit x64 Datacenter
(cont)

Operating system Windows Server 2008 SP2 64-bit x64 Datacenter without Hyper-V
Windows Server 2008 SP2 64-bit x64 Enterprise,
Windows Server 2008 SP2 64-bit x64 Enterprise without Hyper-V
Windows Server 2008 SP2 64-bit x64 Standard without Hyper-V
Windows Server 2008 SP2 64-bit x64 Web
Windows 2008 R2 64-bit x64 Datacenter
Windows 2008 R2 64-bit x64 Enterprise
Windows 2008 R2 64-bit x64 Standard
Windows 2008 R2 64-bit x64 Web
Windows Server 2008 R2 x64 for Windows Essential Server
Solutions
Windows Server 2012 64-bit Datacenter
Windows Server 2012 64-bit Standard
Windows Server 2012 64-bit Essentials
Windows Server 2012 64-bit Foundation
Memory RAM:
• Minimum:1 GB
• Recommended: 4 GB or more
• 2 TB (SQL Server Enterprise Edition supports a maximum of
2 TB of RAM or operating system maximum, whichever is
lower).
SQL Server 2008 R2 SP3 Standard (64-bit) x64

The following table shows system requirements for SQL Server 2008 R2 Standard (64-bit)
x64:

Processor speed:
Recommended: 2.0 GHz or faster

Operating System Windows XP Professional SP2 x64

Windows Vista SP2 Ultimate x64
Windows Vista SP2 Enterprise x64
Windows Vista SP2 Business x64
Windows Server 2008 SP2 x64 Datacenter, Windows Server 2008
SP2 x64 Datacenter without Hyper-V
Windows Server 2008 SP2 x64 Enterprise, Windows Server 2008
SP2 x64 Enterprise without Hyper-V
Windows Server 2008 SP2 x64 Standard, Windows Server 2008
SP2 x64 Standard without Hyper-V
Windows Server 2008 SP2 x64 Web
Windows Server 2008 SP2 for Windows Essential Server
Solutions2
Windows Server 2008 SP2 x64 Foundation Server
Windows 7 x64 Ultimate
Windows 7 x64 Enterprise
Windows 7 x64 Professional
Windows Server 2008 R2 64-bit x64 Datacenter
Windows Server 2008 R2 64-bit x64 Enterprise
Windows Server 2008 R2 64-bit x64 Standard
Windows Server 2008 R2 64-bit x64 Web
Solutions
Windows Server 2008 R2 64-bit x64 Foundation Server
(cont)

Operating System Windows Server 2012 64-bit Foundation

Windows 8 64-bit
Windows 8 Professional 64-bit
Windows RT
Memory RAM:
• Minimum:1 GB
• Maximum: 64 GB
SQL Server 2008 R2 SP3 Enterprise (32-bit)

The following table shows the system requirements for SQL Server 2008 R2 Enterprise (32-
bit):

• Pentium III-compatible processor or faster
Processor speed:
Operating System Windows Server 2003 SP2 Datacenter

Windows Server 2003 SP2 Enterprise
Windows Server 2003 SP2 Standard
Windows Server 2003 R2 SP2 Datacenter
Windows Server 2003 R2 SP2 Enterprise
Windows Server 2003 R2 SP2 Standard
Windows Server 2008 SP2 Datacenter
Windows Server 2008 SP2 Datacenter without Hyper-V
(cont)

Operating System Windows Server 2008 SP2 Enterprise

Windows Server 2008 SP2 Enterprise without Hyper-V
Windows Server 2008 SP2 Standard without Hyper-V
Windows Server 2008 SP2 Web
Windows Server 2008 SP2 x64 Datacenter
Windows Server 2008 SP2 x64 Datacenter without Hyper-V
Windows Server 2008 SP2 x64 Enterprise
Windows Server 2008 SP2 x64 Enterprise without Hyper-V
Windows Server 2008 SP2 x64 Standard
Windows Server 2008 SP2 x64 Standard without Hyper-V
Windows 2008 R2 64-bit x64 Datacenter
Windows 2008 R2 64-bit x64 Enterprise
Windows 2008 R2 64-bit x64 Standard
Windows 2008 R2 64-bit x64 Web
Solutions
Memory RAM:
• Minimum:1 GB
• 2 TB (SQL Server Enterprise Edition supports a maximum of
2 TB of RAM or operating system maximum, whichever is
lower).

SQL Server 2008 R2 SP3 Standard (32-bit)

The following table shows the system requirements for SQL Server 2008 R2 Standard (32-
bit):

• Pentium III-compatible processor or faster
Processor speed:
Operating System Windows XP Professional SP3

Windows XP SP3 Tablet
Windows XP SP2 x64 Professional
Windows XP SP3 Media Center 2002
Windows XP Professional SP3 Reduced Media
Windows Server 2003 SP2 Datacenter
Windows Server 2003 R2 SP2 Datacenter
Windows Server 2003 R2 SP2 Enterprise
Windows Server 2003 R2 SP2 Standard
Windows Vista SP2 Ultimate
Windows Vista SP2 Enterprise
Windows Vista SP2 Business
(cont)

Operating System Windows Server 2008 SP2 Datacenter

Windows Server 2008 SP2 Datacenter without Hyper-V
Windows Server 2008 SP2 Enterprise without Hyper-V
Windows Server 2008 SP2 Standard Server
Windows Server 2008 SP2 Standard Server without Hyper-V
Windows Server 2008 SP2 Web
Windows Server 2008 SP2 x64 Datacenter
Windows Server 2008 SP2 x64 Datacenter without Hyper-V
Windows Server 2008 SP2 x64 Enterprise
Windows Server 2008 SP2 x64 Enterprise without Hyper-V
Windows Server 2008 SP2 x64 Standard
Windows Server 2008 SP2 x64 Standard without Hyper-V
Windows Server 2008 SP2 for Windows Essential Server
Solutions
Solutions
Windows 7 Ultimate
Windows 7 Enterprise
Windows 7 Professional
Windows Server 2008 R2 64-bit Foundation Server
(cont)

Operating System Windows 8 32-bit

Windows 8 64-bit
Windows RT
Memory RAM:
• Minimum:1 GB
• Maximum: 64 GB
SQL Server 2008 R2 SP3 Express with Tools (64-bit) x64

The following table shows the system requirements for SQL Server 2008 R2 Express with
Tools (64-bit) x64.

Processor speed:
Operating System Windows Server 2003 x64

Windows Vista SP2 Home Premium x64
Windows Vista SP2 Home Basic x64
Windows Server 2008 SP2 64-bit x64 Datacenter without Hyper-V
(cont)

Operating System Windows Server 2008 SP2 64-bit x64 Enterprise

Windows Server 2008 SP2 64-bit x64 Foundation Server
Windows 7 x64 Home Premium
Windows 7 x64 Home Basic
Solutions
Windows 8 64-bit
Windows RT
Memory RAM:
• Minimum:512 MB
• Recommended: 1 GB
• Maximum: 1 GB for the Database Engine

SQL Server 2008 R2 SP3 Express with Advanced Services (64-bit) x64
The following table shows system requirements for SQL Server 2008 R2 Express with
Advanced Services (64-bit) x64:

Processor speed:
Operating System Windows Server 2003 x64

Windows Server 2008 SP2 64-bit x64 Foundation Server
(cont)

Operating System Windows 7 x64 Professional

Solutions
Windows 8 64-bit
Windows RT
Memory RAM:
• Minimum:512 MB
• Recommended: 1 GB
• Maximum: 1 GB for the Database Engine, 4 GB for Reporting
Services
SQL Server 2008 R2 SP3 Express x64 (64-bit)

The following table shows system requirements for SQL Server 2008 R2 Express x64 (64-
bit):

Processor speed:
Operating System Windows Server 2003 SP2 64-bit x64 Datacenter

(cont)

Operating System Windows Server 2003 R2 SP2 64-bit x64 Enterprise

Solutions
Windows 8 64-bit
Windows RT

Memory RAM:
• Minimum:256 MB
• Recommended: 1.024 GB
• Maximum: 1 GB for the Database Engine
A.1.3 Cross-Language Support

For more information about cross-language support and considerations for installing SQL
Server in localized languages, see Local Language Versions in SQL Server at http://
msdn.microsoft.com/en-us/library/20b99363-0490-4aa3-9a3d-262f827d81e8.
A.1.4 Extended System Support

SQL Server 2008 R2 64-bit versions include support for extended systems, also known as
Windows on Windows (WOW64). WOW64 is a feature of 64-bit editions of Windows that
enables 32-bit applications to execute natively in 32-bit mode. Applications function in 32-bit
mode even though the underlying operating system is running on the 64-bit operating
system.
A.1.5 Hard Disk Space Requirements (32-Bit and 64-Bit)

During installation of SQL Server 2008 R2, Windows Installer creates temporary files on the
system drive. Before you run Setup to install or upgrade SQL Server, verify that you have at
least 3.6 GB of available disk space on the system drive for these files. This requirement
applies even if you install SQL Server components to a non-default drive.
Actual hard disk space requirements depend on your system configuration and the features
that you decide to install. The following table provides disk space requirements for SQL
Server 2008 R2 components:
Feature Disk space requirement
Database Engine and data files, Replication, and Full-Text 711 MB

Search
Analysis Services and data files 345 MB
Reporting Services and Report Manager 304 MB
Integration Services 591 MB
Client Components (Other than Books Online and 1823 MB

Integration Services tools)
SQL Server Books Online 157 MB
A.1.6 Installing SQL Server on a Domain Controller

For security reasons, Microsoft recommends that you do not install SQL Server 2008 R2 on
a domain controller. SQL Server Setup will not block installation on a computer that is a
domain controller, but the following limitations apply:

• On Windows Server 2003, SQL Server services can run under a domain account or a
local system account.
• You cannot run SQL Server services on a domain controller under a local service
account or a network service account.
• After SQL Server is installed on a computer, you cannot change the computer from a
domain member to a domain controller. You must uninstall SQL Server before you
change the host computer to a domain controller.
domain controller to a domain member. You must uninstall SQL Server before you
change the host computer to a domain member.
• SQL Server failover cluster instances are not supported where cluster nodes are
domain controllers.
• SQL Server Setup cannot create security groups or provision SQL Server service
accounts on a read-only domain controller. In this scenario, Setup will fail.
A.1.7 Supported Clients (64-Bit)

SQL Server 2008 R2 SP3 64-bit client components can be installed on Windows Server
2003 (64-bit).
A.1.8 SQL Server Express 2008 Remote Connection

SQL Server Express 2008 can be used as a host database for AVEVA Instrumentation. If
SQL Server Express 2008 is installed on a different computer to that of AVEVA
Instrumentation, then the user must make sure that SQL Server Express 2008 is correctly
configured.
The user must enable remote connections via TCP (Transmission Control Protocol).
On the computer that has SQL Server Express 2008 installed the user must conduct the
following steps:
1. Click Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools >
SQL Server Configuration Manager.
2. Select SQL Server Services on the left of the SQL Server Configuration Manager
window.
3. Click Service tab and change Start Mode to Automatic. Click OK to apply changes.
4. In the right hand part of the window highlight SQL Server Bowser and right click and
select Start.
5. Expand SQL Server Network Configuration in the left of the SQL Server
6. Configuration Manager window to show Protocols for each database instance. Right-
click on TCP/IP and select Enable to enable the protocol.
7. A pop-up will be displayed prompting the user to restart the SQL Service.
8. Click SQL Server Services in the left of the SQL Server Configuration Manager
window. In the right hand part of the window select SQL Server (SQLEXPRESS) and
click Restart.
The user can now specify the remote instance of SQL Server Express 2008 when using
AVEVA Instrumentation.

A.2 SQL Server 2012

• SQL Server 2008 R2
• SQL Server 2012
The following sections list the minimum hardware and software requirements to install and
run SQL Server 2012. For more information about requirements for Analysis Services in
SharePoint integrated mode, see Hardware and Software Requirements (PowerPivot for
SharePoint and Reporting Services in SharePoint Mode).
For both 32-bit and 64-bit editions of SQL Server 2012, the following considerations apply:
• We recommend that you run SQL Server 2012 on computers with the NTFS file format.
Installing SQL Server 2012 on a computer with FAT32 file system is supported but not
recommended as it is less secure than the NTFS file system.
• SQL Server Setup will block installations on read-only, mapped, or compressed drives.
• To make sure that the Visual Studio component can be installed correctly, SQL Server
requires you to install an update. SQL Server Setup checks for the presence of this
update and then requires you to download and install the update before you can
continue with the SQL Server installation. To avoid the interruption during SQL Server
Setup, you can download and install the update before running SQL Server Setup as
described below (or install all the updates for .NET 3.5 SP1 available on Windows
Update):
• If you install SQL Server 2012 on a computer with the Windows Server 2008 SP2
operating system, you can get the required update from http://
support.microsoft.com/?kbid=956250.
• If you install SQL Server 2012 on a computer with the Windows 7 SP1 or Windows
server 2008 R2 SP1 or Windows Server 2012 or Windows 8 operating system, this
update is included.
• The installation of SQL Server 2012 fails if you launch the setup through Terminal
Services Client. Launching SQL Server Setup through Terminal Services Client is not
supported.
• SQL Server Setup installs the following software components required by the product:
• SQL Server Native Client
• SQL Server Setup support files
• Upgrade to SQL Server 2012: For information about using SQL Server 2012 tools to
prepare for an upgrade to SQL Server 2012, see Use Upgrade Advisor to Prepare for
Upgrades at http://msdn.microsoft.com/en-us/library/d85b0833-ddeb-42e3-9397-
97ea60d521b7.
• For minimum version requirements to install SQL Server on Windows Server 2012 or
Windows 8, see Installing SQL Server on Windows Server 2012 or Windows 8 at http:/
/support.microsoft.com/kb/2681562.

A.2.1 Hardware and Software requirements

The following requirements apply to all SQL Server 2012 installations:
.NET Framework2 .NET 3.5 SP1 is a requirement for SQL Server 2012 when you
select Database Engine, Reporting Services, Master Data
Services, Data Quality Services, Replication, or SQL Server
Management Studio, and it is no longer installed by SQL Server
Setup.
• If you run Setup on a computer with the Windows Server
2008 SP2 operating system, and you do not have .NET 3.5
SP1, SQL Server Setup requires you to download and
install.NET 3.5 SP1 before you can continue with the SQL
Server installation. The error message includes a link to the
download centre, or you can download .NET 3.5 SP1 from
Windows Update. To avoid interruption during SQL Server
Setup, you can download and install .NET 3.5 SP1 before you
run SQL Server Setup.
2008 R2 SP1 operating system, you must enable .NET
Framework 3.5 SP1 before you install SQL Server 2012.
2012 or Windows 8 operating system, the SQL Server Setup
automatically downloads and installs the .NET Framework 3.5
SP1. This process requires internet access.
If there is no internet access, it is required to download and
install .NET Framework 3.5 SP1 before you run Setup to
install any of the above mentioned components. For more
information about the recommendations and guidance on
how to acquire and enable .NET Framework 3.5 in Windows
Server 2012 or Windows 8, see Microsoft .NET Framework
3.5 Deployment Considerations at
http://msdn.microsoft.com/library/windows/hardware/
hh975396.
.NET 4.0 is a requirement for SQL Server 2012. SQL Server
installs .NET 4.0 during the feature installation step.
• If you are installing the SQL Server Express editions, ensure
that an Internet connection is available on the computer. SQL
Server Setup downloads and installs the .NET Framework 4
because it is not included in the SQL Server Express media.
• SQL Server Express does not install .NET 4.0 on the Server
Core mode of Windows Server 2008 R2 SP1 or Windows
Server 2012. You must install .NET 4.0 before you install SQL
Server Express on a Server Core installation of Windows
Server 2008 R2 SP1 or Windows Server 2012.

Windows SQL Server 2012 does not install or enable Windows PowerShell
PowerShell 2.0; however Windows PowerShell 2.0 is an installation
prerequisite for Database Engine components and SQL Server
Management Studio. If Setup reports that Windows PowerShell
2.0 is not present, you can install or enable it by following the
instructions on the Windows Management Framework page at
http://support.microsoft.com/kb/968929.
Network Software Supported operating systems for SQL Server 2012 have built-in
network software. Named and default instances of a stand-alone
installation support the following network protocols: Shared
memory, Named Pipes, TCP/IP and VIA.
Note:
• Shared memory and VIA are not supported on failover

clusters.
• The VIA protocol is deprecated. This feature will be removed
in a future version of Microsoft SQL Server.
For more information about Network Protocols and Network
Libraries, see Network Protocols and Network Libraries at http://
msdn.microsoft.com/en-us/library/8cd437f6-9af1-44ce-9cb0-
4d10c83da9ce.
Virtualization SQL Server 2012 is supported in virtual machine environments

running on the Hyper-V role in:
• Windows Server 2008 SP2 Standard, Enterprise and
Datacenter editions
• Windows Server 2008 R2 SP1 Standard, Enterprise, and
Datacenter editions.
• Windows Server 2012 Datacenter and Standard editions.
In addition to resources required by the parent partition, each
virtual machine (child partition) must be provided with sufficient
processor resources, memory, and disk resources for its SQL
Server 2012 instance. Requirements are listed later in this topic.1
Within the Hyper-V role on Windows Server 2008 SP2, Windows
Server 2008 R2 SP1 or Windows Server 2012, a maximum of four
virtual processors can be allocated to virtual machines running
Windows Server 2008 SP2 32-bit/64-bit or Windows Server 2008
R2 SP1 64-bit or Windows Server 2012 64-bit editions. For more
information on compute capacity limits for different editions of SQL
Server 2012 and how they differ in physical and virtualized
environments with hyper threaded processors, see Compute
Capacity Limits by Edition of SQL Server at http://
msdn.microsoft.com/en-us/library/ms143760.aspx.
(cont)

Virtualization For more information about the Hyper-V role, see the Windows
Server 2008 Web site at http://technet.microsoft.com/en-us/
windowsserver//default.aspx.
Important:
Guest failover clustering is supported in SQL Server 2012.
For more information about the supported versions of SQL
Server and operating systems for guest failover clustering,
and the support for virtualization, see Support policy for
Microsoft SQL Server products running in a hardware virtual
environment at http://support.microsoft.com/?id=956893.
Internet Software Internet Explorer 7 or a later version is required for Microsoft

Management Console (MMC), SQL Server Data Tools (SSDT), the
Report Designer component of Reporting Services, and HTML
Help.
Hard Disk SQL Server 2012 requires a minimum of 6 GB of available hard-

disk space.
Disk space requirements will vary with the SQL Server 2012
components you install. For more information, see Hard Disk
Space Requirements (32-Bit and 64 Bit) later in this topic. For
information on supported storage types for data files, see Storage
Types for Data Files.
Drive A DVD drive, as appropriate, is required for installation from disc.
Monitor SQL Server 2012 requires Super-VGA (800x600) or higher

resolution monitor.
Internet Internet functionality requires Internet access.
Note 1
Running SQL Server 2012 on a virtual machine will be slower than running natively because
of the overhead of virtualization.

A.2.2 Processor, Memory, and Operating System Requirements

The following memory and processor requirements apply to all editions of SQL Server 2012:
Memory1 Minimum:
• Express Editions: 512 MB
• All other editions: 1 GB
Recommended:
• Express Editions: 1 GB
• All other editions: At least 4 GB and should be increased as
database size increases to ensure optimal performance.
Processor Speed Minimum:

• x86 Processor: 1.0 GHz
• x64 Processor: 1.4 GHz
Recommended:
• 2.0 GHz or faster
Processor Type • x64 Processor: AMD Opteron, AMD Athlon 64, Intel Xeon
with Intel EM64T support, Intel Pentium IV with EM64T
support
• x86 Processor: Pentium III-compatible processor or faster
Note 1
The minimum memory required for installing the Data Quality Server component in Data
Quality Services (DQS) is 2 GB of RAM, which is different from the SQL Server 2012
minimum memory requirement. For information about installing DQS, see Install Data
Quality Services at http://msdn.microsoft.com/en-us/library/486e4216-a946-4c6e-828c-
61bc905f7ec1.
WOW64 Support
WOW64 (Windows 32-bit on Windows 64-bit) is a feature of 64-bit editions of Windows that
enables 32-bit applications to run natively in 32-bit mode. Applications function in 32-bit
mode, even though the underlying operating system is a 64-bit operating system.
• On a supported 64-bit operating system, SQL Server 32-bit edition can be installed to
the WOW64 32-bit subsystem of a 64-bit server. WOW64 is supported only for stand-
alone instances of SQL Server. WOW64 is not supported for SQL Server failover
cluster installations.
• For SQL Server 64-bit edition installations on supported 64-bit operating systems,
Management Tools are supported in WOW64. For more information about supported
operating systems, select an edition of SQL Server 2012 from the sections below.
Server Core Support

SQL Server 2012 is now supported on a Server Core installation of Windows Server 2008
R2 and Windows Server 2012. Installing SQL Server 2012 is supported on the Server Core
mode of the following editions of Windows Server:
• Windows Server 2012 64-bit x64 Datacenter

• Windows Server 2012 64-bit x64 Standard

• Windows Server 2008 R2 SP1 64-bit x64 Datacenter
• Windows Server 2008 R2 SP1 64-bit x64 Enterprise
• Windows Server 2008 R2 SP1 64-bit x64 Standard
• Windows Server 2008 R2 SP1 64-bit x64 Web
For more information on installing SQL Server 2012 on Server Core, see Install SQL Server
2012 on Server Core at http://msdn.microsoft.com/en-us/library/1dd294cc-5b69-4d0c-9005-
3e307b75678b.
Note: SQL Server editions that are supported on Windows Server 2008 R2 64-bit x64
Standard edition are also supported on Windows Small Business Server 64-bit x64.
A.2.3 Editions of SQL Server 2012 supported by AVEVA for use with AVEVA
Instrumentation
The following table shows the operating system requirements for the supported editions of
SQL Server 2012:
SQL Server Edition 32-bit 64-bit
SQL Server Enterprise Windows Server 2012 64- Windows Server 2012 64-
bit Datacenter bit Datacenter
Windows Server 2012 64- Windows Server 2012 64-
bit Standard bit Standard
bit Essentials bit Essentials
bit Foundation bit Foundation
Windows Server 2008 R2 Windows Server 2008 R2
SP1 64-bit Datacenter SP1 64-bit Datacenter
SP1 64-bit Enterprise SP1 64-bit Enterprise
SP1 64-bit Standard SP1 64-bit Standard
SP1 64-bit Web SP1 64-bit Web
Windows Server 2008 SP2 Windows Server 2008 SP2
64-bit Datacenter 64-bit Datacenter
64-bit Enterprise 64-bit Enterprise
64-bit Standard 64-bit Standard
64-bit Web 64-bit Web
(cont)

SQL Server Enterprise Windows Server 2008 SP2

32-bit Datacenter
Windows Server 2008 SP2
32-bit Enterprise
32-bit Standard
32-bit Web
SQL Server Standard Windows Server 2012 64- Windows Server 2012 64-
SP1 64-bit Foundation SP1 64-bit Foundation
Windows 8 32-bit Windows 8 64-bit
Windows 8 Professional Windows 8 Professional
32-bit 64-bit
Windows 8 64-bit Windows 7 SP1 64-bit
Ultimate
64-bit Windows 7 SP1 64-bit
Enterprise
Windows 7 SP1 64-bit
Ultimate Windows 7 SP1 64-bit
Professional
Enterprise Windows Server 2008 SP2
64-bit Datacenter
Professional (cont)
(cont)

SQL Server Standard Windows Server 2008 SP2 Windows Server 2008 SP2
64-bit Datacenter 64-bit Enterprise
64-bit Enterprise 64-bit Standard
64-bit Standard 64-bit Foundation
64-bit Foundation 64-bit Web
Windows Server 2008 SP2 Windows Vista SP2 64-bit
64-bit Web Ultimate
32-bit Datacenter Enterprise
32-bit Enterprise Business
32-bit Standard
32-bit Web
Windows Vista SP2 64-bit
Ultimate
Enterprise
Business
Ultimate
Enterprise
Business
SQL Server Express Windows Server 2012 64- Windows Server 2012 64-
(cont) (cont)

SQL Server Express Windows Server 2008 R2 Windows Server 2008 R2

SP1 64-bit Foundation SP1 64-bit Foundation
Windows 8 32-bit Windows 8 64-bit
Windows 8 Professional Windows 8 Professional
32-bit 64-bit
Windows 8 64-bit Windows 7 SP1 64-bit
Ultimate
64-bit Windows 7 SP1 64-bit
Enterprise
Ultimate Windows 7 SP1 64-bit
Professional
Enterprise Windows 7 SP1 64-bit
Home Premium
Professional Windows 7 SP1 64-bit
Home Basic
Home Premium Windows Server 2008 SP2
64-bit Datacenter
Home Basic Windows Server 2008 SP2
64-bit Enterprise
Ultimate Windows Server 2008 SP2
64-bit Standard
Enterprise Windows Server 2008 SP2
64-bit Foundation
Professional Windows Server 2008 SP2
64-bit Web
Home Premium Windows Vista SP2 64-bit
Ultimate
Home Basic Windows Vista SP2 64-bit
Enterprise
64-bit Datacenter Windows Vista SP2 64-bit
Business
64-bit Enterprise Windows Vista SP2 64-bit
Home Premium
(cont)
(cont)

SQL Server Express Windows Server 2008 SP2 Windows Vista SP2 64-bit
64-bit Standard Home Basic
64-bit Foundation
64-bit Web
32-bit Datacenter
32-bit Enterprise
32-bit Standard
32-bit Web
Ultimate
Enterprise
Business
Home Premium
Home Basic
Ultimate
Enterprise
Business
Home Premium
Home Basic
A.2.4 Cross-Language Support

For more information about cross-language support and considerations for installing SQL
Server in localized languages, see Local Language Versions in SQL Server at http://
msdn.microsoft.com/en-us/library/20b99363-0490-4aa3-9a3d-262f827d81e8.

A.2.5 Extended System Support

SQL Server 2012 64-bit versions include support for extended systems, also known as
Windows 32-bit on Windows 64-bit (WOW64). WOW64 is a feature of 64-bit editions of
Windows that enables 32-bit applications to execute natively in 32-bit mode. Applications
function in 32-bit mode even though the underlying operating system is 64-bit.
A.2.6 Hard Disk Space Requirements (32-Bit and 64-Bit)

During installation of SQL Server 2012, Windows Installer creates temporary files on the
system drive. Before you run Setup to install or upgrade SQL Server, verify that you have at
least 6.0 GB of available disk space on the system drive for these files. This requirement
applies even if you install SQL Server components to a non-default drive.
Actual hard disk space requirements depend on your system configuration and the features
that you decide to install. For a list of features that are supported by the editions of SQL
Server, see Features Supported by the Editions of SQL Server 2012 at http://
technet.microsoft.com/library/cc645993(SQL.110).aspx.
The following table provides disk space requirements for SQL Server 2012 components.
Feature Disk space requirement
Database Engine and data files, Replication, Full-Text 811 MB

Search, and Data Quality Services
Analysis Services and data files 345 MB
Reporting Services and Report Manager 304 MB
Integration Services 591 MB
Master Data Services 243 MB
Client Components (other than SQL Server Books Online 1823 MB

components and Integration Services tools)
SQL Server Books Online Components to view and 375 KB

manage help content1
Note 1
The disk space requirement for downloaded books online content is 200 MB.
A.2.7 Storage Types for Data Files

The supported storage types for data files are:
• Local Disk
• Shared Storage
• SMB File Share
Important
SMB storage can be hosted by a Windows File Server or a third party SMB storage device.
If Windows File Server is used, the Windows File Server version should be 2008 or later.
For more information about installing SQL Server using SMB file share as a storage option,

see Install SQL Server with SMB fileshare as a storage option http://msdn.microsoft.com/
en-us/library/8b7810b2-637e-46a3-9fe1-d055898ba639.
Caution
SQL Server failover cluster installation supports Local Disk only for installing the tempdb
files. Ensure that the path specified for the tempdb data and log files is valid on all the
cluster nodes. During failover, if the tempdb directories are not available on the failover
target node, the SQL Server resource will fail to come online.
A.2.8 Installing SQL Server on a Domain Controller

For security reasons, we recommend that you do not install SQL Server 2012 on a domain
controller. SQL Server Setup will not block installation on a computer that is a domain
controller, but the following limitations apply:
• You cannot run SQL Server services on a domain controller under a local service
account.
domain member to a domain controller. You must uninstall SQL Server before you
change the host computer to a domain controller.
domain controller to a domain member. You must uninstall SQL Server before you
change the host computer to a domain member.
• SQL Server failover cluster instances are not supported where cluster nodes are
domain controllers.
• SQL Server Setup cannot create security groups or provision SQL Server service
accounts on a read-only domain controller. In this scenario, Setup will fail.

Upgrading Access Databases to SQL Server Databases
B Upgrading Access Databases to SQL Server

Databases
As of AVEVA Instrumentation 12.1 Microsoft Access project databases are no longer

supported. Only SQL Server databases are supported. All existing Access project
databases must therefore be upgraded to SQL Server databases.
In order to facilitate this, the AccessMigration tool has been provided.
B.1 Prerequisites
The AVEVA Instrumentation design database version of the Access database being
upgraded must be that required by the tool (the required version is in the message
displayed when the tool is run - see below). If it is an older version, it must be updated to the
newest one before running the tool.
Note: You must have SQL Server Administration rights so that AVEVA Instrumentation can
create the SQL database. You will also need to know the Server Name.
Note: Login information is not saved anywhere and is used once to connect to the Server
to create the database.
Note: Refer to Hardware and Software Requirements for Installing SQL Server.
B.2 Upgrade Procedure

Run the AccessMigration tool. The following message is displayed:
Click Run Migration to continue.
© Copyright 2000 to current year. B:1 12 Series

The Select a Project dialog is then displayed:
The dialog lists all AVEVA Instrumentation Access database projects.

Click on the project to be upgraded and click Select.
The Login dialog is then displayed:
Enter the required login details for the selected project and click OK.
The tool will then check that the project is at the required AVEVA Instrumentation design
database version. If it is not, the following message is displayed:

As explained in the message, the database must be upgraded to the latest 12.0.SP5 version
by opening it in the latest version of AVEVA Instrumentation 12.0.SP5. The tool can then be
run again to upgrade the database. Click OK to close the tool.
If the database is at the required version, the SQL Server Login dialog is displayed:
This dialog is used to select the SQL Server that will be used to create the new SQL
database.
Enter a valid Server Name.
Login using Windows Authentication or SQL Server Authentication. This login must be a
valid SQL Server Administrator account login.
Important: Do not use the AVEVA Instrumentation Admin login.
Test that the entered details are valid by clicking Test Connection.
Click OK if the test is successful. The following dialog is then displayed:
Enter the name of the new database and click OK. The database creation process is then
started.

The contents of the Access database is then migrated to the new SQL database (see
Migration Procedure for details). A dialog is then displayed showing the progress of this
process:
Messages are displayed indicating the project number of the new database when the
procedure is complete:
Messages detailing any errors that occur during the procedure are also displayed.
The procedure will stop if an error is encountered. Further details of errors are displayed in
the Error Messages tab. See Migration Procedure for more information on errors and how to
resolve them.
Click Exit. A message displaying the name of the new database is displayed:

B.2.1 Migration Procedure

Details of the migration procedure are as follows:
• New schemas items existing only on SQL databases, including tables, triggers,
constraints, etc., will be applied to the new SQL database.
• Old Access records will be copied into the new SQL database.
• Records in new tables that exist only in SQL databases will be created. These include
basic records required for the operation and the demo data.
• Records in the old Access database will be kept as they are, with possibly some minor
mends for the inconsistencies inside the Access database. This will not affect the data.
For example, inside Access table DeviceCatalog, all records with column NoOfOutput
= NULL are set to Column NoOfOutput = 0 to avoid conflicts or violation. Similarly
column NoOfRevsAvailaible on table ReportViews.
• The Access database records created during the lifetime of projects will be checked for
consistency when being copied into SQL Server databases. If inconsistencies are
found, error messages will pop up and the related information for the diagnosis will be
provided.
• Information related to such errors should be brought up to the attention SQL Server
database administrators. Once remedies to these errors have been applied to the SQL
Server or/and Access database, the migration tool should be run again. This.
• If the inconsistencies are still not resolved, please contact AVEVA's technical support.
• When the tool is run again, it will continue from point that the error occurred
After successfully migrating to the SQL Server database:
• A newly generated SQL database is created.
• A newly created project name is generated and is added to the project list.
• This new SQL project uses the same settings as the Access one, with the original
design Access database being replaced by the SQL database.
• All the folders relating to the upgraded project are kept at the same locations.


Index
C Setup . . . . . . . . . . . . . . . . . . . . . . . . 3:5
SQL Server 2008 R2 . . . . . . . . . . . . A:1
Computer Requirements . . . . . . . . . . . . . 2:1 SQL Server 2012 . . . . . . . . . . . . . . A:19
SQL Server Express 2008 Remote Connec-
D tion . . . . . . . . . . . . . . . . . . A:18
Supported Clients (64-Bit) . . . . . . . A:18
Database Systems
Supported . . . . . . . . . . . . . . . . . . . . . 1:1
U
I Upgrading Access Databases to SQL Server Da-
tabases . . . . . . . . . . . . . . . . . . . B:1
Instrumentation Setup . . . . . . . . . . . . . . . 2:1 User Security . . . . . . . . . . . . . . . . . . . . . 3:8
L
Licence Activation . . . . . . . . . . . . . . . . . . 2:2
N
New Project
Tag Format . . . . . . . . . . . . . . . . . . . . 3:3
P
Project Folders . . . . . . . . . . . . . . . . . . . . 1:1
Project Setup . . . . . . . . . . . . . . . . . . . . . 3:1
S
SQL Server
Hardware and Software Requirements for
Installing . . . . . . . . . . . . . . . A:1
Installing SQL Server on a Domain Control-
ler . . . . . . . . . . . . . . . . . . . A:17
Security . . . . . . . . . . . . . . . . . . . . . . 3:7
© Copyright 2000 to current year. Index page 1 12 Series

© Copyright 2000 to current year. Index page 2 12 Series


Aveva Instrumentation Installation User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Aveva Instrumentation Installation User Guide

Uploaded by

Copyright:

Available Formats

AVEVA Instrumentation

To the fullest extent permissible at law:

Date Version Comments / Remarks

Installation User Guide

Project Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1

Hardware and Software Requirements for Installing SQL Server .A:1

© Copyright 2000 to current year. i 12 Series

Processor, Memory, and Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . A:4

Upgrading Access Databases to SQL Server Databases . . . . . . . .B:1

© Copyright 2000 to current year. ii 12 Series

AVEVA Instrumentation is a client-server application. The application modules are installed

1.1 Database Systems Supported

Express is available as a free download from the Microsoft website.

1.2 Project Folders

1.3 Guide Structure

Introduction Introduction to the AVEVA Instrumentation application.

Installation Describes the minimum requirements for each end user PC

Project Setup Describes how to setup an AVEVA Instrumentation project.

© Copyright 2000 to current year. 1:1 12 Series

Upgrading Access Describes how use the AccessMigration tool to upgrade

© Copyright 2000 to current year. 1:2 12 Series

2.1 Client Computer Requirements

Note: AutoCAD 2012 and 2013 are the supported versions.

2.2 Microsoft .NET Framework 4.0 Runtime

2.3 AVEVA Instrumentation Setup

© Copyright 2000 to current year. 2:1 12 Series

2.3.1 Installing a Full Release

2.3.2 Installing a Partial Release (Fix Release)

2.4 License Activation

© Copyright 2000 to current year. 2:2 12 Series

© Copyright 2000 to current year. 2:3 12 Series

© Copyright 2000 to current year. 2:4 12 Series

3.1 Selecting an Existing Project

© Copyright 2000 to current year. 3:1 12 Series

3.2 Creating a New Project

The Create a New Project window is then displayed:

© Copyright 2000 to current year. 3:2 12 Series

Project Name or No: Enter the Project Name or No.

Note: Once sharing has been selected, it cannot be deselected.

© Copyright 2000 to current year. 3:3 12 Series

File Locations (Folders)

© Copyright 2000 to current year. 3:4 12 Series

3.3 SQL Server Setup

© Copyright 2000 to current year. 3:5 12 Series

Enter a valid Server Name.

Important: Do not use the AVEVA Instrumentation Admin login.

AVEVA Instrumentation Admin Account

© Copyright 2000 to current year. 3:6 12 Series

Manual AVEVA Instrumentation SQL Server Database Creation

3.4 SQL Server Security

Select the project database(s) to add the new user to.

© Copyright 2000 to current year. 3:7 12 Series

Select desired Access/Rights (Read-Write or Read-Only)

3.5 AVEVA Instrumentation User Security

© Copyright 2000 to current year. 3:8 12 Series

A Hardware and Software Requirements for

A.1 SQL Server 2008 R2 (SP3)

© Copyright 2000 to current year. A:1 12 Series

A.1.1 Hardware and Software requirements

Framework2 SQL Server Setup installs the following software components

Software2 SQL Server Setup requires Microsoft Windows Installer 4.5 or a

Note: The VIA protocol is deprecated. This feature will be

© Copyright 2000 to current year. A:2 12 Series

Virtualization SQL Server 2008 R2 is supported in virtual machine environments