US | EN myRockwellAutomation Careers Investors PartnerNetwork Portal Contact Us Resources

Sales
Industries
Products Services Support&
& Solutions
Partners

ID: QA75419 | Access Levels: TechConnect, Toolkit, RA TechSupport

Steps to install SQL Server 2022 on Windows

operating systems to log FactoryTalk Alarms and
Events

Document ID QA75419

Published Date 03/13/2024

Help & Feedback

Summary
Steps to install SQL Server 2022 on Windows operating systems to log FactoryTalk Alarms
and Events

Question
Is there a Step by Step Guide on how to install another instance of SQL Server 2014 to
use for logging FactoryTalk Alarms and Events history?
What operating systems will this apply to?
What do I need to do to setup Alarm Events history?
Why is there nothing available under Database definition in RSLinx Enterprise (or
FactoryTalk Linx) or the Tag Alarm and Event Server properties?

Environment
Factorytalk View SE 14
Microsoft SQL Server 2022
Windows 10 and 11 as well as Server 2016, 2019 and 2022

Answer
The Installation Files
The FactoryTalk View Site Edition 14 and newer install media (DVD or Downloaded folder)
have several installation files for SQL server on it. They are located in
the \Redist\SQLServerEXPR_2022 folder.

The folder consists of the following files:

SQL_Server Install.bat - This runs the SQL 2014 install using
the SQLEXPR_x64.exe. The batch file passes several switches to it that customizes
 the SQL 2014 Express Setup. It will not install the Management Studio.
SQLEXPR_x64.exe - This is a slimmed down install of SQL 2014. The Management
Studio is not included.

Note: Neither of these installs will install the Studio Management software. In order
to setup a new database for alarm logging, you will need to connect to the following
site to obtain SQL Server Management Studio (SSMS) that will work with SQL 2022. It
is also not absolutely necessary to have SQL Management Studio install and this will
work without it. However, you will not be able to manipulate the SQL Server
databases and rights or check the data within the database other than the log viewer
object in FactoryTalk View SE Client without this installed.

Download SQL Server Management Studio (SSMS) from Microsoft.com

Definitions
SQL Server Management Studio - Used to manage the SQL Server, create databases,
display data, setup views, reset password etc.

You can download SQL Server Management Studio (SSMS) from Microsoft.com

SQL Instance - A database server that does not share its system and user databases with
other servers running on the same computer. To create a new instance for SQL server you
just re-run the SQL installation. When creating a connection to a SQL server specify the
server name\Instance name.
FactoryTalk View Site Edition
Version 6.10 through 9.00 of FactoryTalk View Site Edition use SQL 2008 Express to create
a SQL Instance named FTVIEWX64TAGDB. This is instance is used for the FactoryTalk View
Site Edition tag databases.

Note It is recommended that you do not use the FTVIEWX64TAGDB instance for storing
any other data. To log FactoryTalk Alarm and Events, FactoryTalk Diagnostics or data from
data log models install another instance of SQL server using the SQL installation files on
the Site Edition disk or from SQL server media.

Version 6.0 and older versions of FactoryTalk View Site Edition does not use SQL Server for
the tag database.
SQL Installation
Note: Before starting the SQL installation verify that you have Windows Administrator
privilege. Also ensure that User Account Control is set to Never Notify before starting. If
you are unsure where to check this, see article QA53328 - Disabling User Account Control
(UAC) in Windows OS for guidance.
Also the Windows Computer name and Windows User Name running the installation
cannot be the same or the install will fail.

From the FactoryTalk View Site Edition installation media navigate to

the \Redist\SQLServerEXPR_2022 and select an installation of SQL Server. (See above
for an explanation of the installation files).
1. The installation will start up. Browse the install media and locate
the \Redist\SQLServerEXPR_2014SP2 folder. Double-click
the SQLEXPR_x86_ENU.exe and the install will begin extraction.

2. Select New SQL Server stand-alone installation or add features to an existing

installation.
3. Place a check in the I accept the License Terms checkbox and click Next

4. Leave the Use Microsoft Update to check for Updates (Recommended) unchecked
and Select Next.
Note: This is optional, generally windows updates can cause unforeseen issues
 so use this at your own risk.

5. For Feature Selection, make sure to select Database Engine Services and SQL Client
Connectivity. Notice that SQL Server Management Studio is not in this list.
Installing SQL Server Replication is optional, but not required.
6. Then select the instance name, for our purposes, we will use the default SQLExpress

7. Next, we will be prompted with the services window. Generally, you will take the
defaults for this section. However, if you intend on using this SQL Server instance for
datalogging or any other option that will require the use of a DSN to connect to and
want to make this server discoverable when doing so, enable the SQL Server Browser
 to Automatic.

8. Once we get to this point, we will need to change the Authentication Mode to Mixed
Mode and give this a password. This password will be needed in upcoming steps so
make this something you have documented or can easily remember. Then click Next.
 9. At this point, you are finished with the SQL server install, click Close.

If you plan on accessing the SQL server remotely you will need to enable the TCP/IP
protocol. You may also need to enable the SQL Server Browser. Set this service to
start Automatically.

The SQL Server Configuration Manager should be installed. You can use this to view or
perform basic configuration management on the SQL Server services and protocols. From
Windows Taskbar select Start --> Microsoft SQL Server 2022 --> SQL Server Configuration
Manager.

Note: For windows 10 and the new style of start menu, see the screen shot below:
Once this is open, you will drill down through SQL Server Configuration Manager(Local) to
SQL Server Network Configuration (32-bit) and then to Protocols for SQLEXPRESS and
enable TCP/IP on the right side.

Note: for this example, I used the instance name SQLEXPRESS, you may choose to change
the SQLEXPRESS name it provides by default, just be sure to choose that names instance
when enabling TCP/IP.
Enable TCP/IP by setting this Enabled setting to Yes:

Once done, you will be prompted with a warning regarding the restart of SQL services,
click OK:

After this, locate the SQL Services in the Configuration Manager we are currently in and
restart the SQL Server service, in this case, the instance is called SQLExpress so it reads
"SQL Server (SQLExpress)"

Make sure the Firewall is configured to allow the connections. The following Microsoft
articles explain how to open up the firewall or you can just disable it.

http://support.microsoft.com/kb/914277 (SQL 2005)

http://msdn.microsoft.com/en-us/library/cc646023.aspx (SQL 2012)
http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-
connections-in-sql-server-2008.aspx (SQL 2008)
Setting up logging for Alarm and Events
1. Open the FactoryTalk Administration Console or Studio. For Administration console,
be sure to select Local or Network, depending on the type of project you are using.
Same for Studio, be sure to open the project you want to log the alarms with.
Then navigate to the bottom of the Explorer tree and expand System --> Connections
--> Databases:

2. Right click on Databases and select Add Database Connection

3. In the Database Type drop down, select Factorytalk Alarm & Events History Database:

4. In the Definition name box enter a name for this connection.

5. In the Computer Name enter the Windows PC name of the SQL server followed by a
backslash \ then the SQL Instance name. e.g. SQLServer1\SQLEXPRESS.
6. Enter the Database user name. At this point, you will make up a username and
password of your choosing.
7. Enter a database name. It will be created if it does not exist. If the user name and
password are correct from the above steps then before you enter the database name
you can select the box to the right with the three periods and you should be able to
browse the existing databases.
 Note: Once you click OK, the database definition will attempt to create the
database in the SQLExpress instance as well as the username and password you
created. It will prompt you for a login, at which time you will use the username sa
and password you supplied during the install of SQL in step 8 above in this
document.

NOTE: After doing this if you hit OK and nothing happens follow the procedure in this
technote: QA20981 - Unable to create Database for Historical Alarm and Events under
the Connections folder
Configure RSLinx Enterprise (or FactoryTalk Linx) or the Tag Alarm
and Event Server to log to SQL
Note: RSLinx Enterprise does not need to be configured if you are not using any
device-based alarming (ALMA or AMLD instructions defined directly in a controller).

1. Right-click on RSLinx Enterprise (or FactoryTalk Linx) and select Properties. If you
are assigning to an alarm and event server, then right-click that server and go to
properties.
2. Then click on the Alarms and Events tab for Factorytalk Linx. If you are assigning this
to an Alarms & Events server, then choose the Priorities and History tab. Make
sure Enable Alarm and Event support is checked and also check the box to Enable
history under the Alarm and Event History section.

3. Select the database definition in the drop down box.

4. For the Tag Alarm and Event Server, right click on it and select Priorities and History.
Then check the appropriate check boxes. To get to the Priorities and History tab on
newer versions of FactoryTalk View SE, right click on your FactoryTalk Alarm and
Event server, select Properties ---> Priorities and History.

Data Log Setup (Optional)

You can optionally set up another database on the instance you created above to use
with data log models in FactoryTalk View SE, which is separate from logging
FactoryTalk Alarm and Event history. Before you follow the steps below, it’s important
that you create a new database within you instance of Microsoft SQL Server. You
should do this by downloading SQL Server Management Studio, connecting to your
instance of the database server, and then creating a new database specifically for
SQL data logging. For more information on this, follow the steps outlined in QA-
39884-FactoryTalk View SE - How to Setup SQL Datalogging

Problems with Database user name and password

5. Download SQL Server Management Studio (SSMS) from Microsoft.com
 6. Start the SQL Management Studio and connect to your SQL server name and
instance.
7. Expand Security --> Logins.
8. Bring up the properties for the My_User account (or the account you want to use).
9. You can change the password here. Also check the Status of the account to make
sure it is Enabled and not locked out and Permission to connect is set to Grant.

Recently Viewed

FactoryTalk View SE: FactoryTalk View SE - FactoryTalk View SE

Choosing what get logged Configuring Custom Data Extended by FactoryTalk
to Alarms and Events Storage Paths for Optix: OPC UA Application
history in SQL DataLogPro InfluxDB Notes

DISCLAIMER
This knowledge base web site is intended to provide general technical information on a particular subject or subjects and is
not an exhaustive treatment of such subjects. Accordingly, the information in this web site is not intended to constitute
application, design, software or other professional engineering advice or services. Before making any decision or taking any
action, which might affect your equipment, you should consult a qualified professional advisor.

ROCKWELL AUTOMATION DOES NOT WARRANT THE COMPLETENESS, TIMELINESS OR ACCURACY OF ANY OF
THE DATA CONTAINED IN THIS WEB SITE AND MAY MAKE CHANGES THERETO AT ANY TIME IN ITS SOLE
DISCRETION WITHOUT NOTICE. FURTHER, ALL INFORMATION CONVEYED HEREBY IS PROVIDED TO USERS "AS
IS." IN NO EVENT SHALL ROCKWELL BE LIABLE FOR ANY DAMAGES OF ANY KIND INCLUDING DIRECT, INDIRECT,
INCIDENTAL, CONSEQUENTIAL, LOSS PROFIT OR DAMAGE, EVEN IF ROCKWELL AUTOMATION HAVE BEEN
ADVISED ON THE POSSIBILITY OF SUCH DAMAGES.

ROCKWELL AUTOMATION DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED IN RESPECT OF

THE INFORMATION (INCLUDING SOFTWARE) PROVIDED HEREBY, INCLUDING THE IMPLIED WARRANTIES OF
FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, AND NON-INFRINGEMENT. Note that certain
jurisdictions do not countenance the exclusion of implied warranties; thus, this disclaimer may not apply to you.

COMPANY NEWS & TRAINING CONTACT US INSIGHTS

EVENTS
About Us Webinars TechConnect Results Achieved
Newsroom Support
Accessibility Workforce Case Studies
Press Releases Development Training Customer Care
Careers Blogs
 Diversity, Ethics World Economic PARTNERNETWORK General Inquiries The Journal
and Integrity Forum
Find a Partner How to Buy Podcasts
Engage Online Automation Fair
Community What is the Report Ethical
Upcoming Events PartnerNetwork? Concerns
Investor
Relations 2024 Customer
TRENDING OUR BRANDS Experience
Modern Slavery TOPICS Survey
Statement Allen-Bradley
Cybersecurity
FactoryTalk
Sustainability
Digital
Trust Center Transformation LifecycleIQ Services

Smart
Manufacturing

The Connected
Enterprise®

Legal NoticesPrivacy & Cookies PolicyEmail PreferencesCookies Settings © 2024 Rockwell

Accessibility SettingsROK $291.33 ▲ Automation