You are on page 1of 12

SMT Planning Guide v8.

5
Whats in the Planning Guide?
This Planning Guide is intended to guide you through the following decisions: Should I install the KINGDOM Software 32-bit or 64-bit? What is the difference? What are my database choices, or do I even have to choose? If I configure a particular database to house my KINGDOM projects, can I convert to a different database later?

The Planning Guide contains the following sections that will answer these questions with the focus being on the transition from MS Access to SQL Server Express: 32-bit versus 64-bit KINGDOM Software Database Choices SQL Server Express (SSE) Installing SQL Server Express Migrating your Access Database to SQL Server Express Managing your SQL Server Express (SSE) Projects SQL Server Express Project Backups KINGDOM and SQL Server Express FAQs

KINGDOM 8.5

32-bit versus 64-bit KINGDOM Software

32-bit versus 64-bit KINGDOM Software


The 64-bit version of KINGDOM is highly recommended due to the scalability limitations inherent with 32-bit applications. The advantages of 64-bit applications are increased memory capacity (many 64-bit workstations can have up to 128 GB of RAM), and increased addressable memory (8 terabytes), which together can significantly increase application performance.

KINGDOM Software (64-bit)


can only be installed on a 64-bit machine installs to C:\Program Files\KingdomSuite\TKS85 is not compatible with MS Access as the project database. A database upgrade to SQL Server Express (SSE), SQL Server, or Oracle is required. Access projects can be easily migrated to any of these databases from the KINGDOM Start Page. SQL Server Express is Microsofts replacement for Access on the 64-bit systems. SMT provides an upgrade to SQL Server Express at no extra cost which can be downloaded from the SMT Web site and then installed on your machine, or installed from the SMT Installation Manager on the KINGDOM Software DVD.

KINGDOM Software (32-bit)


can be installed on a 32-bit or 64-bit machine installs to C:\Program Files\KingdomSuite\TKS85 on a 32-bit machine installs to C:\Program Files(x86)\KingdomSuite\TKS85 on a 64-bit machine can use SQL Server Express, SQL Server, or Oracle as the project database. The database application will have to be installed separately. is currently compatible with MS Access as the project database

KINGDOM 8.5

Database Choices

Database Choices
The KINGDOM software supports MS SQL Server Express, MS SQL Server, Oracle, and MS Access (32-bit only) databases. Microsoft does not support a 64-bit version of Access. Therefore, if you are planning to install KINGDOM Software 64-bit, you will have to upgrade to one of the following databases: SQL Server Express (SSE) - is Microsofts replacement of Access provided free of charge and has a database size limit of 4 GB.

Note: MS Access has a database size limit of 2 GB. SQL Server - operates on Windows only and needs to be purchased and installed separately. Theoretically, there are no limitations to the size of the database. SQL Server also has multiprocessor support capability. Oracle - can operate on Windows or Unix / Linux operating systems and needs to be purchased and installed separately. Theoretically, there are no limitations to the size of the database. Oracle has multiprocessor support capability.

Note: The KINGDOM Software is not certified on Oracle Express. See The KINGDOM Software Help Topics > Database Administration for more information on configuring Oracle and SQL Server for KINGDOM.

KINGDOM 8.5

SQL Server Express (SSE)

SQL Server Express (SSE)


SQL Server Express is provided free of charge. This SMT version of SQL Server Express has a dedicated SMTKINGDOM instance with a pre-configured username and password to make the upgrade user friendly and seamless. SQL Server Express can only run on Microsoft operating systems. For Linux / Unix servers, you will need to install Oracle. This section contains the following topics: Installing SQL Server Express Migrating your Access Database to SQL Server Express Managing your SQL Server Express (SSE) Projects SQL Server Express Project Backups KINGDOM and SQL Server Express FAQs

Installing SQL Server Express


See also SQL Server Express and Windows 7. If you already have SQL Server Express installed on your system, you must still install the SQL Server Express SMTKINGDOM instance which is available from the following: as a download from the SMT Web site or from the Update Manager. Log in to My Account and select Downloads > Latest Release. from the KINGDOM Software DVD. If you do not have access to the internet or if you have downloaded the ISO image and burned it to a DVD, you will install SQL Server Express from the SMT Installation Manager. Select the Install Third Party Software tab and click Install Microsoft SQL Server Express.

Installation of this instance will not affect your existing instances of SQL Server Express. You do not need to uninstall existing instances. Caution: If multiple users are going to access the SQL Server Express projects, you should install SQL Server Express on a network accessible machine. You cannot specify to install SQL Server Express on a different machine than the one you are logged into. For optimal KINGDOM performance, run SQL Server Express on a dedicated machine with at least 3GB of physical memory.

KINGDOM 8.5

SQL Server Express (SSE)

Note: You only need to install SQL Server Express once. Reinstalling or updating KINGDOM will not affect SQL Server Express.

SQL Server Express and Windows 7


If the computer where the SMTKINGDOM instance of SQL Server Express is installed is running Windows 7, then Microsoft SQL Server Express version 2005 SP3 or later is required. Version 2005 SP3 is available for download from the SMT Web site or from the KINGDOM 8.5 DVD. Before updating SQL Server Express, you should back up your KINGDOM project databases. See SQL Server Express Project Backups. Note: If your workstation has Windows 7 but the computer where SQL Server Express is installed has Windows XP or Vista, no upgrade is required.

Migrating your Access Database to SQL Server Express


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. With KINGDOM 8.5 you can migrate to SQL Server or Oracle from both KINGDOM 32-bit and 64-bit. 1. Launch KINGDOM and select Project > Open Project or From the KINGDOM Start Page click Migrate Access Project under Tools and browse to the *.tks file of the Access project: Note: You must have SQL Server Express installed first. 2. If you are running the 32-bit version of KINGDOM you will be prompted to migrate your project, but the database migration is optional.

KINGDOM 8.5

SQL Server Express (SSE)

Figure 1 Optional Access Database Migration

Click Yes if you want to migrate your project database at this time. If you are running the 64-bit version of KINGDOM, you must migrate the project before you can open it. When you try to open your Access project, you will be prompted to migrate the project database as in Figure 2 below.

Figure 2 Migrate Project Database from Access to SQL Server or Oracle

3. Select Microsoft SQL Server or Microsoft SQL Server Express and click Migrate. 4. Specify the SQL Server Instance into which the Access database contents will be imported.

KINGDOM 8.5

SQL Server Express (SSE)

Figure 3 Microsoft SQL Server Configuration

SQL Server Connectlists the names of available SQL Server instances. The KINGDOM configured SQL Server Express instances are named <computer name> \SMTKINGDOM. If you have installed SQL Server Express on your local computer, then <computer name> will be the name of your computer. User Name and Passwordare required for SQL Server and Oracle databases, but not for the SMTKINGDOM instance of SQL Server Express. These fields will disappear after you select your SMTKINGDOM instance as in Figure 4 below. Note: For shared projects, select a network accessible SQL Server Express instance.

Figure 4 SQL Server Express with SMTKINGDOM Instance Connect

5. Click OK to import the project into the specified SQL Server Express database and complete the migration. The Select Author dialog box opens, and your project is ready to go in SQL Server Express.

KINGDOM 8.5

SQL Server Express (SSE)

Note: When your project is converted to SSE, 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 SMTKINGDOM instance of SQL Server Express.

Note: See The KINGDOM Software Help Topics > Database Administration for instructions on other project conversions and on installing and configuring required Oracle and SQL Server components.

Managing your SQL Server Express (SSE) Projects


Like SQL Server and Oracle, the project database of your SSE project no longer resides in the project folder as it does with MS Access. Therefore, to perform project management tasks such as copy, move, backup, or delete, a minimum of two items will need to be managed: the project folder and the project database. 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 the SQL Server Express Management tool to manage your project, move all external files into the KINGDOM project folder. You can manage your SSE projects through one of two tools: 1. SQL Server Express Managementprovides a number of project management options for your SSE projects: make a project portable, copy, move, or delete a project, backup and restore a project. This tool is available from the KINGDOM Start Page. Under Tools click Manage SQL Server Express Projects. 2. KINGDOM Data Management - is a project management application with a wide range of project inventory and management tools. KINGDOM Data Management requires a separate license.

10

KINGDOM 8.5

SQL Server Express (SSE)

SQL Server Express Project Backups


Before upgrading KINGDOM or SQL Server Express, we recommend that you back up your KINGDOM Projects. Single Project Backups Multiple Project Backups

Note: If the computer where the SMTKINGDOM instance of SQL Server Express is installed is running Windows 7, then Microsoft SQL Server Express version 2005 SP3 or later is required. Version 2005 SP3 is available for download from My Account on the SMT Web site or from the KINGDOM 8.5 DVD.

Single Project Backups


The SQL Server Express Management tool available from the KINGDOM Start Page has a simple backup tool for single project backups. 1. Launch KINGDOM 32-bit or 64-bit. 2. Under Tools on the KINGDOM Start Page click Manage SQL Server Express Projects. 3. Select Create a Backup. 4. Select the source project file (.TKS). Click Browse and navigate to the <project 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 desired location for the backup project file on the network or your computer. Click OK. 6. Select a Validation mode. 7. Click Start to begin the process. A status bar will display the progress. 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.5

11

SQL Server Express (SSE)

Multiple Project Backups


A multiple project database backup of your SQL Server Express projects includes creating a backup script using the SQL Server Management Studio and then launching the script at the time of the backup 1. If required, Download Microsoft SQL Server Management Studio Express and follow the InstallShield Wizard to install. 32-bit OS: SQLManagementStudio_x86_ENU.exe 64-bit OS: SQLManagementStudio_x64_ENU.exe

2. Launch the SQL Server Management Studio Express. 3. Connect to your SQL Server Express database instance. 4. Expand the Databases node and right click on one of the databases to be backed up. 5. Select Tasks > Back Up. 6. 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. Accept the default or browse to the selected location.

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. 7. Save the backup instructions to a file. Click the down-arrow next to the Script button and select Script Action to File. 8. 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). 9. Open the resulting file for edit. Right click on the file and select Edit. The file will open in Notepad. Note: Double-clicking the file will launch an actual backup job.

12

KINGDOM 8.5

SQL Server Express (SSE)

10. Add additional project databases to this script file in order to back up all database: 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 5 Results of Pasting New Backup Instruction into .sql File

11. Save the final edited .sql backup script when completed. 12. 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. 13. Click Execute in the Management Studio. The backups will be written to the designated location: <database name>.bak.

KINGDOM and SQL Server Express FAQs


See the following FAQs concerning your KINGDOM projects and SQL Server Express. Q Will my Access project database automatically be updated when I install SQL Server Express? No, your project databases are not upgraded to SQL Server Express until you open them in KINGDOM version 8.2 (x64) or later with SQL Server Express installed. You will then be advised that the project will be automatically migrated to Oracle or SQL Server / SQL Server Express. If you plan to use 8.5, click Yes to continue. See Migrating your Access Database to SQL Server Express.

KINGDOM 8.5

13

SQL Server Express (SSE)

Will I be able to open my SQL Server Express projects in older versions of KINGDOM once they have been converted? You can open your SSE projects in KINGDOM versions 8.1 and later. However, KINGDOM versions 8.0 and earlier will not recognize the database. If prompted, enter the username: SMTKINGDOM and password: $ei$micMicro. Note that the password is cap sensitive. KINGDOM 8.1 ServicePAK builds 5400.18 and later will automatically open SQL Server Express projects without the user having to enter the user name and password.

Once my projects have been converted to SQL Server Express, can I convert them back to Access? Yes. See The KINGDOM Software Help Topics > Database Admin > Database Conversions.

I have already created KINGDOM projects in SQL Server Express in an earlier version of KINGDOM using a different instance of SQL Server Express. KINGDOM 8.5 only sees the SMTKINGDOM instance projects. What can I do? For a complete workflow, see the FAQ article Attaching SSE Projects to SMTKINGDOM. SMT FAQ articles can be accessed through My Account on the SMT Web site.

14

KINGDOM 8.5