Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
839 views

SQL

This document provides instructions for installing SQL Server 2008 R2 Express on a computer with FactoryTalk View Site Edition version 6.1 or later. It describes the SQL installation files included with FactoryTalk View, how to run the SQL installation, configure the database instance, set permissions, and enable remote access. It also provides directions for configuring FactoryTalk applications like Alarm and Events and data logging to store historical data in the new SQL database instance.

Uploaded by

Darshan
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
839 views

SQL

This document provides instructions for installing SQL Server 2008 R2 Express on a computer with FactoryTalk View Site Edition version 6.1 or later. It describes the SQL installation files included with FactoryTalk View, how to run the SQL installation, configure the database instance, set permissions, and enable remote access. It also provides directions for configuring FactoryTalk applications like Alarm and Events and data logging to store historical data in the new SQL database instance.

Uploaded by

Darshan
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 25

SQL Server 2008 with Factorytalk View SE

The Installation Files:


The Factorytalk view Site Edition DVD has several installation files for SQL server on
it. They are located in the Redist\SQLServer2008 folder. The folder consists of the
following files:
SQL_Server Install.bat This runs the SQL 2008 install using the
SQLEXPRWT_x86_ENU.exe. The batch file passes several switches to it that
customizes the SQL 2008 Express Setup. It will not install the Management Studio.
SQLEXPRWT_x86_ENU.exe This is the SQL 2008 Express setup. Running this will
install SQL 2008 Express and will also allow you to select the Management tools
which is the SQL 2008 Management Studio.
*Note: On the Factorytalk View ver. 7 install disk both SQL install files are release
2008 R2 Express.
SQLEXPR_x86_ENU.exe This is a slimmed down install of SQL 2008 R2. The
Management Studio is not included.

Definitions:
SQL Server Management Studio Used to manage the SQL Server, create
databases, display data, setup views
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 Editon:


Version 6.1 of Factorytalk View Site Edition use SQL 2008 Express to create a SQL
Instance named FTVIEWX64TAGDB. This is instance is used for the 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 of Site Edition does not use SQL Server for the tag database.

SQL Installation:

Note:

Before starting the SQL installation verify you have Windows


Administrator privilege. Some issues have come up where policies
have been set to remove certain privileges of the local Administrator
account.
See
http://blogs.technet.com/b/fort_sql/archive/2009/12/17/installingreporting-services-2008.aspx
The Windows Computer name and Windows User Name running the
installation cannot be the same or the install will fail.

From the Site Edition installation media navigate to the Redist\SQLServer2008 and
select an installation of SQL Server. (See above for an explanation of the installation
files).
The installation will start up:

Select Installation from the left column.

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


installation.

Select OK.

Select Next.

Accept the license and select Next.

Select Install

Select Next.

Depending on the installation run and what you currently have installed you may
get the screen above or the following screen. In the screen above there is no option
to install the Management tools. This is usually the case when running the
installation from the batch file or from the SQLEXPR_x86_ENU.exe. Check Database
Engine Services and Next. If you have the display below check Database Engine
Services and the Management Tools Basic then select Next.

The display above will be seen if the SQL installation was run from
SQLEXPRWT_x86_ENU.exe. In this case check Database Engine Services and the
Management Tools Basic then select Next.

Enter a name for this Instance of SQL server. This instance name will be used
along with the server name when creating a connection to the SQL server.
Remember to connect to the SQL server for logging data use the Windows
Computer name\Instance name. If there are any other Instances installed they
should be listed in the Installed instances box.

Review Disk Space Requirements.

Select an account to use.

Select Mixed Mode for the Windows Authentication Mode and enter a password. This
password is for the built-in sa account for this Instance of SQL. If you want to add
the current user performing the installation then select Add Current User. This is
recommended in case the sa account password is forgotten. The current user can
always be removed later.

Select Next.

Select Next.

Select Install.

Select Next.

If everything went well you should end up with this screen.


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 All Programs Microsoft SQL Server
2008 R2 Configuration Tools SQL Server Configuration Manager.

You see the status of the Services and the Instance name in parenthesis.

Remember to connect to the SQL server for logging data use the Windows
Computer name\Instance name.
Connecting to the SQL Server Remotely
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.

Check that the SQL server will allow remote connections. From the SQL
Management right click on your SQL server and select Properties Connections.
Make sure Allow remote connections to this server is checked.

Make sure the Firewall is configured. 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-remoteconnections-in-sql-server-2008.aspx (SQL 2008)

Setting up logging for Alarm and Events


1. Open the Factorytalk Administration Console or with you project opened in
Studio navigate to the bottom of the Explorer tree and expand System
Connections.
2. Right click on Database and select New database.
3. In the Definition name box enter a name for this connection.
4. 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.

5. Enter the Database user name. If the defaults were used during the
installation use the sa account.
6. Enter the password for the user that was entered.
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.

Configure RSLinx Enterprise or the Tag Alarm and Event Server to log to
SQL
1. Right click on RSLinx Enterprise and select Properties Alarm and Events
2. 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.
Problems with Database user name and password
1. Start the SQL Management Studio and connect to your SQL server name and
instance.
2. Expand Security Logins.
3. Bring up the properties for the sa account (or the account you want to use).
4. You can change the password here. Also chck the Status of the account to
make sure it is Enabled and not locked out and Permission to connect is set to
Grant.

Data Log setup


To configure data logging for tag data first configure a DSN.
For 32-bit operating systems use the ODBC Administrator available from Control
Panel Administrative tools to configure a DSN to connect to your SQL database.
For 64-bit operating systems we still need to use the 32-bit ODBC Data source
Administrator. Run the Windows\SysWOW64\odbcad32.exe to create the DSN.
When configuring the DSN point it to the Database you want to log to. Do not log
to the Master Database.
Configure Data logging in Site Edition to use the DSN.

Misc. SQL Install Problems


Problem:
Running SQL setup from exe and DOS Window pops up after file extraction then goes
away.
Running Setup from SQL Extracted files under a DOS window and it comes back with:
Trying to install SQL Server 2008 Standard R2 on a Windows Server 2008 R2 64bits
machine (all updates applied)...
I run the setup.exe on the command line and I get the following error :
The language ENU is not supported by this setup package.
An error occurred during the SQL Server 2008 R2 Setup operation.

Error result: -2067529698


Result facility code: 1220
Result error code: 30

Solution:
Delete/rename the following folder and it should work.
C:/Program Files (x86)/Microsoft SQL Server/100/Setup Bootstrap/SQLServer2008R2/

Problem:
Do not log to the SQL server Master Database.
The following is from Microsoft :
The master database records all the system-level information for a SQL Server system.
This includes instance-wide metadata such as logon accounts, endpoints, linked servers, and
system configuration settings. In SQL Server, system objects are no longer stored in
the master database; instead, they are stored in the Resource database. Also, master is
the database that records the existence of all other databases and the location of those
database files and records the initialization information for SQL Server. Therefore, SQL
Server cannot start if the master database is unavailable.

You might also like