Database Admin

IHS
Database Administration
User Manual
December 2012 v8.8
2012 IHS. All Rights Reserved. All trademarks belong to IHS

or its affiliated and subsidiary companies. All rights reserved.
www.ihs.com/Kingdom
Trademarks and Copyright

This manual was produced by IHS Inc.
Version 8.8
December 2012
.
8584 Katy Freeway, Suite 400

Houston, Texas 77024
U.S.A.
Tel: (713) 464-6188
Fax: (713) 464-6440
Website: wwwkingdom.ihs.com
Sales: etasales@ihs.com
Support: support@seismicmicro.com
The following trademarks appear in this manual.

IHS Kingdom software and all of its components, 2dPAK, 3dPAK, 2d/3dPAK, AVOPAK,
CGMPAK, EarthPAK, LoadPAK, ModPAK, PAKnotes, IHS Petra, SynPAK,
Tunnel L+, Tunnel O, VelPAK, VuPAK, Kingdom 1D Forward Modeling, Kingdom Colored
Inversion, The Kingdom Company, Kingdom Data Management, Kingdom DM Catalog
Builder, Kingdom Illuminator, Kingdom Seeker, are trademarks or registered trademarks of
IHS Inc.
Portions of data loading are copyrighted by Blue Marble Geographics.
VuPAK includes OpenInventor and VolumeViz from Visualization Sciences Group, Inc. Some
components or processes may be licensed under U.S. Patent Number 6,765,570.
ModPAK includes SHAPES from XOX Corporation.
Tunnel L+ includes OpenWorks and SeisWorks Development Kit from the Landmark Graphics
Corporation.
Kingdom Connect and Tunnel O include OpenSpirit FrameWork from OpenSpirit, a TIBCO
Software Group Company.
Kingdom Data Management includes components from OpenSpirit and are copyrighted by OpenSpirit,
a TIBCO Software Group Company.
1D Forward Modeling includes software developed as part of the NPlot library project available from:
http://www.nplot.com/.
Portions of Kingdom bitmap graphics are based on GD library by Boutell.Com, Inc. Further
information about the company can be found at www.boutell.com.
PAKnotes TIFF support is based in part on libtiff.
iii
Rock Solid Attributes is a trademark of RDSP I, L.P. Solid Attributes contains confidential,
proprietary, and trade secret information of RDSP I, L.P. This unpublished work by RDSP I, L.P. is
protected by the laws of the United States and other countries. Additionally, if publication occurs, the
following notice shall apply: Copyright RDSP I, L.P., All Rights reserved.
Baker Hughes JewelSuite is a trademark of Baker Hughes. JewelSuite contains confidential,
proprietary and trade secret information of Baker Hughes.
Microsoft is a registered trademark of Microsoft Corporation. Windows 2000, Windows XP, and
Windows XP x64, Windows Vista, Windows 7 operating systems, MS-DOS and SQL Server are
trademarks of Microsoft Corporation. Oracle Databases are registered trademarks of Oracle
Corporation. OpenWorks, SeisWorks, Interpret 2000 and Interpret 2003 are registered trademarks of
Landmark Graphics Corporation.
IHS Inc. incorporates BMC AppSight Black Box Technology in its software. BMC Software,
BMC Software logos and all other BMC Software product and service names are registered
trademarks or trademarks of BMC Software Inc. 2009 BMC Software, Inc. All rights reserved.
All other trademarks are the property of their respective holders.
2011 - 2012 IHS Inc.

All Rights Reserved Worldwide
Kingdom and this manual are both copyrighted and intended for use by a single user or a single
computer whose model is authorized by IHS Inc. You are entitled to electronically transcribe Kingdom
DVD to the hard disk of an authorized computer so long as Kingdom and related software packages
are operated on only one computer at a time. You are further entitled to electronically transcribe the
DVD to other DVD(s) for archival storage only. Physical duplication of the Kingdom software and
SENTINEL is expressly forbidden. No portion of Kingdom software may be incorporated into any
other program. No other usage or transcription in any form is allowed without the express written
permission of IHS Inc.
No portion of this manual may be reproduced, transmitted, transcribed or stored on any information
retrieval system, or translated into any foreign language or any computer language in any form and by
any means whatsoever without the express written permission of IHS Inc. This document contains
confidential information and trade secrets proprietary to IHS Inc.
Misuse Disclaimer
IHS Inc. makes no representation or warranties of any kind with respect to this manual or the Kingdom
software. Specifically, IHS Inc. disclaims any implied or any other claimed warranties of
merchantability or suitability for any particular purpose. IHS Inc. reserves the right to modify the
Kingdom software and any of the associated user documentation at any time.
Acknowledgments
IHS Inc. wishes to gratefully acknowledge the contributions of the many client software testers in
preparing the Kingdom software. The enthusiastic Beta testers, smoke testers, and IHS Inc.staff greatly
appreciate their invaluable feedback and contributions.
iv
Table of Contents
Database Considerations
Choosing a Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Microsoft Access Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Advantages of Oracle and SQL Server as a Project Database . . . . . . . . . . . .
An Error Occurred Connecting to the Database . . . . . . . . . . . . . . . . . . . . . . . . . .
3
4
5
6
Microsoft SQL Server Express as the Project Database

Kingdoms SQL Server Express. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How is Auto SSE different from Manual SSE? . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auto SSE and Backward Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing an Auto SSE Project back to Manual SSE. . . . . . . . . . . . . . . . . . . .
Connecting to your SQL Server Express Database. . . . . . . . . . . . . . . . . . . . . . . .
My Kingdom SSE instance is not listed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Error Occurred Connecting to the Database . . . . . . . . . . . . . . . . . . . . . . . . . .
Connection Requirements for Auto SSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing your Manual SQL Server Express Projects. . . . . . . . . . . . . . . . . . . . . .
7
9
10
10
14
14
15
18
19
SQL Server Express Service Configuration

What is your Working Environment? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Unable to start the service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Manual SQL Server Express (SSE) Management

Manage your Manual SSE Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Basic SSE Management Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Make a Project Portable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Attach Portable Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Make an Active Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create a Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restore a Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Move Project Files Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Delete an Entire Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting SQL Express Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows File Sharing and Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows Access Privilege Matrix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
30
32
37
42
44
46
48
50
51
52
57
62
Microsoft SQL Server as the Project Database

SQL Server Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Kingdom 8.8
Table of Contents
Installing and Configuring a SQL Server Database . . . . . . . . . . . . . . . . . . . . . . . .

Install Microsoft SQL Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verify the SQL Server Database is Running . . . . . . . . . . . . . . . . . . . . . . . . . .
Connect to the SQL Server Management Studio. . . . . . . . . . . . . . . . . . . . . . .
Create SQL Server Databases and Logins . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set SQL Server Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create a Project using the Microsoft SQL Server Database . . . . . . . . . . . . . .
Connecting to your SQL Server Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
My SQL Server instance is not listed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Error occurred connecting to the database . . . . . . . . . . . . . . . . . . . . . . . . . . .
66
66
67
68
69
72
73
76
76
76
Oracle as the Project Database

Oracle Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Oracle Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create Required Tablespaces and Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create Oracle Users for Kingdom Projects . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing and Configuring the Oracle Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Install the Oracle Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create Oracle Service Name on Oracle Client . . . . . . . . . . . . . . . . . . . . . . . .
Set Oracle as the Kingdom Project Database . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting to your Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
79
80
80
84
89
89
90
93
95
Kingdom Project Backups

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What do I Backup?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Backing up Kingdom Project Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Make a Single Project Manual Backup with DBAdmin. . . . . . . . . . . . . . . . . . . . . .
Restore a Kingdom Project with DBAdmin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Automating SQL Server and SQL Server Express Backups . . . . . . . . . . . . . . . . .
Creating the Backup Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scheduling the Backup with SQL Server Agent . . . . . . . . . . . . . . . . . . . . . . . .
97
98
99
101
104
108
108
113
Kingdom Project Database Conversions

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migrate Access Database to SQL Server or Oracle. . . . . . . . . . . . . . . . . . . . . . . .
Convert Your SQL Server Express Project Back to Access . . . . . . . . . . . . . . . . . .
Create a Database Dump of the Original Project. . . . . . . . . . . . . . . . . . . . . . .
Import the Database Dump File into the Original Access Database . . . . . . . .
Check the Status of the Converted Project . . . . . . . . . . . . . . . . . . . . . . . . . . .
Convert SQL Server or Oracle Database to Access with DBAdmin. . . . . . . . . . . .
Create a Twin Access Database if no Access Database Exists . . . . . . . . . . .
Import the Database Dump File into the Target Access Database. . . . . . . . . .
Check the Status of the Converted Project . . . . . . . . . . . . . . . . . . . . . . . . . . .
Convert SQL Server Database to Oracle (or vice versa) with DBAdmin . . . . . . . .
Create an Empty Target Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
121
122
124
125
127
128
129
129
132
133
134
135
135
137
Kingdom 8.8
Import the Database Dump File into the Target Database . . . . . . . . . . . . . . . . 139
Database Admin (DBAdmin) Tool

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DBAdmin Database Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connect to a Project Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database Admin Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Backup Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DBAdmin License Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
141
143
143
145
148
154
OpenKingdom Data Server

OpenKingdom Data Server Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Select License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Project Seismic File Locator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Global Seismic File Locator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Kingdom 8.8
155
156
156
157
158
vii
Table of Contents
viii
Kingdom 8.8
Database Administration
Kingdom Database Administration includes the following:
Database Considerationshelps you decide which database (SQL Server, SQL Server
Express, Oracle, or Access) is best for your Kingdom environment.
Microsoft SQL Server Express as the Project Databasecovers installing SQL Server
Express, migrating Access databases to SQL Server Express, and connecting to SQL
Server Express Databases.
SQL Server Express Service Configurationcontains detailed information on configuring

your SQL Server Express service for use in a network environment including
troubleshooting tip if the service is unable to start.
Manual SQL Server Express (SSE) Managementdetails how to manage your Manual
SQL Server Express projects and convert an Auto SSE project to the manual
configuration.
Microsoft SQL Server as the Project Databaserequires a server and client installation
and user authentication. SQL Server requires Windows or SQL Server authentication for
access to the project.
Oracle as the Project Databaserequires configuring the Oracle Host and installing and
configuring the Oracle Client. Oracle also requires user authentication for access to the
project.
Kingdom Project Backupsdescribes procedures to backup the project files, the project
database, external files, and custom color bar files.
Kingdom Project Database Conversionscovers processes to convert Kingdom project

databases from one type to another. Some conversions use the database export
functionality in the Database Admin tool. Conversions from Access are available when
opening an Access project in Kingdom 32-bit or 64-bit.
Database Admin (DBAdmin) Toolexplains the Database Admin Tool which is used to
examine and edit (if required) Kingdom project database tables, copy and convert project
databases.
OpenKingdom Data Servercontains settings required to transfer data to and from

Kingdom projects using Kingdom Connect or Tunnel O.
Kingdom 8.8
Kingdom 8.8
Database Considerations
Choosing a Database
Kingdom Software 64-bit applications allow you to benefit from the full power of 64-bit
computing and enjoy a significant increase in application performance:
increased memory capacity (many 64-bit workstations can have up to 128 GB of RAM)
increased addressable memory (8 Terabytes)
improved graphics capabilities
Kingdom 64-bit as well as most Kingdom Advanced modules require the scalability and
performance attributes provided by SQL and Oracle databases and require one of the
following:
SQL Serverrequires installation and configuration of a central server and a local client.
Two options are available:
-
SQL Server (Single)creates a project specific database. With this configuration,

each project will have its own database in the selected SQL Server instance.
SQL Server (Multiple)adds the project to an existing database that may contain
multiple Kingdom projects. The tables for each project have a unique number as a
prepend to the table name. See Microsoft SQL Server as the Project Database.
Kingdoms SQL Server Express

-
Auto SSEis configured to be automatically portable. As long as all data is contained

in the project folder, when all authors are out of the project, the project can be copied
or moved without any tools or special operations.
Manual SSEhas the original configuration introduced with Kingdom 8.2 and is
compatible with Kingdom versions 8.2 and later. Management of your Manual SSE
projects is done through the Manual SSE Management Tool available from the
Kingdom Start Page.
Oraclerequires installation and configuration of a central server and a local client. See
Note: The Kingdom Software is not certified on Oracle Express Edition.
Kingdom 8.8
Kingdom 64-bit is NOT compatible with an Access database. When you open an Access
project with Kingdom 64-bit, you will be required to migrate the Access database to one of the
databases listed above.
Related Topics
Microsoft Access Usersprovides important information about using Microsoft Access as
your project database.
The Planning Guide provides additional information on moving from Kingdom 32-bit to
Kingdom 64-bit.
Advantages of Oracle and SQL Server as a Project Databasediscusses the benefits provided
by Oracle and SQL Server as your project database.
An Error Occurred Connecting to the Databaselinks to troubleshooting tips if you are
having trouble connecting to an existing database.
Microsoft Access Users

Kingdom Core 32-bit supports Microsoft Access as a database.
Kingdom 64-bit and most Kingdom Advanced modules on 32-bit or 64-bit do not support
Access as a database.
If your projects are currently in Access but you would like to run Kingdom 64-bit or have
upgraded to Kingdom Advanced, a database upgrade to SQL Server Express, SQL Server, or
Oracle is required.
SQL Server Express (SSE) is Microsofts replacement for Access on the 64-bit systems.
Kingdom provides an upgrade to SSE at no extra cost.
Kingdoms customized version of SSE is automatically installed when you install Kingdom
versions 8.5 and later. However, if you do not want to install SSE you can deselect this feature
during installation.
SQL Server Express can also be downloaded from the Kingdom website and then installed on
your machine, or installed from the Kingdom Installation Manager on the Kingdom Software
DVD.
Note: Kingdom projects with SQL Server Express databases can be used with both 32-bit
and 64-bit versions of Kingdom.
Note: 32-bit software will generally run on a 64-bit computer, but 64-bit software will not
run on a 32-bit computer.
Kingdom 8.8
Even with Kingdom Core 32-bit users, Access has some inherent limitations which may make
it less desirable for use with large projects or in a large office:
Multiple users in a single project can affect Kingdom performance. More than five users
can make performance noticeably slower.
In a multi-user environment, Microsoft Access database updates may fail under a heavy
input/output load which could result in a loss of data.
Access has a 2 GB single database size limit.
Multiple Access projects may be more difficult to administer locally by a central database
administrator. If these databases are distributed, then backups may be more of a chore than
if a central database were used.
Many companies prefer to use the extra security measures they associate with an external
relational database management system (RDBMS) such as Oracle or SQL Server.
Advantages of Oracle and SQL Server as a

Project Database
Oracle and SQL Server databases have several advantages especially in larger organizations
where security is a requirement and very large, multi-author projects are the norm.
Note: The following points do not apply to SQL Server Express.
In theory, there is no database size limitation. Databases are actively sizeable to allow
project growth.
They provide an additional level of protection by requiring user authentication prior to

opening the project. A Kingdom project is assigned to an Oracle or SQL Server account
for which users must know the password. These accounts are not related to Kingdom
authorship or interpretation ownership, but to database table access only.
The Oracle instance can reside on any server, be it UNIX, Linux or Windows. Kingdom
requires the Oracle client for Windows be installed on the local PC, but the Oracle
database server can run anywhere.
Note: Kingdom 32-bit requires the Oracle 32-bit client and Kingdom 64-bit requires the
Oracle 64-bit client. Both clients can be installed on the workstation which will allow
both versions of Kingdom to connect to Kingdom Oracle projects.
Oracle and SQL Server use snapshot creation (making database edits pending), so the
administrator can do a backup without shutting down the database and asking users to exit
their instance of the project.
Kingdom 8.8
An Error Occurred Connecting to the Database
An Error Occurred Connecting to the

Database
If you received an error message when trying to connect to your database, click the database
type below for troubleshooting tips:
Connecting to your SQL Server Express Database
Connecting to your SQL Server Database
Connecting to your Oracle Database
Kingdom 8.8
Microsoft SQL Server Express as

the Project Database
Kingdoms SQL Server Express
SQL Server Express is provided free of charge on the Kingdom Software DVD and on the
IHS Kingdom website. This version of SQL Server Express has a dedicated Kingdom instance
with a pre-configured user name and password to make the upgrade seamless.
Only one installation is required. Once SQL Server is installed, you can select the auto or
manual portability configuration when you create or open a project to suite your portability
and project management needs:
Auto SSEis configured to be automatically portable. As long as all data is contained in

the project folder, when all authors are out of the project, the project can be copied or
moved without any tools or special operations.
Manual SSEhas the original portability configuration introduced with Kingdom 8.2.
Management of your Manual SSE projects is done through the Manual SSE Management
Tool available from the Kingdom Start Page. Projects using the Manual SSE portability
configuration are backward compatible to Kingdom 8.2.
SQL Server Express can only run on Microsoft operating systems. For Linux / Unix servers,
you will need to install Oracle.
What are you trying to do?

Decide which type of SQL Server Express to use for my Kingdom projects.
-
See How is Auto SSE different from Manual SSE?
Ive just installed SQL Server Express and need help configuring the service.
-
First select Local or Network.
If you are in a network environment, you will need help from your domain
administrator. See Network ProjectNetwork Database Instance for instructions.
Update my Kingdom projects with Access databases to SQL Server Express.

-
See Migrate Access Database to SQL Server Express
Kingdom 8.8
I cant connect to the database or start the service.

-
Connecting to your SQL Server Express Database troubleshooting tips
Unable to start the service
Im using the Manual option and need to make my project portable.

-
Manual SQL Server Express (SSE) Management provides details on how to copy,
move, backup, restore, and delete your Kingdom projects.
Kingdom 8.8
How is Auto SSE different from Manual

SSE?
Kingdom versions 8.5 and later include an auto portability option for the SQL Server Express
database. Auto SSE is designed to minimize database management and differs from Manual
SSE in the following ways:
Auto SSE
Manual SSE
Places the database in the Kingdom project directory

in a folder named ProjectDatabase.
Places the database in the KingdomSuite

directory under Program Files (x86) on
the machine where the instance is
installed.
Automatically attaches the database when the first

user opens the project
Does not automatically detach / attach
Automatically detaches the database when the last

user exits the project
You must use the Manual SSE

Management tool to detach (make
portable) or attach
After all users exit the project, you can copy / move
the project with Windows Explorer
After all users exit the project, you must

use the Manual SSE Management tool to
copy/move the project
Supports the following location combinations:
Supports mixed mode location

combinations for your project folder and
SSE instance. Your project on the network
can connect to a local instance and vice
versa.
Local ProjectLocal Database Instance
Network ProjectNetwork Database Instance
Projects with the auto portability configuration have the same management simplicity as
Access projects. When the last author exits the project, the project folder can be moved or
copied with the database intact.
Note: Only data stored inside the project folder will be included in any move or copy. Data
stored outside of the project folder such as seismic files, author files, or tiff images of
your raster logs, will need to be copied separately.
Kingdom 8.8
How is Auto SSE different from Manual SSE?
Related Topics
Auto SSE and Backward Compatibilityprovides instructions if you want to open your Auto
SSE project in an earlier version of Kingdom.
Changing an Auto SSE Project back to Manual SSEchanging from auto to manual is done
through the Manual SQL Server Express Management tool.
Auto SSE and Backward Compatibility

If you want to open a project with the auto portability configuration in Kingdom 8.5 Release
or earlier, you will need to change the project to the manual portability configuration using the
Make a Project Portable option in the Manual SQL Server Express Management tool.
Note: Projects changed back to the manual portability configuration are also compatible with
Kingdom version 8.5 SP2 and later.
1. Launch the tool from the Kingdom Start Page. Select Manage Manual SQL Server
Express Projects.
2. Select one of the Make Project Portable options.
3. Browse to the project *.tks file.
4. Click Start to Make a portable copy of the project or to make that project portable.
5. Click Yes in the message to continue with the Manual SSE configuration.
6. When the process is finished, the Summary Report will display project details.
The project is packaged in its current location into a folder called <project
name>_portable_<date yyyymmdd>_<time>.
The project now has the manual portability configuration and can be opened in Kingdom
versions 8.2 and later.
To open this project, use the Attach Portable Project option in the Manual SQL Server Express
Management tool.
Changing an Auto SSE Project back to Manual

SSE
Changing a project from Auto SSE back to Manual SSE involves the following steps:
1. Launch the Manual SQL Server Express Management tool from the Kingdom Start Page.
10
Kingdom 8.8
2. Apply any of the options available in the management tool to change the project to
Manual SSE.
See Manage your Manual SSE Projects for detailed workflows.
Note: Converting or copying an Auto SSE project to a different instance using Kingdom
Data Management changes the project to Manual SSE.
Kingdom 8.8
11
How is Auto SSE different from Manual SSE?
Migrate Access Database to SQL

Server Express
When you open a Kingdom project with an Access database, you will be prompted to migrate
your project database. For SQL Server Express you have 2 options: Auto SSE and Manual
SSE. See How is Auto SSE different from Manual SSE?
You can also open the database migration tool from the Kingdom Start Page. Click the
Migrate Access Project link under Tools and browse to the *.tks file of the Access project.
See Connection Requirements for Auto SSE for supported work environments.
If you are running the 32-bit version of Kingdom, you will be prompted to migrate your
project, but the database migration is optional. If you are running the 64-bit version of
Kingdom, you must migrate the project before you can open it.
Note: After migration, the Kingdom project folder remains in the same location with the
same name. The Access database is renamed and the <project name>.xml file is
created. This .xml file is the pointer to the project database in the Kingdom instance of
SQL Server Express.
Note: For best results when migrating your project data, make sure your computer is set to
English (United States) in the Control Panel > Region and Language options. After
the database has migrated, you can change the language back to your choice. However,
Kingdom requires that the decimal symbol be a period, and not a comma.
To migrate your Access database to SQL Server Express, select the Auto or Manual SQL
Server Express and Yes.
Migrate Access Project to Auto SSE
Migrate Access Project to Manual SSE
Migrate Access Project to Auto SSE

1. In the Migrate Project Database dialog box select Auto SQL Server Express and Yes Migrate.
2. If your project and SQL Server Express instance are both on your workstation, the project
will automatically migrate to that instance and open.
If your project and SQL Server Express instance are both on the same workstation in your
work group, you will have to select the SQL Server Express instance.
12
Kingdom 8.8
If your project and SQL Server Express instance are on different computers on the
network, you will need to select the instance on the network that has been configured as
the network instance. See Network ProjectNetwork Database Instance for details.
3. When the migration is complete, the Select Author dialog box opens, and your project is
ready to go in SQL Server Express.
Migrate Access Project to Manual SSE

1. In the Migrate Project Database dialog box select Manual SQL Server Express and Yes Migrate.
2. Select the SQL Server Express instance you want to connect to and click OK.
3. When the migration is complete, the Select Author dialog box opens, and your project is
ready to go in SQL Server Express.
Kingdom 8.8
13
Connecting to your SQL Server

Express Database
The following section gives troubleshooting tips for a database migration to SQL Server
Express. These tips also apply to problems opening an existing SQL Server Express Kingdom
project.
My Kingdom SSE instance is not listedwhen creating a project, you cannot see your SQL
Server Express instance in the list of available instances.
Error Occurred Connecting to the Databasea general error message when trying to create or
open a SQL Server Express project could be caused by a number of reasons.
Connection Requirements for Auto SSEif you received an error message when creating an
Auto SSE project stating that the instance did not have adequate permission to read/write to
the project database file, you may need to change permissions on the project directory or
change the log on account of the SQL Server (SMTKINGDOM) service.
Related Topics:
My Kingdom SSE instance is not listed

If you have already installed the SMTKINGDOM instance of SQL Server Express from the
Update Manager or from the Kingdom Software DVD and you still cannot see your instance
in the drop down list as in the figure below, there are multiple reasons.
Before troubleshooting, try typing the installed SQL Server Express instance into the SQL
Server Connect field. Remember, the instance will have \SMTKINGDOM at the end.
14
Kingdom 8.8
After you enter the instance, the User Name and Password fields will disappear.
Click OK to continue.
If you receive an error message see Error Occurred Connecting to the Database
Error Occurred Connecting to the Database

If you get An error occurred connecting to the database. Would you like to try again?,
Click No and try the following solutions:
Problem 1: One of the SQL Server services is not running.
Solution 1: Open the Administrative Tools on the computer where SQL Server Express is
installed and start the service(s):
1. Click Start > Settings > Control Panel > Performance and Maintenance >
Administrative Tools > Services.
2. Scroll down to locate the SQL Server services. Check that SQL Server (SMTKINGDOM)
and the SQL Server Browser are Started.
In the figure below, the SQL Server (SMTKINGDOM) database service is not started.
Kingdom 8.8
15
3. To start a service, right click beside the service in the Status column and select Start.
4. Now open the Access Kingdom project with Kingdom 64-bit and try the project migration
again.
Problem 2: One of the TCP/IP protocols is not enabled.
If the SQL Server Express instance you are migrating to is not local (on your computer),
the TCP/IP protocols on the remote database instance and on your local (client) machine
must be enabled. If the SQL Server Express instance is on your machine, this is not an
issue.
Solution 2A: On the computer where SQL Server Express is installed, open the SQL Server
Configuration Manager and Enable the TCP/IP protocol:
1. Click Start > Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL
Server Configuration Manager.
16
Kingdom 8.8
Figure 1 Enable TCP/IP Protocol
2. Under SQL Server 2005 Network Configuration, select Protocols for SMTKINGDOM.
3. In the right panel, check if the TCP/IP protocol is Enabled. If it is Disabled as in the figure
above, right click Disabled and select Enable.
4. You will need to restart the database service.
a. In the same Configuration Manager, select SQL Server 2005 Services in the left
panel.
b. In the right panel right click SQL Server (SMTKINGDOM) and select Restart.
Solution 2B: Now return to the Kingdom workstation and Enable the TCP/IP Client Protocol
using the same procedure:
2. Under SQL Native Client Configuration, select Client Protocols.
3. In the right panel, check if the TCP/IP protocol is Enabled. If it is Disabled, right click
Disabled and select Enable.
Note: The default status for these protocols is Enabled.
Warning: After you have completed parts A and B of the solution, open the Access Kingdom
project with Kingdom 64-bit and try the project migration again.
Kingdom 8.8
17
Connection Requirements for Auto SSE

When using the Auto SSE option, successful connectivity depends on the configuration of
your working environment:
The following combinations are supported:
Kingdom projects are

on your workstation or
on a colleagues
workstation.
You are a single user or have

a small work group.
Install SQL Server Express on the

same computer as the Kingdom
project and use a Local Project
Local Database Instance
configuration.
Kingdom projects are

on a shared resource on
the network
The Kingdom project and

SQL Server Express
instance are on different
machines.
Install SQL Server Express on a

network computer - not on your
workstation.
This configuration requires a
Network ProjectNetwork
Database Instance solution.
Note: When using Auto SSE, projects on the network cannot connect to a local SSE
instance. Similarly, local projects cannot connect to an SSE instance on the network.
Local ProjectLocal Database Instance

Your project and your SQL Server Express (SMTKINGDOM) instance are both on your local
workstation or another workstation in your work group.
This is the simplest configuration. After you change your project to Auto SSE, no further
action is required. When you close the project, it will be portable.
How do I install SQL Server Express on my workstation?
18
Kingdom 8.8
Managing your Manual SQL Server

Express Projects
With Manual SQL Server Express projects, like SQL Server and Oracle, the project database
is tied to the server on that computer. The database no longer resides in the project folder as it
does with Auto SSE projects or MS Access projects. Therefore, to copy, move, backup or
delete the project, you need to consider both the project folder and the database.
Note: If your projects have the auto portability configuration, you do not need to use this tool
unless you want to open your project with Kingdom 8.5 or earlier - or if you want to
convert your project from Auto SSE back to Manual SSE.
Changing an Auto SSE Project back to Manual SSE
You can manage the Manual SSE project by two methods:
1. Manual SQL Server Express (SSE) Managementa utility that enables you to copy,
move, backup, and delete your SQL Server Express projects if they have the
SMTKINGDOM pre-coded instance.
On the Kingdom Start Page, click Manage SQL Server Express Projects.
2. Kingdom Data Managementa project management application with a wide range of
project inventory and management tools. Kingdom Data Management requires a separate
license.
Warning: The Manual SQL Server Express Management tool manages only the SQL Server
Express database and the files in the Kingdom project folder. By default, Kingdom
files are saved in the project folder, but if files such as seismic data, author folders,
or raster logs have been saved in locations outside of the project folder, these files
will not be included in the action.
Before using Manual SQL Server Express Management to manage your project,
move all external files into the Kingdom project folder.
Kingdom 8.8
19
Managing your Manual SQL Server Express Projects
20
Kingdom 8.8
SQL Server Express Service

Configuration
What is your Working Environment?
One of the following configuration options are required for the Auto SQL Server Express
configuration and highly recommended for the Manual configuration:
Local
Projects
Kingdom projects are on your workstation or on a colleagues

workstation.
Users
You are a single user or have a small work group.
SQL Server Service
Install SQL Server Express on the same computer as the

Kingdom projects. Accept Local as the configuration. Click OK
in the SQL Server Express Service Configuration dialog box to
exit.
Other users in a work group or network that have permissions to access this computer will
also be able to work in the Kingdom projects.
Kingdom 8.8
21
Network
Projects
Kingdom projects are on a shared resource on the network.
Users
The Kingdom projects and SQL Server Express instance may be

on different machines. Multiple users may connect to the same
SQL Server Express instance.
SQL Server Express

Service
Install SQL Server Express on a network computer - not on your

workstation.
This configuration requires a Network ProjectNetwork
Database Instance solution.
You will need to get service credentials from your domain administrator before continuing.
See Unable to start the service for troubleshooting tips if you get an error message after trying
to start the service with the entered log on credentials.
Network ProjectNetwork Database Instance

You are in a network environment when your project and your SQL Server Express
(SMTKINGDOM) instance are both on your network - not on your workstation. This
configuration supports multiple projects on multiple computers connecting to a central SQL
Server Express instance.
See What is your Working Environment? for local and network criteria.
Your network administrator will need to do the following:
1. Create user (service account)
2. Add the Log on as a service right to the user account
3. Grant the service account Full Control privileges to Kingdom project directories
4. Add the service account user to the computer where the SQL Server Express instance is
installed and add to Administrator Group
5. Set the service account as the Log On account for the SQL Server (SMTKINGDOM)
service
Create user (service account)

Prerequisites:
22
Kingdom 8.8
Microsoft Administrative Tool Pack is installed on a machine in the domain or you have
access to the domain controller.
You have a domain administrator account or service account with permissions to create
users and modify the default domain policy to create the service account.
Create the user (service account)

1. On a Windows Domain Controller, open Administrative Tools and click Computer
Management.
2. Expand Your Domain.
3. Right click Users and select New User
4. Enter the user account information and click Next.
5. Enter a password and confirm the password.
6. Select Password never expires.
7. Click Create and then Close.
Add the Log on as a service right to the user account

1. On a Windows Domain Controller, open Administrative Tools and select Domain
Security Policy.
2. In the console tree, expand Local Policies and then User Rights Assignment.
3. In the details pane, double-click Log on as a service.
4. If this security setting has not yet been defined, select the Define these policy settings
check box.
5. Click Add User or Group and then add the user (service) account you created.
Grant the service account Full Control privileges to Kingdom

project directories
Add the service account to the group(s) that have Full Control access to the Kingdom project
directoriesorshare the Kingdom project directories to the user account and give Full
Control access. For the second option, see How do I share my project directories?
Add the service account to the group(s) that have Full Control access
1. On the Windows Domain Controller, select Start > Programs > Administrative Tools >
Active Directory Users and Computers.
2. Click Groups to display existing groups.
3. Right click the selected group and select Add to Group.
Kingdom 8.8
23
4. Click Add.
5. Make sure Service Accounts is displayed under Select this object type and that your
Domain is displayed under From this location.
6. Enter the name of the service account that you created and click Check Names.
7. When the account is returned, select OK and OK again.
Add the service account user to the computer where the SQL Server
Express instance is installed and add to Administrator Group
This step can be done by the domain administrator remotely or by any user that is an
administrator on the computer where SQL Server Express is installed.
Tip:
You can use the same service account for other instances of SQL Server Express.
1. Administrator Tools > Computer Management

2. Expand Local Users and Groups.
3. Right click on Users and select New User
4. Enter the user name and password, and select Password never expires.
5. Click Create. The next step is to add this user to the Administrators Group.
6. Select Groups and open Administrators.
7. In Administrator Properties click Add.
8. In Select Users, Computers, Service Accounts, or Groups:
a. Check that the Location is the computer, not the domain.
b. Enter the service account user name and click OK.
9. If successful, you will return to Administrators Properties. The service account user name
and password should be listed. Click OK.
Set the service account as the Log On account for the SQL Server
(SMTKINGDOM) service
Note: This step can be done by the SQL Server Express Service Configuration tool installed
with the instance. The user installing the instance will only need the user name and
password of the service account.
You must be a local administrator on the computer to set the Log On account.
24
Kingdom 8.8
1. Log in to the network computer where SQL Server Express is installed.

2. Select Control Panel > Administrative Tools > Services
3. Right click the SQL Server (SMTKINGDOM) service and select Properties.
4. Select the Log On tab.
5. Select This account and click Browse.
6. In Select User, click Locations.
7. Expand Entire Directory and select the company domain (network) name. Click OK.
8. In Select User or Service Account enter the created service Active Directory user name
or display name and click Check Names. The service account should appear in the object
name box.
9. Click OK to return to the Log On tab.
10. Enter and confirm the service account domain password and click OK.
11. Click Yes in the 2 messages and OK again in the Log On tab.
12. You will need to restart the service. In the Services list, right click the SQL Server
(SMTKINGDOM) service and select Restart.
The SQL Server (SMTKINGDOM) service will now be able to access the database files
located in the Kingdom project folders.
The Kingdom project directories must be shared to the SQL Server (SMTKINGDOM) service
Log On account (service account).The Log On account must have Full Control permissions to
the project directories.
How do I share my project directories?

You must share your project folder on your computer to the Log On account for the SQL
Server (SMTKINGDOM) service and give this account Full Control permissions.
1. Contact your network administrator and request the name of the service account that was
created for the SQL Server (SMTKINGDOM) service.
2. Share your project folder to this service account and give it Full Control permissions.
a. Right click the project folder on your computer and select Properties.
b. Select the Sharing tab and click Share.
c. Enter the service account name and click Add. If a matching domain account is found,
the domain\service account name will appear in the list.
d. Under Permission level, click the down arrow and select Full Control. Click Share.
Your folder is now shared to the service account. Click Done to exit.
Kingdom 8.8
25
Windows Domain Controller

On Windows Server Systems, a domain controller (DC) is a server that responds to security
authentication requests (logging in, checking permissions, etc) within the Windows Server
domain. Windows 2000 and later versions introduced Active Directory.
26
Kingdom 8.8

There are a number of reasons why the service is unable to start. Microsoft returns 24 possible
reasons. However, the following are the most common:
Table 1
The user password is not
valid
Re-enter the password in the Server Configuration dialog box

and retry.
The user has not been

granted local logon as a
service rights
If prompted that the user will be added to the local logon as a

service group, click OK.
The domain user is not a

member of a Group that has
logon as a service rights.
Contact your domain administrator. See Network Project

Network Database Instance for detailed steps.
The user is not in the

Administrator group on the
local machine
Add the service account user to the computer where the SQL
Server Express instance is installed and add to Administrator
Group
The user logged in to the

computer is not a local
administrator
You must be a member of the Administrator group on the

computer. Contact your domain administrator for assistance.
Kingdom 8.8
27
28
Kingdom 8.8
Manual SQL Server Express (SSE)

Management
Manage your Manual SSE Projects
Warning: The SQL Server Express Management tool manages only the SQL Server Express
database and the files in the Kingdom project folder. By default, Kingdom files are
saved in the project folder, but if files such as seismic data, author folders, or raster
logs have been saved in locations outside of the project folder, these files will not
be included in the action.
Before using SQL Server Express Management to manage your project, move
all external files into the Kingdom project folder.
Note: If your projects have the auto portability configuration, you do not need to use this tool
unless you want to open your project with Kingdom 8.6 or earlier - or if you want to
convert your project from Auto SSE back to Manual SSE.
Changing an Auto SSE Project back to Manual SSE
Note: Use the Manual SSE Management tool to accomplish the following.
Make a Project PortableSend or take your Manual SSE project to a computer not on
your network (home or to a colleague). You have two choices:
-
Make the Original Project Portablemakes the project itself portable until restored.
Select the first option, Detach project database. The project database is moved into
the project directory in its original location. The project is inactive in this portable
form. You can then transfer the portable project to an external storage device and
Attach Portable Project in the new location.
Make a Portable Copy of the Projectkeeps the original project active and makes a
portable copy of the entire project in a new folder. Select the second option, Copy
entire project. The portable project is inactive in this portable form.
Attach Portable ProjectMake your portable project active in the new location to
begin work. You have two choices:
Kingdom 8.8
29
Attach the Project Database Onlyattaches the project database to the specified
instance and makes the Kingdom project active in its current location.
Attach the Database and Copy the Project Filescopies the portable project file to the
specified location and then attaches the project database to the specified instance.
Make an Active CopyCopy the project to a location on your computer or network.

The new project will have its own database identical to the database in the original project.
Create a BackupMake a project copy to store. A copy of the project is packaged into a
portable folder to a location you specify. The original project remains active. You can
Restore a Backup as required.
Restore a BackupMake your project backup active and begin work.
Move Project Files OnlyRelocate the Kingdom project files without moving the
database. The moved project will remain active.
Delete an Entire Project Delete the database and project files of your Manual SQL
Server Express projects.
Tip:
All operations follows a Basic SSE Management Workflow.
Basic SSE Management Workflow

SQL Server Express Management is available from the Kingdom Start Page.
1. Launch Kingdom 32-bit or 64-bit.
2. Under Tools on the Kingdom Start Page click Manage Manual SQL Server Express
Projects.
Note: You can also launch the Manual SSE Management tool from DBAdmin.
Select Start > Programs > The Kingdom Software 8.7.1 > DbAdmin
Select Database > SQL Server Express Management
30
Kingdom 8.8
3. Select the option. See Manage your Manual SSE Projects for a definition of each option or
click the link below for detailed instructions:
Make a Project Portable
Attach Portable Project
Make an Active Copy
Create a Backup
Restore a Backup
Move Project Files Only
Delete an Entire Project
4.
Complete the Option Source / Destination / Instance Information

The option you select will determine the required source project, destination location, and
SQL Server Express instance information.
5. Determine if you want to use Validation mode for added data security.
Kingdom 8.8
31
Validation mode
Validation is a file by file comparison of the destination project with the source project.
This comparison is done after the selected action of the project database and project files
has been successfully completed. All validation issues detected during the selected
process will be listed in the Summary Report. Validation mode is not available for
database only operations (detach and attach database only) or for delete entire project.
Note: Validation mode will substantially increase the time required to complete the process
6. When the selected process is finished, review the Summary Report.
Make a Project Portable

This option creates a portable, inactive project in a single folder. Use Make a Project
Portable if you want to take the project to a different physical location, or if you want to
attach the project to a database on a computer not connected to your network.
You have two choices when making your project portable:
-
Make the Original Project Portablemakes the project itself portable until restored.
Select the first option, Detach project database. The project database is moved into
the project directory in its original location. The project is inactive in this portable
form. You can then transfer the portable project to an external storage device and
Attach Portable Project in the new location.
Make a Portable Copy of the Projectkeeps the original project active and makes a
portable copy of the entire project in a new folder. Select the second option, Copy
entire project. The portable project is inactive in this portable form.
Make the Original Project Portable

This option makes the project itself portable until restored. The project database is moved into
the project directory. The entire project will be portable and inactive until attached to a
SMTKINGDOM instance of SSE.
2. Under Tools on the Kingdom Start Page click Manage SQL Server Express Projects.
32
Kingdom 8.8
3. Select Make Project Portable and Detach project database.

4. Select the source project file (.TKS). Click Browse and navigate to the <project
name>.tks file of the project you want to send or move.
Note: You do not have a destination option as the project will packaged in its current
location. The contents of the database will be included in the project folder.
5. Click Start to begin the process. A status bar will display the progress.
The project is packaged in its current location into a folder called <project
For example, for a project named BEG made portable on September 8, 2008 at 1:13 pm,
the now portable project folder will be
Note the following files inside the portable project folder:
Kingdom 8.8
33
Table 1 Portable project files

<project name>.xml
original database pointer file to the SMTKINGDOM SSE

instance
<project name>.tks.bak
the inactive Kingdom project file
<project name>_1.bak
the portable database file. Duplicate database file names will

be appended with a sequential number: _2, _3, _4 etc.
databaseinfo.xml
information on the original location of the project database

file. the default location is
C:\Program Files
(x86)\KingdomSuite\SMTKINGDOM_DATA\MSSQL.1\MS
SQL\Data
7. Now using Windows, copy the portable project folder to an external storage device to
transport to the specified location.
Note: The destination computer must also have the SMTKINGDOM instance of SQL Server
Express installed before you can make the portable project active with Attach Portable
Project. SQL Server Express is available on the Kingdom Software DVD.
8. On the destination machine, use Windows to copy the portable project folder to the project
folder location.
9. Launch Kingdom and click Manage SQL Server Express Projects on the Start Page.
10. Now select Attach Portable Project to return the portable project to its original, active
state.
Make a Portable Copy of the Project

This option keeps the original project active and makes a portable copy of the entire project in
a new folder. The entire project will be portable and inactive until attached to a
SMTKINGDOM instance of SSE.
34
Kingdom 8.8
3. Select Make Project Portable and Copy entire project.

name>.tks file of the project for which you want to make a portable copy.
5. Select a portable project destination. Click Browse and navigate to the location where
you want to save the portable copy of the selected project.
6. Select a Validation mode.
The portable copy is saved to the specified location in a folder called <project
Kingdom 8.8
35
For example, for a project named BEG made portable on September 8, 2008 at 1:13 pm,
the now portable project folder will be
Note the following files inside the portable project folder:

Table 1 Portable project files
<project name>.xml
original database pointer file to the SMTKINGDOM SSE

instance
<project name>.tks.bak
the inactive Kingdom project file
<project name>_1.bak
the portable database file
databaseinfo.xml
information on the original location of the project database

file. the default location is
C:\Program Files
(x86)\KingdomSuite\SMTKINGDOM_DATA\MSSQL.1\MS
SQL\Data
9. Now using Windows, copy the portable project folder to a storage device to transport to
the external location.
Express installed before you can make the portable project active with Attach Portable
Project. SQL Server Express is available on the Kingdom Software DVD.
10. On the destination machine, use Windows to copy the portable project folder to the project
folder location.
11. Launch the SQL Server Express Management Tool through DBAdmin.
12. Now select Attach Portable Project to return the portable project to its original, active
state.
36
Kingdom 8.8
Attach Portable Project

This option makes a portable project active. Use Attach a Portable Project if you want to
make the project active on a computer not connected to your network.
Express installed before you can make the portable project active. SQL Server Express
is available on the Kingdom Software DVD.
You have two choices when making your portable project active:
-
Attach the Project Database Onlyattaches the project database to the specified
instance and makes the Kingdom project active in its current location. The portable
project folder is renamed to its original name, and the database pointer file (<project
name>.xml) is updated with the new SSE SMTKINGDOM instance information.
Attach the Database and Copy the Project Filescopies the portable project file to the
specified location and then attaches the project database to the specified instance. The
copied portable project folder is renamed to its original name, and the database pointer
file (<project name>.xml) is updated with the new SSE SMTKINGDOM instance
information. The original portable project remains intact in the source location.
Attach the Project Database Only

This option attaches the project database to the specified SMTKINGDOM instance of SSE
and makes the Kingdom project active in its current location.
Kingdom 8.8
37
3. Select Attach Portable Project and Attach project database only.

4. Select the portable project file (.BAK). Click Browse and navigate to the <project
name>.tks.bak file in the portable project folder: <project name>_portable_<date
yyyymmdd>_<time>.
Note: You do not have a destination option for the project as the project will be activated and
attached to the database in its current location.
5. Select a SQL Server Express instance. Click the down arrow and select the
SMTKINDOM instance from the list. SMTKINGDOM instances are named
<computer_name>\SMTKINGDOM. If the instance you want is not on the list, enter the
information in the box.
38
Kingdom 8.8
Kingdom 8.8
39
Attach the Database and Copy the Project Files

This option copies the portable project file to the specified location and then attaches the
project database to the specified instance. The copied portable project folder is renamed to its
original name, and the database pointer file (<project name>.xml) is updated with the new
SSE SMTKINDOM instance information. The original portable project remains intact in the
source location.
3. Select Attach Portable Project and Attach project database only.

name>.tks.bak file in the portable project folder: <project name>_portable_<date
yyyymmdd>_<time>.
40
Kingdom 8.8
5. Select a project destination. Click Browse and navigate to the destination location for
the active project.
When the attach is complete, the active project folder will be renamed to its original name
and the portable project folder will remain intact in its original location. The project is
connected to the specified SMTKINGDOM SQL Server Express instance and is ready for
production.
Kingdom 8.8
41
Make an Active Copy

Use Make an Active Copy to make an active copy of both the project and the database to a
location on your computer or network. The new project will have its own database identical to
the database in the original project. Note that the project and the database can reside on
different computers.
3. Select Make and Active Copy.

name>.tks file of the SQL Express Kingdom project you want to copy. Click Open.
42
Kingdom 8.8
5. Select a project destination. Click Browse and navigate to the project file location on the
network or your computer. Click OK.
Note: To Make an Active Copy both the Permissions and Security settings must be set to
Full Control for Everyone in the destination folder. If you get an error message, see
Windows File Sharing and Permissions for instructions on how to check or change
these settings.
Note: The SSE instance must have the SMTKINGDOM configuration.
Kingdom 8.8
43
Create a Backup
Use Backup to make a non-active copy of the project for storage. The backup project folder
will include both the project files and a .BAK file of the database. The original project
remains active.
3. Select Create a Backup.

name>.tks file of the SQL Express Kingdom project you want to back up. Click Open.
5. Select a project destination. Click Browse and navigate to the location for the backup
project file on the network or your computer. Click OK.
44
Kingdom 8.8

When the process is finished, the Summary Report will display project details.
The project.tks file will be appended with a .bak file extension. The backup project folder
name will be <project name>_Backup_<date yyyymmdd>_<time>.
For example, for a project named Golden_sse backed up on July 9, 2008 at 2:26 pm, the
backup project folder will be
Kingdom 8.8
45
Restore a Backup
Use Restore a Backup to convert a project backup to an active state. This Restore tool will
only work on backups created by the SQL Server Express Management tool.
3. Click Restore a Backup.

name>.tks.bak file in the backup project folder: <project name>_Backup_<date
yyyymmdd>_<time>.
5. Select a restore destination. Click Browse and navigate to the destination location for the
restored project.
46
Kingdom 8.8
Note: To Restore a Backup both the Permissions and Security settings must be set to Full
Control for Everyone in the destination folder. If you get an error message, see
Windows File Sharing and Permissions for instructions on how to check or change
these settings.
When the restore is complete, the active project folder will be renamed to its original name
and the backup project folder will remain intact in its original location. The project is
connected to the specified SMTKINGDOM SQL Server Express instance and is ready for
production.
Kingdom 8.8
47
Move Project Files Only

Use Move to relocate the Kingdom project files without moving the database. The moved
project will remain active and will link to the original SQL Server Express database.
3. Select Move Project Files Only.

4. Select the source project file (.TKS) click Browse and navigate to the <project
name>.tks file of the SQL Server Express Kingdom source project that you want to move.
5. Select a project destinationclick Browse and navigate to the destination location on
your computer on network.
48
Kingdom 8.8

8. When the process is finished, the Summary Report will display source and destination
details.
Note: In some instances, the application is unable to delete one or more of the files in the
source folder. In this case, you will be prompted to use Windows to delete the
remaining SOURCE files. Deleting these source files will not affect the moved project
files.
Kingdom 8.8
49
Delete an Entire Project

The Delete option deletes the entire project, both the project files and the database. The Delete
command is irreversible, so delete with caution.
3. Select Delete an Entire Project.

4. Select the source project file to delete (.TKS). Click Browse and navigate to the
<project name>.tks file of the SQL Express Kingdom project to be deleted.
5. Click Start to begin the process.
50
Kingdom 8.8
6. In the warning message, click Yes if you are certain that you want to permanently delete
the project files and project database. A status bar will display the progress.
Warning: Often projects will have shared or linked seismic files. Before deleting the project,
ensure that there are no shared or linked files.
Summary Report
Once the SQL Express Management action has been successfully completed, the Summary
Report dialog box opens as in the figure below:
The Summary Report displays the following details about the Source project and the
Destination project:
Project name
Project location
Database type
Database name
Note: If you selected Validation mode for the SQL Express Management action, and there
were validation issues, the issues will be listed in an additional panel.
Kingdom 8.8
51
Troubleshooting SQL Express Management
Troubleshooting SQL Express

Management
If the SQL Management tool cannot successfully complete the selected operation, the
Prerequisite Issues or Warning Messages will open listing the missing or failed prerequisite,
and details on how to fix the problem.
Prerequisite Issues
To successfully complete the SQL Server Express Management action, you will need to fix
the required prerequisite issues to continue.
The following tables lists the messages given and possible solutions.:
Message
Operation Canceled. The project is currently in use.
Solution
Contact the active author(s) and have them exit the project.
Message
There was a problem connecting to the SQL Server Express Instance. Please
verify that the server is running.
Solution
Start the SQL Server (SMTKINGDOM) service. Select Start > Settings >
Administrative Tools > SQL Server (SMTKINGDOM). In the Status
column, right click and select Start.
52
Kingdom 8.8
Message
This utility only supports the SMTKINGDOM SQL Server Express instance.
Solution
In the project folder, open the <project name>.xml file and check the database
instance. An SMTKINGDOMSQL Server Express instance will read as
follows:
<Connect_85>COMPUTER_NAME\SMTKINGDOM</Connect_85>.
The application did not detect \SMTKINGDOM as part of the instance name.
Message
The source project is not using the SMTKINGDOM instance of SQL Server
Express for its database.
Solution
Check that the project has been migrated to the SMTKINGDOM instance of
SSE from the Kingdom Software and retry.
1. Install The SMTKINGDOM instance of SQL Express from the web
download or from the SMTKingdom Software 8.6 DVD.
2. Launch Kingdom 8.6 and click Migrate Access Project on the Start Page.
3. Repeat the option using the SQL Server Express Management tool.
Message
The source project database cannot be found.
Solution
The database has been deleted, moved, or modified.
Message
The application has detected that here is not sufficient disk space available on
the destination directory. (Required space <>GB, available space <>GB). If
you know that there is sufficient disk space, you can ignore this warning and
continue.
Solution
The SQL Management tool queries the Windows operating system for
available disk space. If you are running on a mixed platform, then the query
may not pick up available space on other operating systems such as Unix or
Linux. If you are sure there is enough space in the destination location, ignore
the message and continue with the operation.
Kingdom 8.8
53
Message
The destination SQL Server Express instance is remote from the portable
project. Do one of the following:
Move the source portable project folder to the SQL Server Express
instance machine OR
Share the source project folder to Everyone, and grant Everyone read
permissions.
Solution
See Windows File Sharing and Permissions for instructions on how to set
sharing and permissions.
Message
The SQL Express server on <destination computer name> is not running or

does not have the required SMTKINGDOM instance.
Solution
The SMTKINGDOM instance of SQL Express must be installed from the

from the web download or from the SMTKingdom Software 8.6 DVD.
Message
The portable project has been corrupted. Restore cannot continue.
Solution
Necessary files or folders have been deleted, moved, or modified. The portable
project is no longer complete and valid.
Message
Unable to Delete Source Folder.

All files have been successfully copied to the destination folder. The source
files are no longer required. However, the application is unable to delete one or
more of the files in the source folder. Please use Windows to delete remaining
SOURCE files.
Solution
In some circumstances, after a Move, you may get this error message. You can
safely follow the directions in the message and delete the remaining source
files. The moved project files will not be affected.
Message
Operation Complete with Issues.
54
Kingdom 8.8
Solution
Message
In some circumstances, after you make a project or project database portable,

you may get this error message. Kingdom was unable to delete the source
database, and/or was unable to rename the portable project folder. You can
safely follow the directions in the message.
Permission and share messages:

Your destination directory is not network shared.
You do not have adequate permissions on the source (destination) directory.
You don not have full access rights on the source directory.
The application encountered a problem while testing the database backup
process. Verify that share permissions are set correctly.
The application encountered a problem while testing the creation of the
destination directory. You may not have adequate permissions.
Solution
See Windows File Sharing and Permissions for any of the error messages
above.
Warning Messages
Certain problems will evoke a warning message.
Figure 1 Problem with the Operation
Some of the warning messages contain:
Kingdom 8.8
a details button. Click for additional information about the problem.
55
a convenient Copy to Clipboard option. Click to copy the additional

information and send to Kingdoms technical support team for analysis.
If you require further instructions on how to fix any of the detected problems, refer to the
white paper SQL Server Express Troubleshooting Guide through My Account on the
Kingdom web page, or contact Kingdoms technical support team at 713-935-7900.
56
Kingdom 8.8
Windows File Sharing and Permissions

If you receive an error message regarding permissions, the first step is to make sure that
simple sharing on your computer has been disabled. For brief instructions, see the next section
Disable Simple File Sharing or Microsoft Help Topics.
In most cases, you only need Read/Write permissions specific to your user account, either
directly on a folder, if working locally, or on a network share if referencing a remote location.
In some cases, you must create a network share that has Read/Write permissions granted to
the Everyone group. In a few select cases with the copy operation, you must create a
network share that has Full Control permission granted to the Everyone group.
In all cases, the program will advise you of the specific permission and share requirements for
your specific case. For brief instructions, see the next section Changing Share and Permission
Settings on Destination Folder or Microsoft Help Topics.
Note: You may need to restart your computer for the changes in the sharing and permissions
to take effect.
Disable Simple File Sharing

By default, simple file sharing is enabled on a Microsoft Windows XP-based computer if the
computer is not a member of a domain. If simple file sharing is enabled, you see the simple
file sharing user interface instead of the Security and Sharing tabs. To disable simple file
sharing, follow these steps:
1. Click Start > My Computer (or double click the My Computer icon on your desktop).
2. On the Tools menu, click Folder Options, and then click the View tab.
3. In the Advanced Settings section, scroll down to the bottom and clear the Use simple file
sharing (Recommended) check box.
4. Click OK.
Kingdom 8.8
57
Changing Share and Permission Settings on Destination

Folder
To successfully copy or restore a SQL Express project using the SQL Express Management
tool, you may be required to have full access rights on the shared source or destination folder
which includes Sharing Permissions to Full Control, and adding specific users or Everyone
on the Security tab and allowing full permissions. See Windows Access Privilege Matrix for
information on possible scenarios requiring a change in share and permission settings.
1. Navigate to the source or destination folder.
2. Right-click the folder and select Sharing and Security to open to the Sharing tab of the
<folder name> Properties dialog box as in the figure below.
3. On the Sharing tab, select Share this folder.

4. Click Permissions to open the Share Permissions dialog box. The default is Read only
for Everyone as in the figure below.
58
Kingdom 8.8
5. You can click Add and add your Windows user name to allow Full Control to you only, or
you can check Full Control to allow Full Control for Everyone.
6. After specifying the user name, and checking Full Control, select Apply as in the figure
below
Kingdom 8.8
59
7. Click OK in the Share Permissions tab to return to the Sharing tab.

8. Click Apply and OK in the Sharing tab to exit.
9. Now select the Security tab in the <folder name> Properties dialog box.
10. Click Add to open the Select Users, Computers, or Groups dialog box.
11. Enter the specific users name, or type Everyone and click Check Names.
60
Kingdom 8.8
If the entered user name is found in the selected Location, then the object name will
become underlined.
12. Click OK to return to the Security tab and check Full Control as Permissions for
Everyone or for the user name entered as in the figure below:
13. Click Apply and OK to exit.

You now have full access rights on the shared source or destination folder.
Note: You may need to restart your computer for the changes in the sharing and permissions
to take effect.
Kingdom 8.8
61
Windows Access Privilege Matrix

SMTKINGDOM
Instance
TKS
Project
Local
Local
SQL Service
Account
NT
Authority\Network
Service
Local User Account
Domain User
Account
Requirements
1. User Read/Write access to SSE backup
directory.
2. User Read/Write access to TKS project
directory.
3. Sufficient free disk space in SSE backup
directory for temporary database backup. The
file will be removed after being copied to the
project directory.
4. Sufficient free disk space in project directory for
database backup file.
Local
Remote
NT
Authority\Network
Service
Local User Account
Domain User
Account
1. User Read/Write access to SSE backup

directory.
2. User Read/Write access to TKS project directory
via a network share or mapped drive.
3. Sufficient free disk space in SSE backup
directory for temporary database backup. The
file will be removed after being copied to the
project directory.
Remote
Remote
62
Local
Remote
NT
Authority\Network
Service
1. Everyone Read/Write access to TKS project

directory via a network share.
NT
Authority\Network
Service
1. Everyone Read/Write access to TKS project

directory via a network share.


Kingdom 8.8
Remote
Local
Local User Account

Domain User
Account
Remote
Remote
Local User Account

Domain User
Account
1. [Everyone or SQL Service Account] Read/

Write access to TKS project directory via a
network share.
2. User Read/Write access to TKS project.
1. [Everyone or SQL Service Account] Read/
Write access to TKS project directory via a
network share.
2. User Read/Write access to TKS project directory
via a network share.
Kingdom 8.8
63
64
Kingdom 8.8
Microsoft SQL Server as the

Project Database
SQL Server Overview
Kingdom can utilize a Microsoft SQL Server database for storage of project data. Two SQL
Server configurations are available:
SQL Server (Single)creates a project specific database. With this configuration, each
project will have its own database in the selected SQL Server instance.
SQL Server (Multiple)adds the project to an existing database that may contain multiple
Kingdom projects. The tables for each project have a unique number as a prepend to the table
name.
In both cases, the SQL Server database administrator will need to add login users to the SQL
Server instance and, in the multiple case, the administrator will need to create a database for
the Kingdom projects.
This section includes the following:
Installing and Configuring a SQL Server Database
In a network environment, multiple workstations can access the SQL Server database. The
required SQL Server client components on each Kingdom workstation are installed during the
Kingdom Software installation.
Kingdom is compatible with SQL Server 2005 and 2008.
Note: The intent of this document is not to replace any documentation provided by the
Microsoft Corporation, but is provided only as an aid to the Kingdom user working in
a project that accesses a Microsoft SQL Server Database.
Kingdom 8.8
65
Installing and Configuring a SQL

Server Database
The following steps are required to install and configure a Microsoft SQL Server database.
1. Install Microsoft SQL Server Software
2. Verify the SQL Server Database is Running
3. Connect to the SQL Server Management Studio
4. Create SQL Server Databases and Logins
5. Set SQL Server Network Configuration
After you have installed and configured the SQL Server database, you can Create a Project
using the Microsoft SQL Server Database
Install Microsoft SQL Server Software

Follow the Microsoft SQL Server installation wizard to install Microsoft SQL Server. with the
exception of the Database Engine Configuration setting, Kingdom does not require any
specific changes from the defaults nor does it require that the server run on any particular
version of Microsoft Windows. SQL Server Help can provide details during installation.
In the Feature Selection, you must install the Database Engine Services and the
Management Tools.
Kingdom does require that you specify Mixed Mode in the Database Engine Configuration
dialog box during installation.
Note: If you are installing SQL Server 2005, the Mixed Mode setting is specified in the
Authentication Mode dialog box.
66
Kingdom 8.8
You must select both the Database Engine

Services and the Management Tools. Other
features are optional.
Kingdom requires Mixed Mode Account Provisioning. With SQL

Server 2008 you must also specify a SQL Server administrator.
Note: The sa password will not be required by the Kingdom users as you will create a
different username and password for each database to hold a Kingdom project.
After installation, ensure that the SQL Server Management Studio (Management Tools) is
installed on the server machine. Select Start > Programs > Microsoft SQL Server [version].
You should see SQL Server Management Studio listed in your installed programs.
The SQL Server Management Studio does not have to be installed on each workstation. It
only needs to be installed on the machine with the SQL Server database.
In a network environment, multiple workstations can access the SQL Server database. The
required SQL Server client components on each Kingdom workstation are installed during the
Kingdom Software installation.
Verify the SQL Server Database is Running

Assuming the installation completed successfully, verify the Microsoft SQL Server database
is running.
Kingdom 8.8
67
1. In the Control Panel, select Administrative Tools > Services.

2. In the right panel, scroll down to the SQL Server service and check that the status of the
following services is Started.
SQL Server (Instance Name)
SQL Server Browser
3. If either is not started, complete the following steps:

a. Right click on the name and select Properties.
b. Select Startup type as Automatic and click Apply.
c. Select Service status > Start and click Apply.
d. Click OK to exit.
Connect to the SQL Server Management Studio

1. Open the Microsoft SQL Server Management Studio. From your desktop select Start >
Programs > Microsoft SQL Server [version] > SQL Server Management Studio.
2. In the Connect to the Server dialog box, select the server name and Windows
Authentication. Windows Authentication is granted to logins with administrative
privileges. No additional login information will be required.
3. Click Connect to open the SQL Server Management Studio.
68
Kingdom 8.8
Note: You can also login using SQL Server Authentication. Enter sa as the Login and the
password you created during the installation process.
4. Click Connect to open the SQL Server Management Studio.

You are now ready to create and configure the SQL Server database for Kingdom.
Create SQL Server Databases and Logins

When you create or migrate a Kingdom project to SQL Server, you have the following
options:
SQL Server (Single)creates a project specific database. With this configuration, each
project will have its own database in the selected SQL Server instance.
SQL Server (Multiple)adds the project to an existing database that may contain multiple
Kingdom projects. The tables for each project have a unique number as a prepend to the table
name.
In both cases, the SQL Server database administrator will need to add login users to the SQL
Server instance and, in the multiple case, the administrator will need to create a database for
the Kingdom projects.
Create a SQL Server Database for Multiple Kingdom Projects
Create SQL Server Logins
Kingdom 8.8
69
Create a SQL Server Database for Multiple Kingdom

Projects
The SQL Server (Multiple) option creates a single database for multiple Kingdom projects.
After you create the database, you will need to create the Login and assign this database as the
default.
1. Connect to the SQL Server Management Studio with a login that has sysadmin rights.
2. Create the database.
a. Right-click Databases in the left panel and select New Database.
b. In the New Database dialog box, enter a database name.
c. Accept Default Settings for Database Size and Autogrowth
d. Accept the default Initial Size of 2 MB and the Autogrowth of 1 MB with unrestricted
growth unless advised otherwise.
e. Cick OK to accept the settings and create the database.
f. You should now see the new database listed in the right panel of the SQL Server
Management Studio.
3. Finally, verify that SQL Server is configured to automatically restart after a reboot (or
power failure).
a. Under Microsoft Windows, open Control Panel > Services or Control Panel >
Administrative Tools > Services and look for an entry like MSSQLServer.
b. If the status column is not Started, then start it manually. If you select Startup Type
as Automatic, then Microsoft SQL Server will be started every time the computer is
rebooted.
4. Create the Login(s) and assign this new database as the default. See Create SQL Server
Logins.
Create SQL Server Logins

These instructions create a login with a sysadmin server role. Login accounts with this profile
will be able to access and create all Kingdom projects on the selected instance and upgrade
existing Kingdom projects to a higher version of the Kingdom software. Authentication
method can be Windows or SQL Server.
Note: SQL Server has numerous levels of server roles to define more granular levels of
access. Your database administrator may assign more restrictive server roles than
sysadmin as per your corporate policy.
70
Kingdom 8.8
Connect to the SQL Server Management Studio with a login that has sysadmin rights. Then
create a new Login account.
1. Expand the main Security node in the tree and right click on Logins.
2. Select New Login to open the LoginNew dialog box.
3. Select authentication type:
Windowssearch for or enter the domain login name. You could also enter an Active
Directory Group.
SQL Serverenter a login name/password and password policy information. Users

will need to enter this information when opening or creating a project.
4. Default database:
-
For the SQL Server (Single) option, accept master as the default database.
For the SQL Server (Multiple) option, change the default database to the database you
created for the multiple Kingdom projects.
5. Under Select a page in the upper left, select Server Roles.

6. In addition to public, select sysadmin.
7. Click OK to finish.
For other Windows users to access this project, the database administrator must add the other
users or groups as new logins. Repeat steps 1-7 above for each user or group.These users will
now be able to open and work in Kingdom project(s) in this SQL Server instance.
Authentication will come from active directory.
If the authentication type is SQL Server, additional users will need the entered user name and
password.
Note: If the user login does not have a sysadmin User Role, User Mapping and a change
from master as the default database to the selected database will be required. See
Microsoft documentation for more information.
When the user creates or migrates a Kingdom project using the single option, a database
named <projectname>_1 will be created in the selected instance.
When the user creates or migrates a Kingdom project using the multiple option, the project
tables will be added to the assigned database. All project tables will be prepended with a
unique identification number.
Kingdom 8.8
71
Set SQL Server Network Configuration

If the SQL Server instance you are configuring is on a network, the TCP/IP protocols on the
remote database instance and on your local (client) machine must be enabled. If the SQL
Server instance is on your machine, this is not an issue.
Enable TCP/IP Protocol on Server

On the computer where SQL Server is installed, open the SQL Server Configuration Manager
and Enable the TCP/IP protocol:
2. Under SQL Server 2005 Network Configuration, select Protocols for <INSTANCE
NAME>.
panel.
b. In the right panel right click SQL Server (INSTANCE_NAME) and select Restart.
72
Kingdom 8.8
Enable TCP/IP Protocol on Client

Return to the Kingdom workstation and Enable the TCP/IP Client Protocol using the same
procedure:
Create a Project using the Microsoft SQL

Server Database
Project > Create New Project
Before you can create a Kingdom project, you must Create SQL Server Databases and Logins.
When you create a Kingdom project, the database schema will be automatically created.
1. Open Kingdom and choose Project > Create New Project or click the Create Project link
from the Kingdom Software Start Page.
2. In the Create New Project dialog box, navigate to the location where you want the
Kingdom project folder to reside, name the project and click Create.
3. Enter an author name for the project and click OK.
Note: Kingdom does not create a folder for the first author of a new project. All
interpretations for the first author are saved in the main project folder.
When creating a new project, make the first author an upper-level non-interpreter such
as company/group name. The creating author should not be a working author. Then
each new user can create an author name, which creates a subfolder in the project main
folder.
Each authors interpretations will be saved in his or her subfolder.
4. In the Select Project Database select a SQL Server option:
SQL Server (Single)creates a project specific database. With this configuration,

each project will have its own database in the selected SQL Server instance.
Kingdom 8.8
73
SQL Server (Multiple)adds the project to an existing database that may contain
multiple Kingdom projects. The tables for each project have a unique number as a
prepend to the table name.
For both options, Logins can be created using Windows authentication or SQL Server
authentication.
Figure 3 Enter SQL Server Login Credentials
5. In the Microsoft SQL Server Configuration dialog box, enter the required information and
click OK.
SQL Server Connectthe host name of the machine running Microsoft SQL Server.
AuthenticationWindows or SQL Server. Only SQL Server authentication will

require a user name and password.
6. When you create a project in the designated SQL Server database, you will be asked if you
would like to create the T_PROJECT Table. You will only get a message with the first
project that the T_PROJECT Table is missing. Click Yes to create one and continue.
Note: Depending upon the speed of your Microsoft SQL Server database server and the
bandwidth of your network this process can take anywhere from a few seconds to
several minutes to create all the new tables and data.
When the project is ready, the Project Options dialog box opens.
7. Enter the required data and click OK to proceed.
74
Kingdom 8.8
Note: Click the Help button for information on the current dialog box.
8. The final step before your project is created is to specify the coordinate system of the new
project.
Click Yes and navigate to an existing project with the same coordinate system as the
project you are creating.
or
Click No to create the project with an undefined XY Projection Method. Once the project
opens, select Project > XY Projection Method and set your projection method.
With the creation of your first project, your SQL Server database is now ready to store your
Kingdom projects.
Kingdom 8.8
75
Connecting to your SQL Server

Database
The following section gives troubleshooting tips for a database migration to SQL Server.
These tips also apply to problems opening an existing SQL Server Kingdom project.
Note: You must know the SQL Server instance name, and your login credentials (user name
and password) before you can migrate your project database to SQL Server.
My SQL Server instance is not listedwhen creating a project, you cannot see your SQL
Server instance in the list of available instances.
Error occurred connecting to the databasea general error message when trying to create or
open a SQL Server project. This error could be caused by a number of reasons.
Troubleshooting tips are provided.
My SQL Server instance is not listed

Before troubleshooting, try typing the instance name into the SQL Server Connect field.
Enter your user name and password and click OK to continue.
If you get An error occurred connecting to the database. Would you like to try again?,
Click No. See Error occurred connecting to the database for troubleshooting tips.
Error occurred connecting to the database

Problem 1: One of the SQL Server services is not running.
Solution 1: Open the Administrative Tools on the computer where SQl Server Express is
installed and start the service(s):
1. Click Start > Settings > Control Panel > Performance and Maintenance >
Administrative Tools > Services.
2. Scroll down to locate the SQL Server services. Check that SQL Server (SMTKINGDOM)
and the SQL Server Browser are Started.
3. To start a service, right click beside the service in the Status column and select Start.
4. Now open the Access Kingdom project with Kingdom 64-bit and try the project migration
again.
76
Kingdom 8.8
Problem 2: One of the TCP/IP protocols is not enabled.

If the SQL Server instance you are migrating to is not local (on your computer), the TCP/
IP protocols on the remote database instance and on your local (client) machine must be
enabled. If the SQL Server instance is on your machine, this is not an issue.
Solution 2A: On the computer where SQL Server is installed, open the SQL Server
Configuration Manager and Enable the TCP/IP protocol:
2. Under SQL Server 2005 Network Configuration, select Protocols for <INSTANCE
NAME>.
panel.
b. In the right panel right click SQL Server (INSTANCE_NAME) and select Restart.
Solution 2B: Now return to the Kingdom workstation and Enable the TCP/IP Client Protocol
using the same procedure:
Kingdom 8.8
77

4. After you have completed parts A and B of the solution, open the Access Kingdom project
with Kingdom 64-bit and try the project migration again.
78
Kingdom 8.8

Oracle Overview
Kingdom can utilize an Oracle database for storage of project data. This chapter explains only
the Oracle configuration pertaining to the Kingdom software which includes the following:
Configuring the Oracle Hoston the Windows, Solaris, or Linux machine designated as
the server.
Installing and Configuring the Oracle Clienton each interpreters workstation.
The section concludes with Connecting to your Oracle Databasea troubleshooting guide.
Oracle version 10g is used in this chapter for the example. The information provided in this
section is primarily for the Database Administrator (DBA) at your company. The client needs
to contact the DBA for the username and the Oracle instance.
Note: The intent of this document is not to replace any documentation provided by the
Oracle Corporation, but is provided only as an aid to the Kingdom user working in a
project that accesses an Oracle Database.
Kingdom 8.7 has been certified on Oracle 10g and 11g.
Note: Kingdom 32-bit requires the Oracle 32-bit client and Kingdom 64-bit requires the
Oracle 64-bit client.
If you are running Kingdom 32-bit on a 64-bit OS, you will need both clients installed
on your workstation.
Kingdom 8.8
79
Configuring the Oracle Host

Once the Oracle Host has been installed on a Linux, Solaris, or Windows system, the database
administrator needs to create the tablespace, user, and password for each Kingdom project.
Note: It is highly recommended that a tablespace and user be created for each Kingdom
project.
Create Required Tablespaces and Tables
Create Oracle Users for Kingdom Projects
Create Required Tablespaces and Tables

After a successful login to the Oracle Host database using the system username and
password information, the system database administrator (SYSDBA) can now create a
tablespace for each Kingdom project. Although not a requirement, we recommend that a
separate tablespace be created for each project.
After you create your tablespace(s) you will create a login account for each tablespace.
The following workflow is using Oracle 10g.
1. Through the web interface on Oracle 10g, log in using the SYSDBA username and
password.
80
Kingdom 8.8
In our example, the Oracle instance created during the install was TRAINING.
After a successful login to the Oracle Enterprise Manager, you are ready to configure the
database for your Kingdom projects.
2. In the Oracle Enterprise Manager, select the Administration tab.
Figure 5 Select Tablespaces in Oracle Enterprise Manager
Kingdom 8.8
81
3. Under Storage, select Tablespaces and click
. on the far right.
4. In the name box, type the Tablespace name. In our example, the name of the tablespace is
the name of the Kingdom project: SOONER.
Figure 6 Name Tablespace in Oracle Enterprise Manager
5. In the same window, scroll down to Datafiles and click Add on the far right.
82
Kingdom 8.8
6. In the Add Datafile window, enter a File Name for the datafile.
Figure 7 Name Datafile for Tablespace
7. In the File Directory box, search
and select your file location or accept the default.
8. Enter a File Size for your Tablespace. Consult your database administrator for file size
requirements.
Note: Your Tablespace file size and Auto-Extend number will depend on the size of your
Kingdom projects. For large projects we recommend the following:
Tablespace file size = 10 to 15 GB
Auto-Extend = 500 MB to 1 GB
9. In the same window under Storage, check Automatically extend datafile when full.
Figure 8 Set Storage Autoextend Limits
Kingdom 8.8
83
10. Set the Increment to 100 MB (or any specified value) and accept the Unlimited
Maximum File Size.
11. Click Continue to complete the process of creating the tablespace.
12. Return to the Administration tab to create the Oracle users for Kingdom. In the Create
Tablespace dialog box, click the Database Instance: <Name> link at the top of the page.
Create Oracle Users for Kingdom Projects

Oracle has several methods for authenticating users. In our example Oracle will use its own
separate list of users and their credentials.
Assuming Oracle is maintaining the user accounts, create a user account that will be allowed
to create new tables and read or change data in the Oracle database.
Each tablespace should have a single Oracle user. Multiple Kingdom authors can log in to the
project with the same Oracle user.
1. On the Administration tab of the Oracle Enterprise Manager, scroll down to Users &
Privileges under Schema and click the Users link.
84
Kingdom 8.8
2. In the Users dialog box, click
on the far right.
3. In the Create Users dialog box:

a. Type a user name in the Name field. In our example, the user name is the same as the
Kingdom project name (which is the same as the tablespace name): sooner.
b. Type a password in the Enter Password field, and re-enter in the Confirm Password
field.
c. Click the
beside the Default Tablespace, select your tablespace from the list and
click Select.
d. Click the
beside the Temporary Tablespace field, select TEMP or an alternate
temporary tablespace from the list and click Select.
Kingdom 8.8
85
Note: Use the same user name and password that you will use later when Kingdom creates a
new project in the Oracle database.
4. Now assign Roles and Privileges to the User.
a. In the Create User dialog box, click the Roles tab and ensure that the Default box (far
right) is checked.
b. Next, click the System Privileges tab and click Edit List.
86
Kingdom 8.8
c. In the Modify System Privileges dialog box, use the scroll bar to locate, select and
move the following Available System Privileges to the Selected System Privileges
box:
CREATE TABLE
CREATE SESSION
CREATE VIEW
UNLIMITED TABLESPACE
d. Once the system privileges have been selected, click OK to return to the Create User
dialog box. The selected System Privileges will be displayed.
Kingdom 8.8
87
e. Click OK to return to the Users dialog box.

5. Repeat this process for each Kingdom project.
Once the Oracle tablespace and user account has been created, the Oracle client must be
installed and configured on each users computer.
88
Kingdom 8.8
Installing and Configuring the Oracle

Client
The Oracle client is installed and configured on your workstation computer and includes the
following steps:
Install the Oracle Client
Create Oracle Service Name on Oracle Client
Set Oracle as the Kingdom Project Database
If you do not see your Oracle Service Name on the list, see Connecting to your Oracle
Database.
Install the Oracle Client

When the Oracle database server is properly configured and running, the Oracle client
software must be installed on each interpreters Microsoft Windows computer.
There are 32-bit and 64-bit versions of the Oracle client.
Kingdom 32-bit requires the Oracle 32-bit client
Kingdom 64-bit requires the Oracle 64-bit client.
Note: If you are running Kingdom 32-bit on a 64-bit OS, you will need both clients installed
In addition, if you are converting an Access Kingdom project to Oracle using the
database migration tool in the 64-bit version of Kingdom, you will need both Oracle
clients installed on your workstation.
This Oracle software may be installed before or after the Kingdom software, but both must be
installed for everything to work properly. Use the Oracle Universal Installer (OUI) to install
the client software.
Install the Oracle Client from the Oracle CD-ROM on the PC running Kingdom.
Note: The Kingdom Software is not certified on Oracle Express.
1. Launch the Oracle client installer.
2. In the Oracle Universal Installer Welcome page click Next.
Kingdom 8.8
89
Installing and Configuring the Oracle Client
3. The Select Installation Type window appears. Click Administrator to install the
management console which will allow you to Configure the service names using the Net
Configuration Assistant unless directed otherwise by your network administrator.
4. In the Specify Home Details window accept the default or Browse to specify a location.
Click Next.
5. The Product-Specific Prerequisite Checks window appears verifying that your
environment has met all the installation and configuration requirements. The Status field
should state Succeeded. Click Next.
6. The Summary window will appear which displays all of your new installations you are
about to install and available space remaining. Click Install.
Installation may take several minutes.
7. In the End of Installation window click Exit.
Create Oracle Service Name on Oracle Client

After installing the Oracle client, there is one more step to configuring the PC. You need to
create an Oracle Service Name to connect to or create Kingdom projects in the Oracle
database.
The information you need for the Oracle server name are: the host, service name, and port
number. These were provided for the database during the server install. The utility TNSPING
can verify if the settings are correct.
Oracle uses a service name as an alias for the Oracle server machine and oracle instance. The
service name is similar to ODBC Datasource Names in Microsoft windows.
Oracle provides a wizard to create these service names called Net Configuration Assistant.
Remaining steps:
1. Configure the service names using the Net Configuration Assistant
2. Set Oracle as the Kingdom Project Database.
Note: You can also manually add entries to the file tnsnames.ora located in the oracle
directory on the client machine. The default location is on your C drive:
C:\oracle\product\10.2.0\client_1\NETWORK\ADMIN
Configure the service names using the Net Configuration

Assistant
1. Launch the Net Configuration Assistant from the Start menu:
90
Kingdom 8.8
All Programs > Oracle - OraClient10g_home1 > Configuration and Migration Tools > Net
Configuration Assistant
Note: The Net Configuration Assistant also opens automatically after installation of the
Oracle client.
2. On the Welcome page, select Local Net Service Name Configuration and click Next to
add the net service name to the tnsnames.ora file.
Note: To complete Net Service Configuration, you will need the host, service name, and port
number of the Oracle server. These were provided for the database during the server
install.
3. Select Add and Next to continue through the wizard entering the information about the
Oracle server:
a. Service Nameis the name of the Oracle database, not the computer name. Enter the
service name and click Next.
b. TCP Protocolis the standard Ethernet protocol used for client/database server
conversation over a network. Select TCP and click Next.
c. Host nameis the name of the computer where the host Oracle database is located.
Enter the host name.
d. Port numberaccept the standard port number or select Use another port number
(as provided for the database during the server install) and click Next.
Kingdom 8.8
91
e. to test that a connection can be made to the database.

4. In the next section of the wizard, test that a connection can be made to the database.
a. Select Yes, perform a test in the Net Service Name configuration, Test dialog box.
Click Next.
b. In the Connecting dialog box click Change Login (see figure below).
Figure 9 Change Login to Connect to the Oracle Database
c. In the Change Login dialog box, enter the Oracle user name and password established
in the Create Oracle Users for Kingdom Projects process (sooner/sooner) and click
OK.
d. If the test was successful, the following message will appear:
Figure 10 Connection Test to Oracle Database Successful
92
Kingdom 8.8
5. Click Next to continue.

6. Accept the default Net Service Name and click Next.
7. Would you like to configure another net service name? Click No and Next to complete
the net service name configuration.
8. Click Next and Finish in the final dialog box of the Wizard.
You should now be able to create your Kingdom project and Set Oracle as the Kingdom
Project Database. Alternatively, you can now convert an Access or SQL Server project to
Oracle. For project conversions see Kingdom Project Database Conversions.
Set Oracle as the Kingdom Project Database

To convert your existing project database to Oracle see Kingdom Project Database
Conversions.
Create a project in Kingdom using the Oracle database server to store project data.
1. Open Kingdom and choose the Project > Create New Project.
2. Create New Projectselect a location and enter a name for your Kingdom project and
click Create.
3. Select Project Database Typeselect the Oracle and click OK.
Kingdom 8.8
93
Note: If you are running Kingdom 64-bit, only the MS SQL Server and Oracle databases will
be available.
4. Enter User Name and Password in the Oracle Configuration dialog box (see the figure
below):
Project Path location of the Kingdom project.
Oracle Service Name the name you configured above using the Oracle Net
Configuration Asst.
UserName / Password must match the Oracle login credentials. See Create Oracle
Users for Kingdom Projects.
In our example, the Oracle Service Name is TRAINING. The User Name is sooner (the
name of the Kingdom project).
5. Please confirmclick OK to confirm creation of the new tables in the database.This

process may take several minutes.
When the project is ready, you will see the normal Project Options dialog box.
You will be required to enter the user name and password each time you open the
Kingdom project.
Note: If you do not see your Oracle Service Name in the list, see Connecting to your Oracle
Database for troubleshooting tips.
94
Kingdom 8.8

The following section gives troubleshooting tips for a database migration to Oracle. These tips
also apply to problems opening an existing Oracle Kingdom project.
Cannot Connect Error when Migrating (Converting) to Oracle or when

Creating an Oracle Project
Kingdom requires Oracle users to have CREATE VIEW System Privileges. Your Oracle
DBA may need to add this privilege for each Oracle user before you can open or create
Kingdom projects with Oracle. See Create Oracle Users for Kingdom Projects.
You must know the Oracle instance name, and your login credentials (user name and
password) before you can migrate your project database to Oracle. Contact your database
administrator.
Kingdom 32-bit requires the Oracle 32-bit client and Kingdom 64-bit requires the Oracle
64-bit client. Both clients can be installed on the workstation which will allow both
versions of Kingdom to connect to Kingdom Oracle projects.
Note: If you are running Kingdom 32-bit on a 64-bit OS, you will need both clients installed
In addition, if you are converting an Access Kingdom project to Oracle using the
database migration tool in the 64-bit version of Kingdom, you will need both Oracle
clients installed on your workstation.
Windows XP and Kingdom 32-bit users: Some versions of Oracle do not work with
applications installed in directories that contain parentheses. If you are using Oracle as
your Kingdom project database and you have installed Kingdom 32-bit on a Windows XP
64-bit operating system, the default installation directory has parentheses in the path:
C:\Program Files (x86)\KingdomSuite. You will need to do one of the following:
-
Uninstall Kingdom 32-bit and reinstall to a folder without parentheses (e.g.

C:\KingdomSuite).
Install a version of Oracle that does work with parentheses or install patch 5059238 for
Oracle client 10.2.0 32-bit.
Note: This is no longer a problem with Windows 7.
Kingdom 8.8
95
Cannot see my Oracle Instance in List
. If you cannot see your Oracle instance in the drop down list, the most common reason is
that you need to create the Oracle service name on your workstation using the Net
Configuration Assistant.
The Net Configuration Assistant creates the tnsnames file which contains the service
name, host, and port information. This file is in the Oracle home directory:
C:\oracle\product\10.2.0\client_64\NETWORK\ADMIN
Check network connectivity. If you recently moved the Oracle database server computer
or if you moved your workstation on the network, the Oracle database server and the
Windows PC may not be able to see each other on the network anymore.
-
96
You can verify your Windows PC can communicate with the Oracle database server by
opening a command prompt on the Windows PC and typing ping OraTestServer.
Where OraTestServer is the host machine and where Oracle is running.
Ensure the Oracle server computer is on and that Oracle is running. Contact your database
administrator.
Kingdom 8.8
Kingdom Project Backups

Overview
This section includes the following topics:
What do I Backup?the Kingdom project includes 4 components. For a full backup, you
must include all components.
Backing up Kingdom Project Databasesa brief overview of backup procedures for SQL
Server, Oracle, and SQL Server Express databases.
Make a Single Project Manual Backup with DBAdminsteps for backing up a Kingdom
project with a SQL Server or Oracle database using Kingdoms Database Admin tool.
Note: For Manual SQL Server Express project backups see

Manual SQL Server Express (SSE) Management.
Restore a Kingdom Project with DBAdminsteps for restoring a Kingdom project

backup using Kingdoms Database Admin tool.
Automating SQL Server and SQL Server Express Backupssteps for automating
multiple project backups.
Kingdom 8.8
97
What do I Backup?
What do I Backup?
Every Kingdom project has four parts:
The project files by default, project files are saved in the project folder. For a
description of file types see The Kingdom Project Architecture.
The project databaseAccess databases and Auto SQL Server Express databases reside
inside the project folder. Oracle and SQL Server databases (including Manual SQL Server
Express databases) are external to the project folder. See Backing up Kingdom Project
Databases.
External data files some files can be stored outside of the project folder. If files such as
seismic data, author folders, or raster logs have been saved in locations outside of the
project folder, these files will not be backed up unless they are copied or moved into the
project folder. However, also note that external files that do not change often such as
seismic files can be backed up separately. See The Kingdom Project Architecture.
Custom color bar files stored in the <Kingdom installation directory>\Colorbars folder.
Custom color bars can be saved individually or placed in the same zip file.
Note: Do not save the colorbars that ship with the product. Save only colorbars you have
created or modified. Although user-customized color bars can be saved anywhere, by
default they are stored in Kingdom installation Colorbars directory.
98
Kingdom 8.8
Backing up Kingdom Project Databases
Backing up Kingdom Project

Databases
Microsoft Access Projects
For MS Access-based projects, most well data and pointer files reside in the <project
name>70.mdb in the project directory. The <project name>70.mdb database file can be
backed up in the same file as the rest of the project.
Oracle or SQL Server projects
Additional backup procedures are recommended if Oracle or SQL Server is the selected
database. In the event that all projects are stored in one Oracle database, all projects would be
rolled back if it became necessary to roll back the database. However, this creates the
possibility that the Oracle backups and the project folder backups could get out of sync if they
are not coordinated. If this were to happen, the result would be either orphaned database
records, or orphaned project files.
To keep the project file data and database data synchronized, you can use the Database Admin
tool to backup individual Oracle or SQL Server Kingdom projects.
First Make a Single Project Manual Backup with DBAdmin
Then Restore a Kingdom Project with DBAdmin
It is, however, a recommended practice to create a unique Oracle account or SQL Server
database to accommodate each Kingdom project. In that way, most standard external database
backup-restore procedures will treat each Kingdom project independently, and not rollback
multiple projects to restore a single project.
Auto SQL Server Express Kingdom Projects
The database for Auto SQL Server Express projects are in the project folder. Both the
database tables and project files can be backed up by making a copy of the project folder.
Manual SQL Server Express Kingdom Projects
For Manual SQL Server Express projects use the SQL Server Express Management tool in the
Database Admin utility. This tool will backup both database tables and project files into one
file.
You can access the tool from the Kingdom Start Page.
Under Tools, click Manage your Manual SSE Projects.
Kingdom 8.8
99
Backing up Kingdom Project Databases
Related Topic
Automating SQL Server and SQL Server Express Backups
100
Kingdom 8.8
Make a Single Project Manual Backup with DBAdmin
Make a Single Project Manual Backup

with DBAdmin
Start > Programs >The Kingdom Software > Dbadmin
1. To open DbAdmin from your desktop, select Start > Programs > The Kingdom
Software > DbAdmin [version].
Note: The version of DbAdmin, both the bit version and release version, must match the
version of Kingdom the project was last opened in.
2. In the Database Admin Tool window, select Database > Connect.
3. In the Select a Project Manager dialog box, select the database type of the current project
and click OK.
Note: For Access projects, the database <project name>70.mdb file is located in the project
folder and has a size limit of 2 GB. To back up an Access project, you do not need to
use DBAdmin. Simply copy the project folder to the backup location. Be sure to
include any files that may reside outside of the project folder.
However, if space in the backup location is limited, you can create a backup using the
DBAdmin tool as enumerated below. The Access project backup without the original
database will be smaller than the original project.
4. For Oracle and SQL Server databases, enter the login credentials and click Next.
For SQL Server Express or Access projects, navigate to the <project name>.tks file of
the project you wish to back up and select.
Kingdom 8.8
101
5. When you are connected to the project database in DBAdmin, click the project that is to be
backed up.
Figure 11 Select Project to be Cloned in DbAdmin
6. With the project highlighted, select Project > Export to File.

7. In the Save In text box navigate to the project folder. (This is the default location.)
8. In the Save As dialog box, edit the name for the file. The default name is export.dmp. The
default save location is the Kingdom project directory.
Note: Database Admin Tool dump files are not equivalent to Oracle database dump files.
They are ASCII xml files unique to Kingdom.
9. Click No in the NULL out message to complete the export.
10. When the export process is complete, exit the Database Admin tool.
The project folder now contains a dump of the project database and can be saved in the
designated backup location.
102
Kingdom 8.8
Warning: Certain files may reside outside the project folder: seismic files, raster logs, author
folders, and culture files. For a complete backup, ensure that these external files
are in the project folder, or that their respective folders are also backed up.
Note: If your original project was Access, the backup folder will contain both the dump of
the database (export.dmp), and the original Access database (<project name>70.mdb).
If the size of the backup folder is an issue, you can remove the original access database
to an external location as the contents are contained in the export.dmp file.
Kingdom 8.8
103
Restore a Kingdom Project with DBAdmin
Restore a Kingdom Project with

DBAdmin
If you have created a project backup of your Kingdom project with the Database Admin tool,
you can restore the project with the same tool.
You will:
1. Create a New Twin Project in the Target Database
2. Import the Database Dump into the Twin Projects Database.
Note: To restore SQL Server Express projects, use the SQL Server Express Management
tool. On the Kingdom Start Page click Manage your Manual SSE Projects.
Create a New Twin Project in the Target Database

The purpose of this step is to create the database tables in the Access, SQL Server or Oracle
database.
1. In Kingdom, select Project > Create New Project.
2. Navigate to the Kingdom project backup folder. Create the new project inside the existing
project folder.
3. In the Create New Project dialog box, type the name of the project to be restored. This
name must be identical to the original name. After typing in the project name click
Create.
4. Click Yes in the warning message.
5. In the Author Name dialog box, enter an author and click OK.
6. In the Select Project Database, select Access, Oracle or SQL Server and click OK.
7. For SQL Server and Oracle, input the instance and login credentials and click OK.
8. A message may be displayed about creating the new tables: click OK. The twin project is
created, as are the project tables in the designated database.
-
104
For Access projects, the <project name>70.mdb file is created in the twin project
folder.
Kingdom 8.8
For Oracle and SQL Server projects, the project tables are created in the designated
Oracle or SQL Server instance, and the <project name>.xml file is created in the twin
project folder.
Note: The <project name>.xml file is the pointer file to the SQL Server or Oracle database.
This file contains the instance, username, password, and windows login information.
Access projects do not have an .xml file.
After the project tables are created, the Project Options dialog box opens.
9. Enter the same project options as the original project and click OK.
10. Click No to Do you want to use the coordinate system of an existing project? This
information is already recorded in the dumped database in the backup, and will be
retrieved once the project is converted.
11. Exit the Kingdom application.
12. Navigate to the twin project folder which is located within the original project folder.
-
For Access projects, copy the <project name>70.mdb file up one level into the
original project directory.
For SQL Server and Oracle projects, copy the <project name>.xml file up one level
into the original project directory.
The project database is now ready to be populated by the export.dmp file. For SQL Server and
Oracle projects, the <project name>.xml file is now in the project folder to point to the
database.
Import the Database Dump into the Twin Projects Database

Start > Programs > The Kingdom Software [version] > DBAdmin
1. Run the DBAdmin tool again. From your desktop, select Start > Programs > The
Kingdom Software [version] > DBAdmin.
2. Select Database > Connect.
3. Select the Project Manager for the project (database type).
4. For SQL Server or Oracle, input the Service Name, User Name, and Password then click
OK.
For SQL Server Express and Access projects, browse to the tks file in the project folder
and click OK.
For Oracle or SQL Server, you may see more than one project in the left panel. Select the
new project that you just created from the project tree.
Kingdom 8.8
105
For Access and SQL Server Express projects there will be only one project in the left
panel.
Figure 12 Select New Project in Database through DbAdmin
Note: With some Oracle and SQL Server database configurations there may be multiple
Kingdom projects in the same database, with each project identified by a unique
prepend number. An easy to find a project in DBADMIN is to search by the projects
GUID number. The GUID can be found in the <project name>.xml file in the project
directory, and entered (including the enclosing brackets) in the window after clicking
Project > Find Project by GUID in DBADMIN.
5. Select Project > Import From File and click Yes to import the export.dmp file from the
project backup folder.
6. Click Yes in the replace project warning.
7. Navigate to the export.dmp file in the project backup folder, and click Open to begin the
import.
An import status dialog will be displayed.
The time needed to import will depend on the project size. The dbAdmin.exe main
window may not be displayed throughout the entire import process but will be displayed
again when the import is completed.
8. When the import is complete, exit the DBAdmin tool.
The project should be restored to an active state.
106
Kingdom 8.8
Check the Status of the Restored Project

1. Open Kingdom and open the restored project.
2. Enter the database Service Name, User Name, and Password and click OK.
3. Select an Author and click OK. You are now running the restored project.
4. You can now delete the twin project folder in the project directory.
Kingdom 8.8
107
Automating SQL Server and SQL

Server Express Backups
The following are instructions on how to schedule automatic backups of your SQL Server and
SQL Server Express databases using a script constructed with the SQL Server user interface.
This procedure can be configured in and launched automatically by the SQL Server Agent
tool. The Agent tool is not available in SQL Express, although the scripts are just as
effectivethey simply must be launched manually at the time of backup.
The steps include:
Creating the Backup Script
Scheduling the Backup with SQL Server Agent
Creating the Backup Script

1. Launch the Microsoft SQL Server Management Studio (or Management Studio Express)
tool.
Note: The SQL Server Management Studio Express tool can be downloaded from the
Microsoft download Center. Click the link below and scroll to the bottom of the page:
Download Microsoft SQL Server Management Studio Express
2. Connect to the SQL Server or SQL Server Express database instance.
3. Expand the Databases node and right click the database to be backed up.
4. Select Tasks > Back Up (see figure below).
Figure 13 Starting the Backup
108
Kingdom 8.8
5. In the Backup Up Database dialog box, specify the following:
Backup set name (or accept the default)
Backup set will expirespecify the number of days that must elapse before this
backup set expires and can be overwritten. The default is 0 which means that the
backup set will never expire.
Destinationbackup location (see figure below). Accept the default or browse to the
selected location a local drive on the SQL database serve.
Figure 14 Selecting backup parameters
Kingdom 8.8
109
Note: The backup file location must be a local drive on the database server. If necessary, the
files can be moved later. SQL Server and SQL Express both require you to use only
local drives as the location to: 1) install the software, 2) store database files and 3) save
database backup files. SAN drives also qualify as local drives.
Note: If you accepted the default location, do not click OK yet.

6. In the Back Up Database dialog box you can click OK to carry out an immediate backup
of the Kingdom project database, or you can save the backup instructions to a file for later
execution.
110
Kingdom 8.8
To save the backup instructions to a file, click the down-arrow next to the Script button
and select Script Action to File (figure below).
Figure 15 Saving Backup Instructions
7. Select a location to save the structured query language (.sql) file and enter a File name:
Kingdom_Projects_Auto_Backups. (No default file name is provided).
8. Open the resulting file for edit. Right click the file and select Edit. The file will open in
Notepad.
Note: Double-clicking the file will launch an actual backup job.
9. To add additional databases to this script file in order to back up all databases, you can do
one of two things:
a. Repeat the above steps and select Script Action to Clipboard instead of Script Action
to File. Then paste (Ctrl+V) the backup instruction string into the .sql text file that is
open (figure below), or
b. Repeatedly copy and paste the initial line of instructions and edit the database name on
each line to match the remaining database names. There are three occurrences to edit
on each line of instructions.
Figure 16 Results of Pasting New Backup Instruction into .sql File
Kingdom 8.8
111
10. Save the final edited .sql backup script when completed.
11. When it is time to make a backup of your project databases, simply double-click the *.sql
backup script file, and the SQL Server Studio Management (or Management Express) tool
will open with the backup scripted steps ready to execute.
12. Click Execute in the Management Studio (figure below). The backups will be written to
the designated location: <database name>.bak.
Figure 17 Executing the Backup Script Manually
112
Kingdom 8.8
13. Copy the backup files out of the destination folder to a permanent location so they are not
overwritten later.
Scheduling the Backup with SQL Server Agent

If you are using the full-featured SQL Server instead of SQL Server Express you will see SQL
Server Agent as one object in the operations tree on the Studio Management interface.
1. Expand the SQL Server Agent tool, right-click Jobs and select New Job (figure below).
Figure 18 Creating a Backup Job
Kingdom 8.8
113
2. On the New Job dialog box, assign a job name and category (figure below).
Figure 19 Describing the Backup Job
114
Kingdom 8.8
3. Next, Select Steps under Select a page, and add the steps you previously scripted.
a. Click New at the bottom of the New Job dialog box.
b. Insert the steps contained in the .sql backup script you previously built. Click Open in
the New Job Step window (see figure below).
Figure 20 Preparing to Open the .sql Script to Insert Job Steps
Kingdom 8.8
115
c. Navigate to the location of the .sql script you built and click Open (see figure below).
Figure 21 Navigating to the .sql Script
116
Kingdom 8.8
The backup script steps contained in the .sql file will now appear as steps in your
scheduled backup job.
d. Enter a Step name and click OK (see figure below).
Figure 22 Backup Steps Now as Part of the Job
Kingdom 8.8
117
4. Now, under Select a page click Schedules on the Job Properties window and click the
New button to open the New Job Schedule window.
5. Select a backup time or frequency and start date and end date for your job, then click OK
to approve the scheduled job (see figure below).
Figure 23 Creating a Daily Backup Schedule
118
Kingdom 8.8
6. Add any other desire alerts or notifications and click OK to complete the scheduling.
7. Check the destination folder location of the backups after a scheduled job to assure that
backups are being properly executed.
8. Copy backups to a new location to prevent over-writing of backups if a longer history is
required. You can script this copy job to a .bat batch file and place it in the Windows
scheduler to make your job easier.
Summary
Kingdom database backups can be automated with the help of either SQL Server Management
Studio Express (downloaded from the Microsoft Download Center) or with SQL Server
Management Studio, purchased as part of full-featured SQL Server:
Kingdom 8.8
119
The sql script that is created with SQL Server Management Studio Express must be
executed manually.
The same sql script is used by SQL Servers Agent to schedule the backups for automated
after-hours execution.
120
Kingdom 8.8
Kingdom Project Database

Conversions
Overview
Kingdom offers the user a choice the following databases: SQL Server SQL Server Express,
Oracle, and Access.
Kingdom 32-bit supports Microsoft Access as a database. Kingdom 64-bit does not. If your
projects are currently in Access but you would like to run Kingdom 64-bit, a database upgrade
to SQL Server Express, SQL Server, or Oracle is required.
You can convert your Kingdom project databases by the following methods:
Migrate Access Database to SQL Server Expressopen your Access project with
Kingdom 32-bit or 64-bit. You will be given the option to migrate (convert) your Access
database to SQL Server Express.
Migrate Access Database to SQL Server or Oracleopen your Access project with
Kingdom 32-bit or 64-bit. You will be given the option to migrate (convert) your Access
database to SQL Server or Oracle.
Convert Your SQL Server Express Project Back to Accessuse the Database Admin tool
for this database conversion.
Convert SQL Server or Oracle Database to Access with DBAdmin
Convert SQL Server Database to Oracle (or vice versa) with DBAdmin
Kingdom Data Managementa project and data management application with database
conversion, data transfer and other project and data management capabilities. Kingdom
Data Management requires a separate license.
Note: When using the Database Admin Tool to manage your Kingdom projects (export/
import database, delete), make sure that the Kingdom project is in the same version of
Kingdom as the DBAdmin tool.
For example, if you are launching DBAdmin from Kingdom 8.7, any projects being
managed should also be in Kingdom 8.7. If necessary, upgrade the project to the
version of DBAdmin before using the tool on that project.
Kingdom 8.8
121
Migrate Access Database to SQL Server or Oracle
Migrate Access Database to SQL

Server or Oracle
Note: For troubleshooting tips see An Error Occurred Connecting to the Database.
When you open a Kingdom project with an Access database, you will be prompted to migrate
your project to SQL Server, SQL Server Express, or Oracle.
You can also open the Access Database Migration tool from the Kingdom Start Page.
Click the Migrate Access Project link under Tools and browse to the *.tks file of the Access
project:
If you are running the 32-bit version of Kingdom, you will be prompted to migrate your
project, but the database migration is optional.
If you are running the 64-bit version of Kingdom, you must migrate the project before you can
open it.
You must have the SQL Server or Oracle client installed on your computer. The SQL Server
client is installed with Kingdom. For Oracle client installation and configuration see Installing
and Configuring the Oracle Client.
See also Choosing a Database for a brief discussion of your options.
You must also know the database configuration information: database (instance) name, user
name, and password.
1. From the Kingdom Software Start Page select Project > Open Project.
2. Browse to the Access project.tks file and click Open.
The Migrate Project Database dialog box will open as in the figure above.
3. Select Microsoft SQL Server or Oracle and click Migrate. The Access database
contents will be imported into the specified database instance.
122
Kingdom 8.8
Figure 24 Oracle Configuration
4. Click the down arrow and select the SQL Server or Oracle instance.
5. Click OK to import the project into the Oracle or SQL Server database and complete the
migration.
The Select Author dialog box opens, and your project is ready to go.
Note: The Kingdom project folder remains in the same location with the same name. The
Access database is renamed and the <project name>.xml file is created. This .xml file
is the pointer to the project database.
Kingdom 8.8
123
Convert Your SQL Server Express Project Back to Access
Convert Your SQL Server Express

Project Back to Access
Note: Before beginning the conversion process, we recommend that you back up the original
project which includes the Kingdom project folder and the external database.
Backup your SQL Server Express projects with the SQL Server Express (SSE)
Management tool available from the Kingdom Start Page.
If you are a Kingdom 64-bit user, you have migrated your Kingdom project database to SQL
Server Express, you can convert it back to MS Access using either Kingdom Data
Management 32-bit or the Database Admin Tool included with your base feature of the
Kingdom software.
Once you have converted your project database back to Access, you will not be able to use
Kingdom 64-bit for this project as Microsoft does not support Access in a 64-bit application.
Instead, launch the 32-bit version of Kingdom and open the project.
Kingdom Data Managementis a project management application with a wide range of
project inventory and management tools which allows you to see and interact with the
contents of all your Kingdom projects simultaneously, making day to day project management
tasks such as converting databases infinitely easier. Kingdom Data Management requires a
separate license.
Database Admin Toolis included with the base Kingdom license. You will need to have
the 32-bit version of Kingdom installed to convert the database from SQL Server Express to
MS Access.
Note: MS Access has a database size limit of 2 GB. You will not be able to make the
conversion back to Access if the database is larger than 2GB.
For example, if you are launching DBAdmin from Kingdom 8.7.1, any projects being
managed should also be in Kingdom 8.7.1. If necessary, upgrade the project to the
Using the Database Admin Tool and Windows Explorer, the project conversion back to
Access involves the following steps:
124
Kingdom 8.8
Step 1: Create a Database Dump of the Original Project:

Step 2: Import the Database Dump File into the Target Access Database
Step 3: Check the Status of the Converted Project
Create a Database Dump of the Original Project

Start > Programs > The Kingdom Software (32-bit) > DbAdmin (32-bit)
1. Open the Database Admin Tool in the 32-bit version. From your desktop select Start >
Programs > The Kingdom Software (32-bit) > DbAdmin (32-bit).
2. In the Database Admin tool, select Database > Connect to open the Project Manager
dialog box.
3. Select Kingdoms SQL Server Express.
Note: If Microsoft Access is not displayed, you have launched DBAdmin (64-bit).
4. In the <Database Type> Configuration dialog box, select a SQL Server Express
instance: CompName\SMTKINGDOM.
Click OK and navigate to the <project name>.tks file in the project folder.
Once you have connected to your project in DBAdmin, the project path and name will
appear under Projects in the left panel as in the figure below.
Kingdom 8.8
125
Figure 25 Connect to your SSE Project in DBAdmin
5. In the Database Admin tool, select your project in the left panel and export the project
database as a *.dmp file to the project folder.
a. With the project path highlighted, select Project > Export to File.
126
Kingdom 8.8
The Export command creates an export.dmp file of the database contents.

6. Add the date to the dump file name: export<date>.dmp. The default save location is the
project directory for the original project.
7. Click No in the NULL out message to complete the export. DBAdmin will complete the
database export to the specified location, or the default location of the project folder.
Import the Database Dump File into the Original

Access Database
The next step is to import the *dmp file into your Access database. However, when you
upgraded your database from Access to SQL Server Express, the Access database, or <project
name>.mdb file was renamed to <project name>70sav.mdb.
1. Before you can import your SQL Server Express .dmp data into the Access database, you
must rename the <project name>70sav.mdb file in Windows Explorer.
Kingdom 8.8
127
a. In Windows Explorer, navigate to the project folder and locate the renamed Access
database file, or <project name>70sav.mdb.
b. Right click the <project name>70sav.mdb file, select Rename. Remove the sav from
the file name. The Database Admin Tool will now be able to connect to the Access
database.
2. In the Kingdom Software 32-bit Database Admin Tool, connect to the projects renamed
Access database.
a. In the Database Admin Tool main window, select Database > Connect and select
Microsoft Access as your database. Click OK.
Note: Only the 32-bit version of the Database Admin Tool will have the Access databases as
choices.
b. In the Open dialog box, navigate to the project folder, select the <project name>.tks
file and click OK. The project path and name will appear in the left panel of the
DBAdmin window.
3. Import the *.dmp file into the project. This will replace the old Access contents.
a. In the left panel, highlight the project.
b. In the Database Admin Tool main menu, select Project > Import from File.
c. In the warning box, click Yes to replace this project with the import data.
d. In the Windows Open dialog box, navigate to the export.dmp file in the project folder
and click Open.
The contents of the SQL Server Express database will replace the original contents of the
Access database.
Check the Status of the Converted Project

1. Now rename the <project name>.xml file.
a. In Windows Explorer, navigate to the project folder and locate the <project
name>.xml file. Right click the <project name>.xml file, select Rename and modify
the original name.
2. Now find the <project name>.tks file and double click to open the project in Access.
Check the status of the converted project.
Your project database is now MS Access. Once again, you will need to open this project using
Kingdom 32-bit.
128
Kingdom 8.8
Convert SQL Server or Oracle Database

to Access with DBAdmin
If your Kingdom project database is SQL Server, SQL Server Express, or Oracle, you can
convert it back to MS Access using either Kingdom Data Manager, or the Database Admin
Tool included with your base feature of the Kingdom software.
Note: If your project was not originally created in Access, you will have an extra step: Create
a Twin Access Database if no Access Database Exists
separate license.
Database Admin Toolis included with the base Kingdom license. You will need to have
the 32-bit version of Kingdom installed to convert the database to MS Access.
Before beginning the conversion process, we recommend that you back up the original project
which includes the Kingdom project folder and the external database.
Using the Database Admin Tool and Windows Explorer, the project conversion to Access
involves the following steps:
Step 2: Create a Twin Access Database if no Access Database Exists
This step is only required if the project was created in Oracle, SQL Server, or SQL
Express. In this case, there would be no <project name>70sav.mdb file in the project
folder.
Step 3: Import the Database Dump File into the Target Access Database

Start > The Kingdom Software (32-bit) > DbAdmin
Kingdom 8.8
129
1. Open the Database Admin Tool in the 32-bit version. From your desktop select Start >
The Kingdom Software (32-bit)>DbAdmin.
dialog box.
3. In the Select a Project Manager dialog box, select the database of your project.
4. In the <Database Type> Configuration dialog box, enter the Service Name, User Name,
and Password.
Figure 26 SQL Server Configuration dialog box
5. In the Database Admin tool, select your project in the left panel and select Project >
Export to File.
Depending on your database configuration, you may see more that one project listed.
130
Kingdom 8.8

7. Click No in the NULL out message to complete the export:
Do you want to NULL out any metadata dates (e.g. DateCreated,
DateLast Accessed)?
The exported database now resides in the project folder and is ready to be imported into the
Access database once it is created.
Kingdom 8.8
131
Create a Twin Access Database if no Access

Database Exists
This step is only required if your project was not originally created in Access. You will have
to create a dummy project in Access with the same <project name> and project options as
your source project.
If your project was originally created in Access and has a <project name>70sav.mbd file,
proceed to Import the Database Dump File into the Target Access Database.
1. In Kingdom 32-bit, select Project > Create New Project.
2. Navigate to the source Kingdom project folder. Create the new project inside the existing
project folder.
3. In the Create New Project dialog type the name of the project to be converted. This name
must be identical to the original name. After typing in the project name click Create.
Figure 27 Subdirectory Warning
6. Select Access as your Project Database and click OK.
information is already recorded in the dumped Oracle or SQL Server database, and will be
132
Kingdom 8.8
9. After the project opens, exit The Kingdom application.

10. Navigate to the twin project folder which is located within the original project folder and
move or copy the new empty Access database (<project name>70.mdb) file up one level
into the original project directory.
The Access database is now ready to be populated by the export.dmp file.
Import the Database Dump File into the Target

Access Database
The next step is to import the *dmp file into the new (or original) Access database.
If your original project was Access, when you upgraded your database from Access to Oracle
or SQL Server, the Access database file was renamed to <project name>70sav.mdb.
1. Before you can import your SQL Server Express .dmp data into the original Access
database, you must rename the <project name>70sav.mdb file by removing the sav.
Note: If you created a new Access database then you will not need to rename the file. Skip to
step 2.
a. In Windows Explorer, navigate to the project folder and locate the renamed Access
database file, or <project name>70sav.mdb.
b. Right click the <project name>70sav.mdb file, select Rename. Remove the sav from
the file name. The Database Admin Tool will now be able to connect to the Access
database.
2. In the Kingdom Software 32-bit Database Admin Tool, connect to the projects renamed
Access database.
a. In the Database Admin Tool main window, select Database > Connect and select
MS Access as your database. Click OK.
choices.
b. In the Open dialog box, navigate to the project folder, select the <project name>.tks
file and click OK.
3. Import the *.dmp file into the project. This will replace the old Access contents.
a. In the left panel, highlight the project.
b. In the Database Admin Tool main menu, select Project > Import from File.
Kingdom 8.8
133
c. In the warning box, click Yes to replace this project with the import data.
d. In the Windows Open dialog box, navigate to the export.dmp file in the project folder
and click Open.
The contents of the SQL Server Express database will replace the original contents of the
Access database or populate the new Access database.
The project is now an Access project.
Check the Status of the Converted Project

Now rename the <project name>.xml file and open the Access project to verify that the
project converted successfully.
1. In Windows Explorer, navigate to the project folder and locate the <project name>.xml
file. Right click the <project name>.xml file, select Rename and modify the original
name.
2. Now find the <project name>.tks file and double click to open the project in Access.
3. If you created a twin Access project, then you can now delete the twin project folder. See
the following Warning:
Warning: Be very careful when you delete the twin Access project. Open the folder before
you delete to check the contents. There should be no author folders or
interpretation files in the project folder.
134
Kingdom 8.8
Convert SQL Server Database to Oracle

(or vice versa) with DBAdmin
Note: For troubleshooting tips see An Error Occurred Connecting to the Database.
You can convert your Kingdom project database from SQL Server to Oracle or vice versa
using either Kingdom Data Management or the Database Admin Tool included with your base
feature of the Kingdom software.
separate license.
Database Admin Toolis included with the base Kingdom license.
Before beginning the conversion process, we recommend that you back up the original project
which includes the Kingdom project folder and the external database.
Using the Database Admin Tool and Windows Explorer, the project conversion involves the
following steps:
Step 2: Create an Empty Target Database
Step 3: Import the Database Dump File into the Target Database

Start > The Kingdom Software (32 or 64 bit) > DbAdmin
1. Open the Database Admin Tool. From your desktop select Start > The Kingdom
Software (32 or 64 bit) > DbAdmin.
dialog box.
3. In the Select a Project Manager dialog box, select the database of your project.
choices.
Kingdom 8.8
135
and Password.
Figure 28 SQL Server Configuration dialog box
5. In the Database Admin tool, select your project in the left panel and select Project >
Export to File.
136
Kingdom 8.8

7. Click No in the NULL out message to complete the export:
Do you want to NULL out any metadata dates (e.g. DateCreated,
DateLast Accessed)?
The exported database now resides in the project folder and is ready to be imported into the
target database once it is created.
Create an Empty Target Database

Kingdom 8.8
137
You will need to know the project options of your project to create the empty target database.
1. In Kingdom, select Project > Create New Project.
2. Navigate to the source Kingdom project folder. Create the new project inside the existing
project folder.
3. In the Create New Project dialog type the name of the project to be converted. This name
must be identical to the original name. After typing in the project name click Create.
Figure 29 Subdirectory Warning
6. Select your target project database and click OK.
7. Enter the database name, user name and password and click OK.
information is already recorded in the dumped Oracle or SQL Server database, and will be
10. Exit The Kingdom application.
11. Now Browse to the new twin project folder which is located within the original project
folder and move or copy the new <project name>.xml file up one level into the original
project directory. Click Yes to replace the existing file.
The target database is now ready to be populated by the export.dmp file.
138
Kingdom 8.8
Import the Database Dump File into the Target

Database
Database > Connect
The next step is to import the *dmp file into the target database.
1. In the Database Admin Tool main window, select Database > Connect and select the
database that you created as your target database. Click OK.
choice.
and Password.
3. In the Database Admin tool, select your project in the left panel. With the project path
highlighted, select Project > Import from File.
4. In the warning box, click Yes to replace this project with the import data.
Kingdom 8.8
139
5. In the Windows Open dialog box, navigate to the export.dmp file in the project folder and
click Open.
The contents of the exported (source) database will populate the new target database.
6. Now open the project in Kingdom to verify that the project converted successfully.
7. Once you have confirmed that the project converted successfully you can delete the empty
twin project folder within the main project folder.
140
Kingdom 8.8
Database Admin (DBAdmin) Tool

Overview
Start > Programs > The Kingdom Software [version#] > DbAdmin
The Database Admin Tool can be used to examine and edit (if required) Kingdom project
database tables, copy and convert project databases, set the conditions and backup procedures
for archiving Kingdom project databases, and specify parameters for the Kingdom Data
Managements Data Transfer tool and OpenSpirit/Tunnel O connectivity.
For example, if you are launching DBAdmin from Kingdom 8.7.1, any projects being
managed should also be in Kingdom 8.7.1. If necessary, upgrade the project to the
On your desktop, click Start > Programs > The Kingdom Software 8.7.1 > DbAdmin to
launch the Database Admin Tool as seen in the figure below.
Kingdom 8.8
141
The initial Database Admin Tool contains the following menu items:
DatabaseDBAdmin Database Menu.
View
Backup ToolsBackup Tools
OpenKINGDOMOpenKingdom Data Server
LicenseDBAdmin License Menu
Help
142
Kingdom 8.8
DBAdmin Database Menu

Database > Connect
ConnectConnect to a Project Database.
Create Test Projectthis option is not supported at this time.
Change Project Managerthis option is not supported at this time. To change the
Project Manager, select Database > Connect.
Convert Base64 Dataopens the Convert Base64 to Array of float dialog box, which
allows you to convert base64 data to binary data. Cut the portion of the file (the control
file) you wish to convert and paste it into the top window. The translation to binary values
will be displayed in the lower portion of the window.
Manual SQL Server Express (SSE) Managementlaunches the SQL Express

Management tool used to copy, move, backup, restore, or delete your Kingdom projects
that have SQL Server Express databases.
Exitclick to close all windows and exit the Database Admin Tool window.
Connect to a Project Database

Database > Connect
From the main menu bar in the Database Admin Tool window, choose Database > Connect
to open the Select a Project Manager dialog box.
The Select a Project Manager dialog box displays the various types of databases that are
valid project databases within Kingdom. Click a project manager icon to open the Open
dialog box, in which you can navigate to select a project.
For Oracle, SQL Server, and SQL Server Express databases the next step is to enter the
database login credentials. For Access databases, no login credentials are required. You will
browse to the Kingdom project folder and select the *.tks file.
Kingdom 8.8
143
Project Manager Configuration

The Oracle and SQL Server Configuration dialog boxes are used to configure the database
settings where each dialog box is specific to the type of Project Manager selected in the Select
a Project Manager option.
Oracle Configuration
When an Oracle Project Manager is selected as the Project Manager, the Oracle
Configuration dialog box opens allowing you to specify the Oracle Service Name, User
Name and Password.
Oracle Service Namename assigned to the Oracle database when the client portion of
the Oracle components were installed on the local system.
User Nameuser name associated with the Oracle Instance when database tables were
created on the server system.
Passwordpassword associated with the Oracle Instance.
Note: This account will need administrative privileges if you intend to delete a project.
Backup and restore require only read/write access rights to the tables.
SQL Server Configuration

If a SQL Server project manager is selected as the Project Manager, the SQL Server
Configuration dialog box opens allowing you to specify the SQL Server name, User name
and Password.
144
Kingdom 8.8
SQL Server Connectname of the SQL-Server host server.
User Nameuser name associated with the SQL Server database when the database
tables were created on the server system
Passwordpassword associated with the SQL Instance when the database tables were
created on the server system.
Database Admin Tool

After you have run the DBADMIN.exe program and connected to the correct database type
for your projects using the SQL Server Configuration or Oracle Configuration, the
Database Admin Tool dialog box opens to the configured database.
The Database Admin Tool is most commonly used for the following tasks:
Backing up Kingdom Project Databases.
Viewing projects in SQL Server and Oracle databases
Running author reports
Configuring settings for OpenSpirit Kingdom connectivity
Managing your SQL Server Express projects using the Manual SQL Server Express (SSE)
Management Tool.
Tip:
This tool is also available from the Kingdom Start Page under Tools.
Kingdom 8.8
145
Once DbAdmin has connected to the specified database, the following menu items are added:
DBAdmin Project Menuprovides options to manage the individual project tables,

including create new project tables, edit project information, create author reports, and
import / export dump files for backup, copy and recovery.
Run a Script on Projects in DBAdminprovides options to create and run scripts on

selected projects or all projects.
DBAdmin Project Menu

The Project menu items are only activated if you are connected to a database instance that
contains one (or more) Kingdom projects. These options are useful when either Oracle or SQL
Server is the Project Manager housing the database.
Create New Project Tablesallows the user to create new Access databases or tables
within Oracle and SQL Server. The type is based on the Project Manager opened within
DBADMIN during this session.
Edit Project Informationallows the user to modify the project information of a SQL
Server or an Oracle database. Changes can be made to the GUID:, the Display Name
146
Kingdom 8.8
(a.k.a. database Project Name), the Project Path and the Prepend (the table entry) and the
status of Locked/UnLocked on the selected project. The ability to Lock or UnLock a
project during backup is currently not implemented.
Warning: Editing project information incorrectly will corrupt the project. Only edit if you are
sure the edits are valid.
Find Project by GUIDfind an Oracle or a SQL Server Database by supplying GUID

number.
List Project Tableslist Tables from the selected project in the Table List window. Valid
with SQLServer or Oracle databases.
Consistency Checklaunches a tool which deletes duplicate data in project.
Author Reportopens Select Author(s) dialog box, in which you can select a project
author.
Convert Base64 DataSame as Database > Convert Base64 data.
Delete Selected Projectremoves the specified projects tables from the database. This
feature is valid with SQL Server or Oracle databases. This feature does not remove the
project folder or files.
Resolve All Projectsthis option is not functional at this time.
Resolve All Projects (with Reports)this option not functional at this time.
Import from Fileimports data from any previously saved dump file and will overwrite the selected projects tables. This option can be used to convert to a different database
structure (i.e., Access databases to Oracle or SQL Server tables or Oracle to SQL Server
or SQL Server to Access and etc.).
Export to Filecreates a .dmp backup file of database. This option is valid for all
supported database types. Use this tool to create a project backup of a Kingdom project
with an external database such as Oracle or SQL Server. See
Tech Support Wizardthis option not functional at this time.
Run a Script on Projects in DBAdmin
Run script on Selected Projectsallows you to convert an earlier version of selected

Kingdom projects into a compatible project database for later versions of TKS using the
script LocalOraAutogenUpgradeDML70-71.scp
Run script on ALL Projectsallows you to convert ALL earlier versions of Kingdom
projects into a compatible project database for later versions of TKS.
Kingdom 8.8
147
Backup Tools
See also Backing up Kingdom Project Databases
Note: For Manual SQL Server Express projects, use the Manual SQL Server Express (SSE)
Management tool in the Database Admin utility. This tool will backup both database
tables and project files into one file.
Projects using the Auto SSE configuration can be backed up by copying the project
folder once all authors have exited the project. The detached database files are in the
project folder.
Backupallows you to select a Control File, activate an interactive backup and review
the report log at completion
Control Fileclick to open a standard Windows Open dialog box, in which you can
navigate to locate a *.ctl control file to use in your backup.
-
Newclick to open a Save As dialog box, in which you can navigate to locate an
SMT Backup Control File (smtbackup.ctl) to use in the Save operation.
Verifyclick to open a standard Windows Open dialog box, in which you can
navigate to locate a *.ctl control file to verify.
Deleteclick to open a standard Windows Open dialog box, in which you can
navigate to locate a *.ctl control file to select and delete.
Editclick to open a standard Windows Open dialog box, in which you can navigate
to locate a *.ctl control file to select and edit.
Mergeclick to open a standard Windows Open dialog box, in which you can
navigate to locate and select *.ctl control files to merge.
Create and Edit a Control File

A Control File (*.ctl) contains the information used to determine which projects are to be
included in the backup process, where the projects database resides, and the frequency with
which a project is backed-up.
Multiple projects can be listed for backup in a single control file (*.ctl).
Execution of a batch script containing the backup command can be used to carry out
scheduled backups.
Project Control File settings not altered on a project-by-project basis will inherit
GLOBAL settings. Global settings must appear first in the Control File.
148
Kingdom 8.8
An explanation of each parameter field in the Modify Project Backup Info dialog box is
included in the Control File (*.ctl) at the beginning of the file. These parameters can be
edited by double clicking the project path in the Database Admin Tool, or they can also
be altered by directly editing the entries in the *.ctl file.
Warning: Syntax errors can be introduced in the *.ctl file if the file is manually edited.
1. Select Backup Tools > Control File > New to open a browser window in which you can
specify and Save the directory folder and the output file name of the control file.
or
Select menu Backup Tool > Control File > Edit to open the file browser window.
2. Click the newly created control file, smtbackup.ctl, then click Open to open the
Database Admin Tool with smtbackup.ctl open as shown below.
3. Double-click GLOBAL in the Projects tree. The Modify Project Backup Info dialog
box opens and displays the GLOBAL parameters of the Control File (*.ctl).
Modify Project Backup Info

The Modify Project Backup Info dialog box allows you to specify parameters that are used
in the back-up procedure.
Backup parameters are set at two levels:
Kingdom 8.8
149
GLOBALglobal settings are parameters that are general to all projects in the control
file. If the parameters have not been specifically altered in each local projects settings
then the GLOBAL settings is used during backup. An example of GLOBAL setting is
shown in the figure Control File Attributes in Database Admin Tool dialog box.
Projectlocal project settings can be made to tailor the settings for a particular project
within the backup control file. If no change is made at the project level, GLOBAL
settings are used during backup.
-
A single-click will list the global attributes and their settings in the Control File
window.
Double-click to open the Modify Project Backup Info dialog box with the selected
project displayed (in this case GLOBAL).
GLOBAL should remain as the parameter specification in the TKS File: when
GLOBAL settings are being altered.
Supply the correct path to the Kingdom project file when specifying the Project
Backup Parameters on an individual basis.
TKS Filedisplays the path to the Kingdom *.tks project file (in this case GLOBAL).
GLOBAL should remain as the parameter specification for TKS File when GLOBAL
settings are being altered.
Browseclick to open a standard Windows Open dialog box in which you can navigate
to locate the TKS file.
150
Kingdom 8.8
Note: Always supply the correct path to the Kingdom project file when altering the Project
Backup parameters on an individual basis. The TKS File (file name) should be
supplied for all Project Database types.
Want Backupwhen selected, specifies to include the project for backup. The
GLOBAL setting should always be checked (ON).
This box acts as an ON/OFF switch to control whether the project should be backed up or
not. This is useful if you want to selectively disable some projects, due to size or time
constraints, but keep their settings in the Control File (*.ctl) for back-up at a later date.
-
Browseclick to open a standard Windows Open window in which you can navigate
to locate a file to overwrite or replace.
Export Filefile that will contain the backup of the database tables. The name can be
altered, the default is export-day-time-year.dmp
The output name supports four special tags %d, %h, %m, and %y
-
Browseclick to open an Open window in which you can navigate to locate a file to
overwrite or replace.
Log Filethis file contains any system messages reported during the backup procedure.
The name can be altered, the default name is log--day-time-year.txt
The output name supports four special tags %d, %h, %m, and %y
-
Browseclick to open an Open window in which you can navigate to locate a file to
overwrite or replace.
Backup Typethis field is used to specify the backup type. Currently only
RDBMS_Tables_Only is supported. Future options may include
RDBMS_And_Binary_Files as well as Seismic_Data.
Connectsupply the name of the Server System housing the project database. This
parameter is typically only used with Oracle and SQL Server databases.
If your project database is MS Access, the database should be located locally in the project
directory and have a file extension of .mdb. In this case this parameter is not necessary.
Userspecify the User name associated with the database when it was created. This
should be the same Password and User account supplied when you open the Kingdom
project. Typically only used when Oracle or SQL Server is the Project Manager of the
database.
Password
Specify the Password assigned when the database you wish to open. This should be the
same Password and User account supplied when you open the Kingdom project. Normally
used only when Oracle or SQL Server is the Project Manager of the database.
Kingdom 8.8
151
Frequencyspecify the number of days to check for a change in file dates before doing a
backup of the project database.
Parameter Specification:
Frequency can be specified in days or hours (i.e., 48 hours, 2 days).The Unit name must be
specified there is no default.
Type: Integer
Example
A frequency of 3 days means:
Back up the project if it has changed in the last three days; otherwise, (i.e. the
project has not been altered in 3 days) ignore this project.
Click OK to Modify the parameters and return to the DataBase Administration
Utility tool with the current.ctl file open in the Control File window.
Click Cancel to close the dialog box without saving any of your changes.
Add Projects to Projects List

Backup Tool > Control File > Merge
The Control file should still be open in the window from the previous step when we edited
GLOBAL and Project settings.
1. Select menu Backup Tool > Control File > Merge. This will display the Open Folder
dialog box.
2. Select the folder where projects to be backup are stored and click OK.
3. In the Project Report dialog box, select projects that are not required in the Projects list:.
to remove or add a single project from the list, hold down the <Ctrl> key and select a
single file from the list.
to remove or add multiple projects to the list, hold down the <Shift> key and select a
first and last file from the list.
4. Click Add.
5. Now the Project tree in the myControlFile.ctl window is populated.
All projects use parameters in the Global unless modified individually. To modify any
parameter for an individual project, double click the project from the Project tree and
modify it and close the dialog box.
6. Close the myControlFile.ctl window, and save it.
152
Kingdom 8.8
Note: The control file can also be edited by opening it with a common editor such as
Notepad. But it is suggested users edit the control file using the dbadmin tool to
avoid some syntax errors. However, deleting projects from the Projects tree can only
be done from the editor currently. The dbadmin backup tool in a later version will
provide the deleting functionality.
Execute DBAdmin Backup Tool

1. Bring up a command Prompt window.
2. Change directories to where the dbadmin.exe is stored.
Example: cd c:\program files\kingdomsuite\tks80
3. Type the following command line:
dbadmin.exe /backup <Path> myControFile.ctl
Where the <Path> is the complete path to the control file. For example E:\TestData\.
4. To verify projects that are scheduled for backup in the Control File, open the project
folder and check to see if the exported dump file exists in the folder.
Note: DBADMIN can also be executed from a batch file containing the following command:
C:\Program Files\KingdomSuite\TKSv#\dbadmin.exe /backup <mypath>
smtbackup.ctl
The batch file can be scheduled using the windows Scheduled Task utility to run at
scheduled times.
Kingdom 8.8
153
DBAdmin License Menu
Select License Serverclick to select a license server you wish to check out licenses
from if Kingdom Software detects multiple network license servers on your network.
Kingdom Software does not communicate with multiple network license servers
simultaneously.
License Statusdetermine the availability of licenses for Kingdom Data Management

and monitor the status of the current network or standalone licenses.
License Search Sequenceselect a standalone or network license search.
154
Get License from My Computer (Standalone Edition)the Standalone Edition

requires a Sentinel plug on a USB or parallel port on the computer. If a Sentinel is not
found, then Kingdom Data Management will give you the option to search the network
for a license.
Get License from the Network License Server (Network Edition)Kingdom Data
Management will search the network for the license.
Kingdom 8.8
OpenKingdom Data Server

OpenKingdom Data Server Overview
What is the OpenKingdom Data Server?
For data transfers to and from Kingdom projects using the OpenSpirit Data Connector and
Tunnel O or OpenSpirits CopySync (now available for Kingdom to Kingdom data transfer
through Kingdom Data Management), you must first specify some settings in DBAdmin.
These settings direct OpenSpirit to the required Kingdom files and directories.
Requirements
Administrator privileges on you local computer.
The server/host name where OpenSpirit server is installed.
The port number to which OpenSpirit client software on your computer can connect.
Note: The port number links to the specific OpenSpirit version/build installed on the server.
Workflow
The setup workflow for the OpenSpirit and Kingdom Data Server is as follows:
1. Install the OpenSpirit Client on your computer. See Installing OpenSpirit Components
in the Kingdom Software Installation Guide.
2. Install the Kingdom version that is compatible with OpenSpirit.
3. In the Database Admin Tool window, choose OpenKingdom from the main menu bar.
Select License Serverrequired for network licenses only.
Kingdom 8.8
155
Set Installation Directoryspecify the installation directory for the Kingdom Software.
Projects Catalog Builderis not active in Kingdom version 8.5 and later. You can now
build your data stores through OpenSpirit.
Project Seismic File Locatorspecify a project by project location for each projects
respective seismic files.
Global Seismic File Locatorspecify a default location for all seismic files.
Select License Server

If you are running Kingdom with a network license, you need to specify the license server
before you can transfer data to and from Kingdom projects using the OpenSpirit Data
Connector and Tunnel O or OpenSpirits CopySync (now available for Kingdom to Kingdom
data transfer through Kingdom Data Management). This operation lets the OpenSpirit
software know where to get a TKS license when OpenSpirit communicates with Kingdom.
In the Database Admin Tool window, choose OpenKingdom > Set License Server.
If only one server is located on your network, a message will display the server name and
IP address. Click OK to confirm.
If more than one server is detected, The Select License Server dialog box will open listing
all servers. Select a server and click OK to exit.
Set Installation Directory

OpenKingdom > Set Installation Directory
In the Database Admin Tool window, choose OpenKingdom > Set Installation Directory
to specify the installation directory for Kingdom. This operation lets the OpenSpirit software
know where Kingdom is installed.
If the Kingdom software is NOT installed in a default folder, you must enter the path to the
folder in the Folder Location text field, or Browse to the folder location.
156
Kingdom 8.8
After you have located the Kingdom installation directory, click OK. This creates an
OpenKingdom.set file which is the link that allows OpenSpirit to get the required Kingdom
.dll files when you run the OpenSpirit Launcher.
This file is also read by Kingdom Data Management for the Data Transfer tool.
Project Seismic File Locator

OpenKingdom > Project Seismic File Locator
In the Database Admin Tool window, choose OpenKingdom > Project Seismic File
Locator to specify the seismic file/data storage location for individual project(s), and where
the CopySync tool in OpenSpirit will place data.
The Project Seismic File Locator dialog box contains the following elements:
1. Select the Data Type
-
Data Typealways SeismicDataFolder.
2. Select TKS Project for Seismic File Catalog
Kingdom 8.8
157
TKS Project Pathclick Browse to open an Open dialog box in which you can
select a path to a TKS project. The selected complete path to the project is displayed in
the TKS Project Path text field. For example:
C:\Projects\Golden\Golden.tks
3. Build Folder ListOrdered By Priority

-
Root Folderclick Browse to open the Browse for Folder dialog box and select the
file folder where you want to store your project seismic data/files. The selected path is
displayed in the Root Folder text field.
4. Addclick to add the path displayed in the Root Folder text field to the Root Folder list.
5. Deleteselect a path in the list and click to delete the selected path.
Note: The Root Folder list is a priority-ordered list. The first folder in the list has the highest
priority, which means seismic data for the project are stored in the folder that is first in
the list. If the specified maximum capacity (Set High Water Mark) of the folder is
reached, the remainder of the seismic data/files are stored in the second file folder, and
so on with succeeding file folders in the list.
6. Set High Water Markallows you to specify the percentage of the total storage capacity
of a folder that can be used to store the data. You can select a folder in the list, select the
high water mark, then click Update to keep your setting for this folder. The Update
button is associated with the folder name you highlighted in the folder list, which means
the High Water Mark for only the selected folder will be set to the percentage specified.
OKclick to create a SeismicDataFolderCollection.xml in a Config sub-folder under

the project specified in the Select TKS Project for Seismic File Catalog area.
Note: You can specify the seismic data/file location for a project only once. However, if you
have several projects for which you need to specify seismic data/file locations, you can
return to the Project Seismic File Locator dialog box and perform repeated
operations.
Global Seismic File Locator

In the Database Admin Tool window, choose OpenKingdom > Global Seismic File
Locator to specify file folders for storing seismic data for all projects.
158
Kingdom 8.8
The Global Seismic File Locator dialog box contains the following elements:
Select the Data Type

-
Data Typealways SeismicDataFolder.
Global Seismic File Catalog Path

-
Seismic File CatalogThe Global Seismic File Locator dialog box is similar to the
Project Seismic File Locator dialog box, except that the file path displayed defaults
to:
C:\Documents and Settings\All Users\Application

Data\KingdomSuite\SeismicDataFolderCollection.xml
Note: The path displayed in Global Seismic File Catalog Path cannot be changed.
Build Folder ListOrdered By Priority

-
Root Folderdisplays the path/folder selected in the Browse for Folder dialog box.
Browseclick to open the Browse for Folder dialog box and select the file folder
where you want to store your project seismic file catalog. The selected path is
displayed in the Root Folder text field.
Kingdom 8.8
159
Addclick to add the path displayed in the Root Folder text field to the Root Folder
list.
Deleteselect a path in the list and click to delete the selected path.
Note: The Root Folder list is a priority-ordered list. The first folder in the list has the highest
priority, which means that a project seismic file catalog is stored in the folder that is
first in the list. If the specified percentage of the total capacity (Set High Water
Mark) of the folder is reached, the remainder of the seismic file catalog is stored in the
second file folder, and so on with succeeding file folders in the list.
Set High Water Markallows you to specify the percentage of the total storage
capacity of a folder that can be used to store the data. You can select a folder in the list,
select the high water mark, then click Update to keep your setting for this folder. The
Update button is associated with the folder name you highlighted in the folder list, which
means the High Water Mark for only the selected folder will be set to the percentage
specified.
-
OKclick to create a SeismicFile CatalogCollection.xml in a Config sub-folder

under the project specified in the Select TKS Project for Seismic File Catalog area.
Note: You can specify the seismic data/file location for a project only once. However, if you
have several projects for which you need to specify seismic data/file locations, you can
return to the Project Seismic File Locator dialog box and perform repeated
operations.
160
Kingdom 8.8

Database Admin

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Database Admin

Caricato da

Copyright:

Formati disponibili

IHS

2012 IHS. All Rights Reserved. All trademarks belong to IHS

Trademarks and Copyright

8584 Katy Freeway, Suite 400

The following trademarks appear in this manual.

2011 - 2012 IHS Inc.

Microsoft SQL Server Express as the Project Database

SQL Server Express Service Configuration

Manual SQL Server Express (SSE) Management

Microsoft SQL Server as the Project Database

Installing and Configuring a SQL Server Database . . . . . . . . . . . . . . . . . . . . . . . .

Oracle as the Project Database

Kingdom Project Backups

Kingdom Project Database Conversions

Database Admin (DBAdmin) Tool

OpenKingdom Data Server

SQL Server Express Service Configurationcontains detailed information on configuring

Kingdom Project Database Conversionscovers processes to convert Kingdom project

OpenKingdom Data Servercontains settings required to transfer data to and from

increased addressable memory (8 Terabytes)

improved graphics capabilities

SQL Server (Single)creates a project specific database. With this configuration,

Kingdoms SQL Server Express

Auto SSEis configured to be automatically portable. As long as all data is contained

Note: The Kingdom Software is not certified on Oracle Express Edition.

Microsoft Access Users

Access has a 2 GB single database size limit.

Advantages of Oracle and SQL Server as a

They provide an additional level of protection by requiring user authentication prior to

An Error Occurred Connecting to the Database

An Error Occurred Connecting to the

Microsoft SQL Server Express as

Auto SSEis configured to be automatically portable. As long as all data is contained in

What are you trying to do?

See How is Auto SSE different from Manual SSE?

First select Local or Network.

Update my Kingdom projects with Access databases to SQL Server Express.

See Migrate Access Database to SQL Server Express

I cant connect to the database or start the service.

Connecting to your SQL Server Express Database troubleshooting tips

Unable to start the service

Im using the Manual option and need to make my project portable.

How is Auto SSE different from Manual

Places the database in the Kingdom project directory

Places the database in the KingdomSuite

Automatically attaches the database when the first

Does not automatically detach / attach

Automatically detaches the database when the last

You must use the Manual SSE

After all users exit the project, you must

Supports the following location combinations:

Supports mixed mode location

Local ProjectLocal Database Instance

Network ProjectNetwork Database Instance

How is Auto SSE different from Manual SSE?

Auto SSE and Backward Compatibility

Changing an Auto SSE Project back to Manual

How is Auto SSE different from Manual SSE?

Migrate Access Database to SQL

Migrate Access Project to Auto SSE

Migrate Access Project to Manual SSE

Connecting to your SQL Server Express Database

Connecting to your SQL Server

My Kingdom SSE instance is not listed