Documente Academic
Documente Profesional
Documente Cultură
Database Administration
User Manual
December 2012 v8.8
www.ihs.com/Kingdom
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.
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
7
9
10
10
14
14
15
18
19
29
30
32
37
42
44
46
48
50
51
52
57
62
Kingdom 8.8
Table of Contents
66
66
67
68
69
72
73
76
76
76
79
80
80
84
89
89
90
93
95
97
98
99
101
104
108
108
113
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
141
143
143
145
148
154
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.
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.
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.
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)
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 (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.
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
Oracle as the Project Database
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.
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.
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.
In theory, there is no database size limitation. Databases are actively sizeable to allow
project growth.
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
Kingdom 8.8
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.
Ive just installed SQL Server Express and need help configuring the service.
-
If you are in a network environment, you will need help from your domain
administrator. See Network ProjectNetwork Database Instance for instructions.
Kingdom 8.8
Manual SQL Server Express (SSE) Management provides details on how to copy,
move, backup, restore, and delete your Kingdom projects.
Kingdom 8.8
Auto SSE
Manual SSE
After all users exit the project, you can copy / move
the project with Windows Explorer
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
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.
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
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
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.
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
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
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
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:
1. Click Start > Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL
Server Configuration Manager.
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
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.
18
Kingdom 8.8
Kingdom 8.8
19
20
Kingdom 8.8
Local
Projects
Users
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
Users
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.
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.
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.
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
Kingdom 8.8
25
26
Kingdom 8.8
Table 1
The user password is not
valid
Add the service account user to the computer where the SQL
Server Express instance is installed and add to Administrator
Group
Kingdom 8.8
27
28
Kingdom 8.8
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.
Auto SSE and Backward Compatibility
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.
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.
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:
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:
Create a Backup
Restore a Backup
4.
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 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.
32
Kingdom 8.8
Kingdom 8.8
33
<project name>.tks.bak
<project name>_1.bak
databaseinfo.xml
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.
34
Kingdom 8.8
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
<project name>.tks.bak
<project name>_1.bak
databaseinfo.xml
9. Now using Windows, copy the portable project folder to a storage device to transport to
the external 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.
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 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.
Kingdom 8.8
37
38
Kingdom 8.8
7. When the process is finished, the Summary Report will display project details.
Kingdom 8.8
39
40
Kingdom 8.8
5. Select a project destination. Click Browse and navigate to the destination location for
the active project.
6. 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.
7. Select a Validation mode.
8. Click Start to begin the process. A status bar will display the progress.
9. When the process is finished, the Summary Report will display project details.
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
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.
6. 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.
7. Select a Validation mode.
8. Click Start to begin the process. A status bar will display the progress.
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.
9. When the process is finished, the Summary Report will display project details.
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.
1. Launch Kingdom 32-bit or 64-bit.
2. Under Tools on the Kingdom Start Page click Manage SQL Server Express Projects.
44
Kingdom 8.8
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.
1. Launch Kingdom 32-bit or 64-bit.
2. Under Tools on the Kingdom Start Page click Manage SQL Server Express Projects.
46
Kingdom 8.8
6. 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.
7. Select a Validation mode.
8. Click Start to begin the process. A status bar will display the progress.
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.
9. When the process is finished, the Summary Report will display project details.
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
48
Kingdom 8.8
Kingdom 8.8
49
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.
7. When the process is finished, the Summary Report will display project details.
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
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
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
Solution
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
Solution
Message
Solution
Necessary files or folders have been deleted, moved, or modified. The portable
project is no longer complete and valid.
Message
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
54
Kingdom 8.8
Solution
Message
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
Kingdom 8.8
55
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
Kingdom 8.8
57
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
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:
Kingdom 8.8
61
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
Remote
Remote
62
Local
Remote
NT
Authority\Network
Service
NT
Authority\Network
Service
Kingdom 8.8
Remote
Local
Remote
Remote
Kingdom 8.8
63
64
Kingdom 8.8
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
66
Kingdom 8.8
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.
Kingdom 8.8
67
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.
Kingdom 8.8
69
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.
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.
Kingdom 8.8
71
2. Under SQL Server 2005 Network Configuration, select Protocols for <INSTANCE
NAME>.
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 (INSTANCE_NAME) and select Restart.
72
Kingdom 8.8
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.
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
76
Kingdom 8.8
2. Under SQL Server 2005 Network Configuration, select Protocols for <INSTANCE
NAME>.
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 (INSTANCE_NAME) and select Restart.
Solution 2B: Now return to the Kingdom workstation and Enable the TCP/IP Client Protocol
using the same procedure:
1. Click Start > Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL
Server Configuration Manager.
Kingdom 8.8
77
78
Kingdom 8.8
Configuring the Oracle Hoston the Windows, Solaris, or Linux machine designated as
the server.
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 Kingdom Software is not certified on Oracle Express Edition.
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
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
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
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.
84
Kingdom 8.8
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
88
Kingdom 8.8
If you do not see your Oracle Service Name on the list, see Connecting to your Oracle
Database.
Note: If you are running Kingdom 32-bit on a 64-bit OS, you will need both clients installed
on your workstation.
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
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.
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
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
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):
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).
94
Kingdom 8.8
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
on your workstation.
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:
-
Install a version of Oracle that does work with parentheses or install patch 5059238 for
Oracle client 10.2.0 32-bit.
Kingdom 8.8
95
. 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
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.
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
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
Related Topic
Automating SQL Server and SQL Server Express Backups
100
Kingdom 8.8
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
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
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.
Kingdom 8.8
105
For Access and SQL Server Express projects there will be only one project in the left
panel.
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
Kingdom 8.8
107
108
Kingdom 8.8
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.
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.
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
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 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
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
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
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.1, any projects being
managed should also be in Kingdom 8.7.1. If necessary, upgrade the project to the
version of DBAdmin before using the tool on that project.
Using the Database Admin Tool and Windows Explorer, the project conversion back to
Access involves the following steps:
124
Kingdom 8.8
Kingdom 8.8
125
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
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.
128
Kingdom 8.8
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.
2. In the Database Admin tool, select Database > Connect to open the Project Manager
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.
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
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
5. In the Author Name dialog box, enter an author and click OK.
6. Select Access as your Project Database and click OK.
After the project tables are created, the Project Options dialog box opens.
7. Enter the same project options as the original project and click OK.
8. Click No to Do you want to use the coordinate system of an existing project? This
information is already recorded in the dumped Oracle or SQL Server database, and will be
retrieved once the project is converted.
132
Kingdom 8.8
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.
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.
The project is now an Access project.
134
Kingdom 8.8
Kingdom 8.8
135
Convert SQL Server Database to Oracle (or vice versa) with DBAdmin
4. In the <Database Type> Configuration dialog box, enter the Service Name, User Name,
and Password.
5. In the Database Admin tool, select your project in the left panel and select Project >
Export to File.
136
Kingdom 8.8
The exported database now resides in the project folder and is ready to be imported into the
target database once it is created.
Kingdom 8.8
137
Convert SQL Server Database to Oracle (or vice versa) with DBAdmin
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.
4. Click Yes in the warning message.
5. In the Author Name dialog box, enter an author and click OK.
6. Select your target project database and click OK.
7. Enter the database name, user name and password and click OK.
After the project tables are created, the Project Options dialog box opens.
8. Enter the same project options as the original project and click OK.
9. Click No to Do you want to use the coordinate system of an existing project? This
information is already recorded in the dumped Oracle or SQL Server database, and will be
retrieved once the project is converted.
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
4. In the warning box, click Yes to replace this project with the import data.
Kingdom 8.8
139
Convert SQL Server Database to Oracle (or vice versa) with DBAdmin
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
Kingdom 8.8
141
The initial Database Admin Tool contains the following menu items:
View
Help
142
Kingdom 8.8
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.
Exitclick to close all windows and exit the Database Admin Tool window.
Kingdom 8.8
143
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.
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.
144
Kingdom 8.8
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.
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:
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.
List Project Tableslist Tables from the selected project in the Table List window. Valid
with SQLServer or Oracle databases.
Author Reportopens Select Author(s) dialog box, in which you can select a project
author.
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 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
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.
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).
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.
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.
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
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.
154
Get License from the Network License Server (Network Edition)Kingdom Data
Management will search the network for the license.
Kingdom 8.8
Requirements
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.
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.
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.
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.
The Project Seismic File Locator dialog box contains the following elements:
1. Select the Data Type
-
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
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.
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.
158
Kingdom 8.8
The Global Seismic File Locator dialog box contains the following elements:
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:
Note: The path displayed in Global Seismic File Catalog Path cannot be changed.
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.
-
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