Download MSDE or SQL Server 2000 Database

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

DBase wikipedia , lookup

Serializability wikipedia , lookup

Tandem Computers wikipedia , lookup

Entity–attribute–value model wikipedia , lookup

IMDb wikipedia , lookup

Extensible Storage Engine wikipedia , lookup

Functional Database Model wikipedia , lookup

Oracle Database wikipedia , lookup

Microsoft Access wikipedia , lookup

Team Foundation Server wikipedia , lookup

Concurrency control wikipedia , lookup

Btrieve wikipedia , lookup

Ingres (database) wikipedia , lookup

Database wikipedia , lookup

Microsoft Jet Database Engine wikipedia , lookup

SQL wikipedia , lookup

Database model wikipedia , lookup

Relational model wikipedia , lookup

Open Database Connectivity wikipedia , lookup

ContactPoint wikipedia , lookup

Microsoft SQL Server wikipedia , lookup

PL/SQL wikipedia , lookup

Clusterpoint wikipedia , lookup

Transcript
3951 Westerre Parkway, Suite 350
Richmond, Virginia 23233 USA
© 2002 Tridium, Inc.
MSDE or SQL Server 2000 Database
INSTALLATION AND CONFIGURATION INSTRUCTIONS
These instructions provide information on configuring, installing, and using an MSDE or Microsoft SQL Server
2000 database as the database for Web Supervisor station archives. The Cloudscape database that typically
serves this function is a single-user database and that license is used by the station itself. Using a SQL database
instead of the Cloudscape database provides access from third-party reporting and analysis applications such as
Microsoft Access and Crystal Reports.
These notes cover the following main topics:
Supported Software
• Architectures
• About Data in the SQL Web Supervisor Database
• Installation and Configuration
•
Supported Software
This topic provides a discussion of the various versions of Tridium and Microsoft software required to archive
data from a Web Supervisor station to either a Microsoft Data Engine (MSDE) database or a SQL Server 2000
database.
Niagara
The SQL database functionality is supported only on a Web Supervisor PC, not on the JACE hardware. To
implement this functionality, you need Niagara Release 2.3, Build 2.301.330 or later.
Licensing
By default, each Web Supervisor licensed for database functionality is licensed to use the Cloudscape database.
A license file with default functionality includes the database feature on the features line, as shown in
Example 1.
Example 1
Default database functionality in the license file.
features=database;coreUi;lonworks;bacnet;webUi;coreRuntime
In order for a Web Supervisor to write data to a SQL database, it must be licensed not only for database
functionality, but also for the specific database type (see the “Supported Database Implementations” section on
page 2).
A Web Supervisor licensed for the MSDE type of SQL database is shown in Example 2.
MSDE or SQL Server 2000 Database Installation and Configuration Instructions
Niagara Release 2.3
Revised: January 7, 2003
1
Supported Software
Supported Database Implementations
Example 2
Web Supervisor license file for an MSDE installation.
features=database;coreUi;lonworks;bacnet;webUi;coreRuntime
databaseType=MSDE
A Web Supervisor licensed for the SQL Server 2000 database is shown in Example 3.
Example 3
Web Supervisor license file for a SQL Server installation.
features=database;coreUi;lonworks;bacnet;webUi;coreRuntime
databaseType=MS_SQL_SERVER
To obtain a Niagara license with the appropriate functionality, contact [email protected]. Be sure to specify
which database configuration (either MSDE or MS_SQL_Server) that you are interested in.
Supported Database Implementations
Two implementations of the Microsoft SQL database are supported:
MSDE
• SQL Server 2000
•
MSDE
MSDE 2000 is a SQL database implementation that provides local data storage that is compatible with
Microsoft SQL Server 2000. It is based on the same data engine as SQL Server, but is designed for use on a
user’s laptop, desktop PC, or a small workgroup server.
Unlike SQL Server, MSDE:
Has a 2 GB storage limit.
• Has a query connection limit of five. This means that, while many users can be connected to the database,
only five queries can be executed simultaneously without severely degrading the performance of the
database.
• Does not have any user interface tools. Rather, you interact with the data in the database through the
Niagara application, or other third-party tools such as Microsoft Access or Crystal Reports.
• Does not support some advanced SQL Server functionality.
•
System Requirements
These are the following minimum hardware and operating system requirements (per Microsoft’s web site) to run
the MSDE database on a Web Supervisor PC:
Computer with a Pentium III, 500-MHz or higher processor.
• Minimum of 512 MB of RAM, 1 GB recommended.
• Minimum of 1 GB of available hard disk space, 3 GB for applications that need more archiving capacity.
•
The following operating system configurations can run the MSDE:
Windows XP Professional
• Windows NT Workstation 4.0 with Service Pack 5 or later
•
2
MSDE or SQL Server 2000 Database Installation and Configuration Instructions
Revised: January 7, 2003
Niagara Release 2.3
Supported Software
Supported Database Implementations
•
•
•
•
•
Windows NT Server 4.0 with Service Pack 5 or later
Windows NT version 4.0 Server Enterprise Edition with Service Pack 5 or later
Windows 2000 Professional
Windows 2000 Server
Windows 2000 Advanced Server
Microsoft asserts that the SQL Server 2000 Driver for JDBC (required for MSDE) has been tested and certified
on the following operating systems:
Microsoft Windows XP
• Microsoft Windows 2000 with Service Pack 2 or higher
•
The following versions of the JDK are supported for use with the SQL Server 2000 Driver for JDBC:
JDK 1.1.8
• JDK 1.2
• JDK 1.3
•
The Microsoft SQL Server 2000 Driver for JDBC is available for download at http:www.microsoft.com to all
licensed SQL Server 2000 customers at no charge. Please review the end-user license agreement (included with
the download) for further details on users’ rights.
Note
You can run an MSDE database on a machine other than the Web Supervisor and have the Web
Supervisor write data to the database. For information on the system requirements for a remote MSDE
installation, see http://msdn.microsoft.com/library. This configuration is not supported by Tridium. You
can configure your database this way, but Tridium will not provide support if you experience problems.
For more information about the capabilities of MSDE, visit the Microsoft web site at http://www.microsoft.com.
Licensing
A fully-licensed copy of MSDE is included on the Niagara installation CD. Tridium recommends that you use
this installation of MSDE to make installing and configuring MSDE easier. You may use an existing version of
MSDE if you already have it installed on your Web Supervisor PC, though.
A license to use MSDE comes with many Microsoft products including Microsoft Access 2000. Please consult
the Microsoft web site for a complete list of products that provide you with a valid license to use MSDE with
your Web Supervisor software. If you use an installation of MSDE of MSDE other than Tridium’s there are
manual configuration changes that you need to make to the installation parameters including changes to your
registry entries that are not covered in this document. Please consult Tridium System Engineering for additional
information.
SQL Server 2000
Many IT departments have standardized on Microsoft SQL Server for enterprise-wide database functions. This
database is typically installed and used on an enterprise-level server. The Tridium SQL database implementation
supports writing archive data to the enterprise-level versions of SQL Server 2000. You can also output archive
data to a SQL Server 7.0 database. However, if you use the Tridium VES product with a SQL Server 7.0
database, you must upgrade you VES implementation to build 330.
MSDE or SQL Server 2000 Database Installation and Configuration Instructions
Niagara Release 2.3
Revised: January 7, 2003
3
Architectures
Cloudscape
Note
All Tridium testing was done using the SQL Server 2000 product.
For more information about the capabilities of the Microsoft SQL Server, visit the Microsoft web site at
http://www.microsoft.com.
Note
This document assumes that the customer’s IT department manages the SQL Server implementation
and has a database administrator (DBA) familiar with setting up and managing SQL Server databases.
This document does not provide instructions on how to install, set up, tune, backup, or manage these
versions of SQL Server.
Licensing
The DBA must verify that the SQL Server is adequately licensed for the connection from each Web Supervisor,
and also for the users who need to access the archive data in the SQL Server.
Architectures
This section discusses the typical system architectures found when using the new database functionality.
Cloudscape
In order to fully understand the impact of using a SQL server implementation, a review of the typical Cloudscape
architectures is provided in Figure 1.
4
MSDE or SQL Server 2000 Database Installation and Configuration Instructions
Revised: January 7, 2003
Niagara Release 2.3
Architectures
Cloudscape
Figure 1
Typical Cloudscape database implementations.
Web Supervisor
Small
Installation
Cloudscape
database
Web Supervisor with:
y
database service
y
logging set to
archive_local
Archives pushed to
Web Supervisor
HEA
RTB
EAT
HEA
RTB
EAT
Rx
RS2
D TxD
POR 32
1
T
Rx
D
RS2 Tx
RS4 32/ D
POR 85
T
1
2
Two or more JACEs with:
y
log objects set up to archive
y
logging set to
archive_remote
Rx
RS2
D Tx
POR 32
T
D Rx
D
RS2Tx
RS4 32/D
POR 85
T2
DAT
ETH
10 A
Rx
0
NET ER
D Tx
LON D
DAT
ETH
10 A
Rx
0
NET ER
D Tx
D
LO
N
Master Web Supervisor
Multi-site
Installation
Cloudscape
database
Master Web Supervisor with:
y
database service
y
logging set to archive_local
y
licensing set for "multisite"
function
Archives pulled from
Web Supervisors
Web Supervisor
Cloudscape
database
Web Supervisor
Web Supervisor with:
y
database service
y
logging set to
archive_local
Cloudscape
database
Archives pushed to
Web Supervisor
Archives pushed to
Web Supervisor
HEA
RTB
EAT
HEA
RTB
EAT
Rx
D Tx
RS2
POR 32 D Rx
D
1 T
RS2 Tx
RS4 32/ D
POR 85
T2
Rx
RS2
D Tx
POR 32 D Rx
1 T
D
RS2 Tx
RS4 32/
POR 85
T2
DAT
ETH
100 A
Rx
NET ER D Tx
D
LO
N
D
DAT
ETH
10 A
Rx
0
NET ER
D Tx D
LO
N
Two or more JACEs with:
y
log objects set up
to archive
y
logging set to
archive_remote
Web Supervisor with:
y
database service
y
logging set to
archive_local
HEA
RTB
EAT
HEA
RTB
EAT
Rx
RS2
D Tx
POR 32 D Rx
D
1 T
RS2Tx
RS4 32/ D
POR 85
T2
Rx
D Tx
RS2
POR 32 D
T
1
DAT
ETH10 A
Rx
0
NETER
D Tx D
LON
Rx
D
RS2 Tx
RS4 32/ D
POR 85
T2
DAT
ETH10
A Rx
NETER0
D Tx
D
LO
N
MSDE or SQL Server 2000 Database Installation and Configuration Instructions
Niagara Release 2.3
Revised: January 7, 2003
Two or more JACEs with:
y
log objects set up
to archive
y
logging set to
archive_remote
5
Architectures
MSDE
Small Installation
In a typical small installation, two or more JACEs are set up to archive logs remotely to a Web Supervisor
running the database service. The data resides in a Cloudscape database on the Web Supervisor. Archived log
data for all JACEs can be accessed via the Web Supervisor’s database service using a browser or the JDE.
Several Web Supervisors can be configured in this manner, but there is no communal source of all data. Rather,
each Web Supervisor must be accessed to view the data from its respective JACEs.
Multi-site Installation
With a multi-site installation, several Web Supervisors are configured as in the previous example. However, a
Master Web Supervisor is set up to poll the other Web Supervisors for their logs. Data for all polled Web
Supervisors resides in the Cloudscape database of the Master Web Supervisor. Data for each JACE can be
accessed from the communal data on the Master Web Supervisor or from the Web Supervisor that the JACE
archives to. The multi-site configuration provides two advantages over the small installation model:
There is one central store of all archived data.
• Web Supervisors can reside in different projects.
•
A Cloudscape database is a single-user database and that license is used by the station itself; therefore, you must
disconnect the station to provide access to the Cloudscape database from third-party reporting and analysis
applications such as Microsoft Access and Crystal Reports.
Using either Cloudscape implementation works best when reporting and analysis needs can be satisfied with the
tools that already exist within the Framework. A Cloudscape database can be easily migrated to a SQL database
using the Niagara dbadmin command line tool. For more information, see “Upgrading an MSDE Installation to
an SQL Server 2000 Installation,” page 14.
MSDE
Figure 2 provides two typical MSDE implementations.
6
MSDE or SQL Server 2000 Database Installation and Configuration Instructions
Revised: January 7, 2003
Niagara Release 2.3
Architectures
MSDE
Figure 2
Typical MSDE database implementations.
.
Workgroup Server
Web Supervisor
MSDE
database
Web Supervisor with:
y
database service
y
logging set to
archive_local
The workgroup server
contains only the MSDE
installation, no other Niagara
components.
This configuration
is technically possible
but is not supported
by Tridium at this
time.
MSDE
database
Database service writes to and
reads from the MSDE database
Web Supervisor
Archives pushed to
Web Supervisor
HEAR
EAT TB
H EAR
Rx
D Tx
RS2
P ORT 32 D Rx
1
D
RS23Tx
RS48 2/ D
POR
5
T2
EA TB
T
Rx
D Tx
RS2
POR 32 D Rx
1 T
D
RS23Tx
RS48 2/ D
POR
5
T2
DAT
ETH
10 A
Rx
0
NET ER
D Tx
D
LO
N
DAT
ETH
10 A
Rx
0
NET ER
D Tx
LON D
Two or more JACEs with:
y
log objects set up
to archive
y
logging set to
archive_remote
Local
Database
Web Supervisor with:
y
database service
y
logging set to
archive_local
Remote
Database
Archives pushed to
Web Supervisor
HEA
RTB
E AT
HE
Rx
EA
RS2
D
T
POR 32 x D
Rx
1 T
D
RS2 Tx
RS4 32/ D
POR 85
T
2
DAT
ETHE
10 A
Rx
NET R0
D Tx
LO
N
D
AR
TB
T
Rx
RDS232
Tx
D
POR
Rx
1 T
D
RS2 Tx
R S48532/ D
P ORT
2
DAT
ETHE
10 A
Rx
NET 0R
D Tx
D
LO
N
Two or more JACEs with:
y
log objects set up
to archive
y
logging set to
archive_remote
Local MSDE Database
The architecture for the local database scenario is similar to the small installation Cloudscape model. The only
difference is that the Web Supervisor uses an MSDE database instead of a Cloudscape database. The database
is installed locally on the Web Supervisor PC. Functionality of the Niagara software is the same: a browser or
the JDE still talks to the database service to access the JACE archive data.
Remote MSDE Database
The architecture for the remote database scenario is similar to the local database model; however, the data,
instead of residing in MSDE on the Web Supervisor PC, now resides in an MSDE database on a remote PC or
server.
Caution
Remember that this configuration is technically possible, but is not supported by Tridium. You must
support this configuration yourself if you choose this implementation option.
MSDE or SQL Server 2000 Database Installation and Configuration Instructions
Niagara Release 2.3
Revised: January 7, 2003
7
Architectures
SQL Server 2000
Note
While it is possible to have multiple Web Supervisors using a common a MSDE database, it is not
practical to do so because of the 2 GB per database size limit. For more information on the limits of the
MSDE database option, see “MSDE,” page 6.
When to Use the MSDE Option
You should use the MSDE database option when you want access to the archive data with third-party tools, the
archive data store will be less than 2 GB, and there will be few users running queries. If you do not need access
with third-party tools, then one of the Cloudscape scenarios is a better choice, because a Cloudscape data store
can grow larger than 2 GB. If you do need third-party access, with more users, or a larger database size, then
SQL Server 2000 is a better option. However, MSDE does provide seamless migration to SQL Server, if after
implementation you find that storage size or user connection limits are exceeded.
SQL Server 2000
Figure 3 shows the only SQL Server 2000 implementation option.
Figure 3
Typical SQL Server 2000 database implementation.
.
Enterprise-level SQL Server
SQL
database
Web Supervisor
SQL
database
Database service
writes to and reads
from individual SQL
databases
Web Supervisor
Two or more
Web Supervisors with:
y
database service
y
logging set to
archive_local
Archives pushed to
Web Supervisor
HEA
RT
EAT B
HEA
RT
EAT B
Rx
RS2
D
TxD
POR 32
Rx
D
1 T
RS2 TxD
RS4 32/
POR 85
T2
DAT
ETH
10 A
Rx
NET ER0
D Tx
D
LO
N
8
Rx
RS2
D
Tx
POR 32 D
Rx
1 T
D
RS2 Tx
RS4 32/ D
POR 85
T2
DAT
ETH
100 A
Rx
NET ER
D Tx
D
LO
N
Archives pushed to
Web Supervisor
Two or more JACEs with:
y
log objects set up
to archive
y
logging set to
archive_remote
HEA
RTB
EAT
HEA
RT
EAT B
Rx
D
RS2
Tx
POR 32 D
Rx
1 T
D
RS2 Tx
RS4 32/ D
POR 85
T2
Rx
D
RS2
Tx
POR 32 D
Rx
D
1 T
RS2 Tx
RS4 32/ D
POR 85
T2
DAT
DAT
ETH
10 A
Rx
0
NET ER
D TxD
LO
N
ETH
10 A
0
NET ER
LO
Rx
D Tx
D
N
Two or more JACEs with:
y
log objects set up
y
to archive
y
logging set to
archive_remote
MSDE or SQL Server 2000 Database Installation and Configuration Instructions
Revised: January 7, 2003
Niagara Release 2.3
Architectures
SQL Server 2000
Individual SQL Databases
The architecture for the individual SQL databases scenario is similar to the remote database model with MSDE.
The data, instead of residing on the Web Supervisor PC, resides in individual SQL databases on a remote,
enterprise-level SQL server.
With the individual SQL databases scenario, each Web Supervisor licensed for the SQL Server database option
writes to and reads from its own database. This scenario provides a way to segregate data. Clients accessing the
Web Supervisor using Niagara tools (a web browser or the JDE) only see the data accumulated by that Web
Supervisor. However, third-party tools run directly against the SQL Server can be configured to aggregate data
for reporting and analysis.
When to Use the SQL Server 2000 Option
You should use the Microsoft SQL Server 2000 option when you need access to Web Supervisor data from a
third-party tool and your data storage requirements exceed 2 GB.
MSDE or SQL Server 2000 Database Installation and Configuration Instructions
Niagara Release 2.3
Revised: January 7, 2003
9
About Data in the SQL Web Supervisor Database
SQL Server 2000
About Data in the SQL Web Supervisor
Database
•
A sample table diagram for an SQL Web Supervisor database (called newarch) is shown in Figure 4. You
will notice that because Web Supervisor data is essentially time-sequence in nature, there are few
relational dependencies among tables in the SQL database.
Figure 4
Sample SQL table diagram.
Regardless of whether you are using the native Cloudscape database or an SQL-based database in the Web
Supervisor, you still need to communicate with the DatabaseService to access station data. So, you still
use either the JDE or a web browser to access the particular Web Supervisor archiving the data.
• If you are using an SQL-based database in a Web Supervisor, you can develop custom interfaces to the
data via the SQL server or other third-party tools.
•
10
MSDE or SQL Server 2000 Database Installation and Configuration Instructions
Revised: January 7, 2003
Niagara Release 2.3
Installation and Configuration
Configuring the Web Supervisor to Use an MSDE or SQL Server 2000 Database
Installation and Configuration
The following sections discuss how to configure MSDE and SQL Server 2000 databases for use with a Web
Supervisor.
Configuring the Web Supervisor to Use an MSDE or SQL
Server 2000 Database
The following procedure explains how to configure the Web Supervisor to ensure that it can use either MSDE
or SQL Server 2000 in lieu of the native Cloudscape database for archiving logs and notifications locally.
Procedure 1
Set Web Supervisor logging and notification archiving to local.
Step 1
From the Windows Start menu, select Programs > Niagara 2.301.330.v1 > Java Desktop
Environment to start the JDE.
Step 2
Use the Admin Tool to open the local host.
Step 3
From the File menu, select Open Offline.
Step 4
In the Open Offline Project dialog, select the station name from the drop-down dialog.
Step 5
Type the user name and password.
Step 6
Click Open.
Step 7
Expand the station to the Services container.
Step 8
In the Services container, right-click Log and select Go > Properties.
Step 9
Select the Config tab.
Step 10
On the Config tab, from the archiveMode drop-down list select archive_local.
Step 11
Click Apply.
All of your logs will now archive locally. This will allow them to be stored in either the MSDE or SQL
Server 2000 database.
Step 12
In the Services container, right-click Notification and select Go > Properties.
Step 13
Select the Config tab.
Step 14
On the Config tab, from the archiveMode drop-down list select archive_local.
Step 15
Click Apply.
All of your notifications will now archive locally. This will allow them to be stored in either the MSDE
or SQL Server 2000 database.
MSDE or SQL Server 2000 Database Installation and Configuration Instructions
Niagara Release 2.3
Revised: January 7, 2003
11
Installation and Configuration
Installing and Configuring an MSDE Database
Installing and Configuring an MSDE Database
The following procedure describes how to install and configure MSDE to act as your Web Supervisor database.
Procedure 2
Step 1
Install and configure MSDE to act as the database on the Web Supervisor PC.
Install MSDE on the Web Supervisor host.
a. From the Windows Start menu, select Programs > Accessories > Windows Explorer.
b. Navigate to the CD drive where the Niagara CD is available.
c. Expand the Niagara CD tree to the msde2k folder.
d. Double-click installMSDE.exe to run the MSDE installer.
e. Press Enter to install MSDE to the default location.
Note
MSDE should be installed on the same host as the Web Supervisor software.
Step 2
From the Windows Start menu, select Programs > Niagara 2.301.330.v1 > Java Desktop
Environment to start the JDE.
Step 3
Use the Admin Tool to open the local host.
Step 4
In the Admin Tool Installation tab, click View License.
Step 5
In the license.properties window, ensure that the Web Supervisor host is licensed to run the MSDE
database. The database type line should read:
databaseType=MSDE
Note
If your license file does not indicate that you are licensed to run an MSDE database, send an e-mail to
[email protected] to get an updated license.properties file. You cannot run an MSDE database
on your Web Supervisor without the correct entry in the license.properties file.
Step 6
Ensure that the station you want to run on the MSDE database is not running. If it is, stop the station
using the Admin Tool.
Step 7
From the File menu, select Open Offline.
Step 8
In the Open Offline Project dialog, select the station name from the drop-down list.
Step 9
Type a user name and password for the station.
Step 10
Click Open.
Step 11
In the station tree, expand the Services container.
Step 12
Right-click on the Database service and select Properties.
Step 13
On the General tab, select Config.
Step 14
On the Config tab, from the databaseType drop-down list, select MSDE.
Step 15
Click Apply.
12
MSDE or SQL Server 2000 Database Installation and Configuration Instructions
Revised: January 7, 2003
Niagara Release 2.3
Installation and Configuration
Converting an Existing Cloudscape Database to MSDE SQL
Step 16
Select the MS SQL Server tab.
Step 17
In the jdbcConnectionUrl field, change the localhost port from 1433 to 3015. The line should now
read: jdbc:microsoft:sqlserver://localhost:3015;SelectMethod=cursor
Note
If you are connecting to a remote MSDE installation, you must replace localhost in the
jdbcConnectionUrl field with the IP address or host name of the remote server. Remember that
Tridium does not support this configuration, so you implement this option at your own risk.
Step 18
In the databaseUser field, set the user name to sa (unless the default username has been changed).
Step 19
Leave the databasePassword field blank (unless the default password has been changed).
Step 20
From the createNewDatabase drop-down list, select True.
Step 21
Leave the databaseName, databaseDataFilename, and databaseLogfilename fields blank. MSDE
will populate these fields when it creates the database.
Step 22
Click Apply.
Step 23
Ensure that you have all of the logging in the station set to archive_local.
Step 24
Once the console window indicates that the database has been created successfully, start the station in
the JDE using the Admin Tool.
Step 25
Right-click on the station name in the Admin Tool and select Standard Output to ensure that the
station started correctly and that the database is running.
Converting an Existing Cloudscape Database to MSDE
SQL
If you have an existing Cloudscape database that you need to convert to an MSDE-compatible SQL database,
follow the steps in Procedure 3.
Procedure 3
Convert an existing Cloudscape database to an MSDE SQL database.
Step 1
From the Windows Start menu, select Programs > Niagara 2.301.330.v1 > Console.
Step 2
In the Niagara Command Line window (the console), type:
dbadmin station_name m cs ms localhost:3015 sa null
where station_name is the name of the Web Supervisor station database that you are converting from
Cloudscape to MSDE SQL.
Note
Step 3
If you are connecting to an MSDE installation running on a remote host, you must replace localhost
in the command with the IP address or host name of the remote host. Remember that Tridium does not
support this configuration, so you implement this option at your own risk.
Open the JDE.
MSDE or SQL Server 2000 Database Installation and Configuration Instructions
Niagara Release 2.3
Revised: January 7, 2003
13
Installation and Configuration
Upgrading an MSDE Installation to an SQL Server 2000 Installation
Step 4
Open the local host.
Step 5
Open the station off-line.
Step 6
Expand the station tree to the Database service.
Step 7
Right-click the Database service and select Go > Properties.
Step 8
On the MS SQL Server tab, select the Config tab.
Step 9
Set the createNewdatabase field to false.
Step 10
Click Apply.
Step 11
Start the station in the JDE using the Admin Tool.
Step 12
Right-click on the station name in the Admin Tool and select Standard Output to ensure that the
station started correctly and that the database is running.
Upgrading an MSDE Installation to an SQL Server 2000
Installation
If you find that you need to migrate your MSDE application to SQL Server because of additional data storage
or data manipulation needs, you have several options:
One option is to simply install SQL Server 2000 on top of your existing MSDE installation.
• You can also remotely administer your MSDE installation by pointing your SQL Server host to the MSDE
host and uploading the MSDE data to the SQL Server’s database.
• Finally, you can detach the MSDE data file and reattach it on a SQL Server host’s database. These tasks
are all outside of the scope of this documentation. Consult the MS SQL Server 2000 documentation for
additional information on these tasks.
You must get a new license.properties file from Tridium to upgrade to an SQL Server 2000 installation from
an MSDE installation. There will be additional fees and costs associated with this upgrade.
•
Configuring an SQL Server 2000 Database
The following procedure describes how to configure a remote installation of SQL Server 2000 to act as your
Web Supervisor database. It assumes that a DBA has already created the appropriate database, user name, and
passwords for you on the SQL 2000 Server. The DBA must create the database and a user account with
db_owner privileges. This user account must have permission to create tables and write data to the database. The
DBA must tell you the TCP port used by the SQL Server installation. The default port is 1433, but the DBA may
have changed this for security reasons. The DBA must tell you the path where the data and log files reside on
the database. The paths to these files will be relative to the host running the SQL Server 2000 software.
Procedure 4
Configure an installation of SQL Server 2000 to act as the database for the Web Supervisor PC.
Step 1
From the Windows Start menu, select Programs > Niagara 2.301.330.v1 > Java Desktop
Environment to start the JDE.
Step 2
Use the Admin Tool to open the local host.
14
MSDE or SQL Server 2000 Database Installation and Configuration Instructions
Revised: January 7, 2003
Niagara Release 2.3
Installation and Configuration
Configuring an SQL Server 2000 Database
Step 3
In the Admin Tool Installation tab, click View License.
Step 4
In the license.properties window, ensure that the Web Supervisor host is licensed to run the SQL
Server 2000 database. The database type line should read:
databaseType=MS_SQL_SERVER
Note
If your license file does not indicate that you are licensed to run a SQL Server 2000 database, send an
e-mail to [email protected] to get an updated license.properties file. You cannot run an SQL
Server 2000 database on your Web Supervisor without the correct entry in the license.properties
file.
Step 5
Ensure that the station you want to run on the SQL Server 2000 database is not running. If it is, stop
the station using the Admin Tool.
Step 6
From the File menu, select Open Offline.
Step 7
In the Open Offline Project dialog, select the station name from the drop-down list.
Step 8
Type a user name and password for the station.
Step 9
Click Open.
Step 10
In the station tree, expand the Services container.
Step 11
Right-click on the Database service and select Properties.
Step 12
On the General tab, select Config.
Step 13
On the Config tab, from the databaseType drop-down list, select MS_SQL_Server.
Step 14
Click Apply.
Step 15
Select the MS SQL Server tab.
In the jdbcConnectionUrl field, the line currently reads:
jdbc:microsoft:sqlserver://localhost:1433;SelectMethod=cursor
Replace localhost with the IP address or host name (if you are using local DNS to resolve names)
of the machine running the SQL Server 2000 software. If your DBA changed the TCP port on the SQL
Server, replace 1433 with the port number provided by your DBA.
Step 16
In the databaseUser field, type the user name provided by your DBA.
Step 17
In the databasePassword field, type the password provided by your DBA.
Step 18
From the createNewDatabase drop-down list, select False.
Step 19
In the databaseName field, type the database name provided by your DBA.
Step 20
In the databaseDataFilename and databaseLogFilename fields, type the paths provided by your
DBA. These are relative paths to the file locations on the host running the SQL Server 2000 software.
Step 21
Click Apply.
Step 22
Ensure that you have all of the logging in the station set to archive_local.
Step 23
Start the station in the JDE using the Admin Tool.
MSDE or SQL Server 2000 Database Installation and Configuration Instructions
Niagara Release 2.3
Revised: January 7, 2003
15
Installation and Configuration
Converting an Existing Cloudscape Database to an SQL Server 2000 Database
Step 24
Right-click on the station name in the Admin Tool and select Standard Output to ensure that the
station started correctly and that the database is running.
Converting an Existing Cloudscape Database to an SQL
Server 2000 Database
If you have an existing Cloudscape database that you need to convert to an SQL Server 2000 database, follow
the steps in Procedure 5.
Procedure 5
Convert an existing Cloudscape database to an SQL Server 2000 Database.
Step 1
From the Windows Start menu, select Programs > Niagara 2.301.330.v1 > Console.
Step 2
In the Niagara Command Line window (the console), type:
dbadmin station_name m cs ms host_IP:TCP_port user_name password
where:
•
is the name of the Web Supervisor station database that you are converting from
Cloudscape to SQL Server 2000
•
host_IP
•
TCP_port
•
user_name
•
password
station_name
is the IP address of the host where the SQL Server 2000 software is running
is the TCP port it is running on
is the user name the DBA assigned you
is the password associated with that user name
Step 3
Once the console window indicates that the database has been created successfully, open the JDE.
Step 4
Open the local host.
Step 5
Open the station off-line.
Step 6
Expand the station tree to the Database service.
Step 7
Right-click the Database service and select Go > Properties.
Step 8
On the MS SQL Server tab, select the Config tab.
Step 9
Set the createNewdatabase field to false.
Step 10
Click Apply.
Step 11
Start the station in the JDE using the Admin Tool.
Step 12
Right-click on the station name in the Admin Tool and select Standard Output to ensure that the
station started correctly and that the database is running.
16
MSDE or SQL Server 2000 Database Installation and Configuration Instructions
Revised: January 7, 2003
Niagara Release 2.3