DOCSLIB.ORG

Pervasive.SQL User's Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Pervasive.SQL User's Guide Pervasive.SQL 2000i Pervasive.SQL User’s Guide Guide to Using Pervasive.SQL Pervasive Software, Inc. 12365 Riata Trace Parkway Building II Austin, TX 78727 USA Telephone: +1 512 231 6000 or 800 287 4383 Fax: +1 512 231 6010 E-Mail: [email protected] Web: http://www.pervasive.com disclaimer PERVASIVE SOFTWARE INC. LICENSES THE SOFTWARE AND DOCUMENTATION PRODUCT TO YOU OR YOUR COMPANY SOLELY ON AN “AS IS” BASIS AND SOLELY IN ACCORDANCE WITH THE TERMS AND CONDITIONS OF THE ACCOMPANYING LICENSE AGREEMENT. PERVASIVE SOFTWARE INC. MAKES NO OTHER WARRANTIES WHATSOEVER, EITHER EXPRESS OR IMPLIED, REGARDING THE SOFTWARE OR THE CONTENT OF THE DOCUMENTATION; PERVASIVE SOFTWARE INC. HEREBY EXPRESSLY STATES AND YOU OR YOUR COMPANY ACKNOWLEDGES THAT PERVASIVE SOFTWARE INC. DOES NOT MAKE ANY WARRANTIES, INCLUDING, FOR EXAMPLE, WITH RESPECT TO MERCHANTABILITY, TITLE, OR FITNESS FOR ANY PARTICULAR PURPOSE OR ARISING FROM COURSE OF DEALING OR USAGE OF TRADE, AMONG OTHERS. trademarks Btrieve, Tango, Client/Server in a Box, and the Pervasive Software logo are registered trademarks of Pervasive Software Inc. Built on Pervasive, Built on Pervasive Software, Extranet in a Box, Pervasive.SQL, Jtrieve, Plug n’ Play Databases, SmartScout, Solution Network, Ultra-light Z-DBA, Z-DBA, ZDBA, UltraLight, MicroKernel Database Engine, and MicroKernel Database Architecture are trademarks of Pervasive Software Inc. Microsoft, MS-DOS, Windows, Windows NT, Win32, Win32s, and Visual Basic are registered trademarks of Microsoft Corporation. Windows 95 is a trademark of Microsoft Corporation. NetWare and Novell are registered trademarks of Novell, Inc. NetWare Loadable Module, NLM, Novell DOS, Transaction Tracking System, and TTS are trademarks of Novell, Inc. All other company and product names are the trademarks or registered trademarks of their respective companies. Copyright 2001 Pervasive Software Inc. All rights reserved. Reproduction, photocopying, or transmittal of this publication, or portions of this publication, is prohibited without the express prior written consent of the publisher. This product includes software developed by Powerdog Industries. Copyright 1994 Powerdog Industries. All rights reserved. The ODBC Driver Manager for NetWare (ODBC.NLM) included in this product is based on the GNU iODBC software Copyright 1995 by Ke Jin <[email protected]> and was modified by Simba Technologies Inc. in June 1999. This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. A copy of the GNU Lesser General Public License is included in your installation of Pervasive.SQL 2000i at \pvsw\doc\lesser.htm. If you cannot find this license, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111- 1307 USA. You may contact Pervasive Software Inc. using the contact information on the back cover of this manual. Pervasive.SQL User’s Guide March 2001 100-003672-004 Contents Contents About This Manual . ix Who Should Read This Manual . x Manual Organization . xi Conventions . xii 1 Introducing Pervasive.SQL . 1-1 Understanding Pervasive.SQL and its Capabilities Understanding Pervasive.SQL . 1-2 What is a Database? . 1-2 What is a Database Management System? . 1-3 Components of Pervasive.SQL . 1-3 Key Concepts . 1-5 Basic Database Structures and Terms . 1-5 Unique Benefits of Pervasive.SQL . 1-8 Why Pervasive.SQL? . 1-10 Understanding the Product Family . 1-12 Workstation . 1-12 Workgroup . 1-13 Server . 1-13 Replication . 1-14 Crystal Reports for Pervasive.SQL . 1-15 Helpful Utilities . 1-16 Using Pervasive.SQL Documentation . 1-18 Getting Started Guides. 1-18 User’s Guide . 1-19 Advanced Operations Guide . 1-19 SQL Engine Reference . 1-19 Status Codes and Messages . 1-19 Pervasive Products and Services . 1-20 Online Help. 1-20 File System Security. 1-21 2 Using Pervasive.SQL . 2-1 A Walk-through of Basic User Tasks Starting and Stopping the Database Engine. 2-2 Starting and Stopping Services on Windows Server . 2-3 Starting and Stopping Services on NetWare . 2-4 Starting and Stopping Services on Unix . 2-5 Granting Administrative Rights for the Database Engine . 2-6 Tasks Requiring Administrative Rights. 2-6 iii Contents How Administrative Rights are Granted . 2-6 Rights Provided to Normal Users . 2-6 Granting Administrative Rights on Windows Server. 2-9 Granting Administrative Rights on NetWare 3.2 . 2-11 Granting Administrator Rights on NetWare 4.2 or 5.0 . 2-11 Granting Administrator Rights on Unix . 2-12 Logging in as Administrator . 2-13 Setting Up ODBC Database Access . 2-14 Basic Concepts. 2-14 What to Know if You are Recreating DSNs . 2-17 Prerequisites to Setting up Database Access. 2-17 Setting Up Database Access on a Windows Server or Workgroup/Workstation . 2-19 Setting Up Database Access on a NetWare Server . 2-28 Setting Up Database Access on Unix . 2-36 Setting Up Client Access. 2-39 Accessing Data via ODBC From Other Applications . 2-46 Before You Begin . 2-46 Accessing Data Using Microsoft Excel. 2-46 Accessing Data Using Microsoft Access . 2-49 Deleting DSNs . 2-53 Bound Databases and Enforced Integrity . 2-56 3 Using the Pervasive Control Center . 3-1 A Brief Tour of Pervasive Control Center An Overview of Pervasive Control Center . 3-2 Registering or Removing a Server. 3-4 Viewing Database Engines. 3-7 Interpreting Server Status Icons . 3-7 Pervasive Control Center Wizards . 3-9 Adding or Creating a Database . 3-11 Deleting a Database . 3-15 Adding a Table . 3-18 Modifying a Table Definition . 3-25 Dropping a Table. 3-29 Setting Database Security . 3-31 Turning Security On and Off. 3-31 Working with Groups and Users. 3-32 Stopping and Restarting Services on Windows Servers . 3-38 Viewing and Modifying Table Properties . 3-39 Viewing and Modifying Data . 3-42 Viewing Data . 3-42 Writing and Executing SQL Statements . 3-42 Using the SQL Statement Builder . 3-45 Exporting/Importing Data . 3-46 Checking Consistency and Referential Integrity . 3-54 iv Contents Listing Referential Constraints . 3-54 Checking Consistency . 3-55 Checking Referential Integrity . 3-57 4 Unix Supplementary Documentation . 4-1 Additional Information on Unix Utilities User Manual Exclusions for Unix . 4-2 Utilities . 4-2 Changes and Exclusions . 4-2 Man Pages . 4-4 Available Utilities . 4-5 5 Basic Troubleshooting . 5-1 How to Identify and Solve Common Problems General Troubleshooting. 5-2 Error Messages from PCC . ..
Load more

Recommended publications
  • Magic Information Systems Chooses Pervasive Software's SQL Database
    Solutions for the Information Project Team • www.dbta.com Volume 16, Number 7 •July 2002 Magic Information Systems Chooses Pervasive Software's SQL Database By Walt Jordan ability to support multiple cur- parallel transactional applica- having to invest much time or Magic Information Systems rencies, landed costs tracking tion with the SQL relational energy tuning the database. has been creating database and others. And though it was database. Now, Btrieve is And neither have his clients. applications since 1989. originally geared to Windows, embedded into Pervasive's SQL The Magic RAD tool is data- Originally called Hartronix, a the company ported it to Unix database. base independent. All the value-added reseller, the com- and other platforms as well. That combination solved reporting is generated by pany created a management But new challenges accompa- Rapoport's problems. "With Crystal Reports Writer from package for wholesale distribu- nied the success. "It was a good Pervasive wrapping Btrieve in a Seagate. "That is our operating tion and light manufacturing product, but maintaining it and relational database and Magic environment, and Pervasive is called Accountware. Over time, customizing it was a headache," as the rapid application devel- at the core," Rapoport said. the Accountware application Rapoport said. "We began look- opment tool, we found that we Interestingly, customers are grew to generate 80 percent of ing for a tool that would let us really didn't need to go any fur- becoming more interested in the overall business. As a get away from the 800,000 lines ther," Rapoport said. what is the underlying data- result, the company was con- of code that we had written in In fact, using Pervasive SQL base.
    [Show full text]
  • Accessing Zen/PSQL Data from ODBC Or Other Applications
    Accessing Zen/PSQL Data From ODBC Or Other Applications A White Paper From For more information, see our web site at http://www.goldstarsoftware.com Accessing Zen/PSQL Data From ODBC (or Other Applications) Last Updated: 02/23/2021 When it comes to "frequently asked questions", this one takes the cake, to be sure. It seems that people are used to databases which provide ODBC access natively (such as FOXPro, Access, etc.) and get confused when they cannot access their own application data immediately. Then, they start “Btrieve-bashing” because they can't get their data out. This document was created to provide some explanation as to what the issues are when it comes to ODBC access and your data, whether it be stored in a current Actian Zen database engine, or one of the older ones, including Actian PSQL, Pervasive PSQL, Pervasive.SQL, and even Btrieve. The material is taken mostly from the PSQL Service & Support classes provided by Goldstar Software. Database Engine Type & ODBC Drivers The first question we have to deal with is the availability of ODBC drivers. If you have a newer engine, then you can skip this section entirely. If you have an older engine, though, then you should read on. Old DOS applications may be using Btrieve 5.x or older for DOS, 5.x for Windows, or even Btrieve 5.x or 6.10 for NetWare. These engines do NOT contain an ODBC driver and will not support 32-bit ODBC access. (MS Access 2.0 had limited support for Btrieve 6.10, but only from 16-bit Windows applications.) If this is the case, then you will need to purchase a new database engine to support this access.
    [Show full text]
  • Technical FAQ: Btrieve – Microsoft SQL Server Migration And
    MERTECH DATA SYSTEMS, INC. 18503 Pines Boulevard, Suite 312 | Pembroke Pines, FL 33029 | USA Tel: (954)585-9016 | Fax: (866)228-1213 www.mertechdata.com Contents Introduction What objects are created on MSSQL? Are there recommended database settings? Technical FAQ: Btrieve – Microsoft SQL Server Which files are used? Migration and Deployment What roles and privileges are required? Can I determine the number of licenses used? How do I install the client? What things should I look for in my code? How do I know if I am targeting Btrieve or SQL? Can the application control login? Can the application execute queries? How do I handle sensitive data? How do I look at the data on the server? Contact Information © 2014 Mertech Data Systems, Inc. All Rights Reserved. This document is for informational purposes only. Mertech makes no warranties, expressed or implied, in this document. Btrieve and Pervasive.SQL are registered trademarks of Pervasive Software, Inc. Mertech Data and Btr2SQL are trademarks of Mertech Data Systems, Inc. Microsoft, SQL Server and Windows are registered trademarks of Microsoft Corporation. Other trademarks and trade names mentioned herein are the property of their respective owners. Introduction Mertech’s Btr2SQL database migration tool smoothly migrates a Btrieve database to a Microsoft SQL Server back-end. The migration process creates the required tables and indexes and copies data to the MSSQL server. This white paper answers frequently asked questions about the migration and deployment process. What objects are created on MSSQL? Indexes If a table has at least one index that is not unique and the table does not have a primary key defined in the DDFs: The MDS_RECNUM column is a primary key.
    [Show full text]
  • Btrieve 12 Release Notes General Release – December 2015
    6/23/2017 Btrieve 12 Release NotesGeneral Release – December 2015 Btrieve 12 Release Notes General Release – December 2015 Contents Welcome to the General Release of Btrieve 12. These release notes cover the following topics: • Overview • PlaĔorms Supported • Product Authorizaĕon • New Features and Enhancements • Installing Btrieve • Installing Btrieve 12 • JRE Components Included in Installaĕon • Known Issues • Usage Notes • Technical Support This document is included in your Btrieve installaĕon but may be updated a├er the release. Its latest version is always posted on the Acĕan PSQL website. Overview PlaĔorms Supported This release has been successfully tested on the following operaĕng systems in their 32‐ and 64‐bit ediĕons: • Windows 10 • Windows Server 2012 • Windows 8 • Windows Small Business Server 2011 • Windows Server 2008 R2 • Windows Foundaĕon Server 2008 R2 • Windows 7 • Windows Small Business Server 2008 • Windows Server 2008 http://www.pervasive.com/portals/55/documents/btrieve/readme_btrieve12.htm 1/5 6/23/2017 Btrieve 12 Release NotesGeneral Release – December 2015 • Windows Vista We recommend updaĕng all operaĕng systems to their latest service packs. Product Authorizaĕon Btrieve 12 comes with a trial key for evaluaĕon installaĕons. These trial keys have limits of 5 users and 30 days. If you install Btrieve 12, you are required to authorize the product either by entering a license key during installaĕon or by using the License Administrator uĕlity a├er installaĕon. Authorizing Btrieve 12 during installaĕon requires an Internet connecĕon. To authorize a├er installaĕon, read about license administraĕon in Btrieve User’s Guide. License Authorizaĕon Access Through Proxy Servers We recommend that you use Windows Internet Explorer to configure proxy servers.
    [Show full text]
  • Determining Your Pervasive, Actian, PSQL Or Btrieve Engine Version
    Determining Your PSQL Engine Version A White Paper From For more information, see our web site at http://www.goldstarsoftware.com Determining Your PSQL Engine Version Last Updated: 12/18/2018 It is very common for people to know that they are using the Btrieve or Pervasive PSQL, or Actian Zen database engine, but to not know exactly which version they are using. Moreover, the list of related files is often a mystery, especially for older versions, and some users are simply without a clue as to what modules are part of the database and what are not. This paper was created so that someone could locate the PSQL-related files on their workstation or server and determine the exact version, including user count, where appropriate. NetWare Server Engines With NetWare servers, it is possible to have any version of Btrieve from 5.x all the way through Pervasive PSQL v9. Many users see the version reported from BREQUEST and assume that this is their Btrieve version -- it just isn't so! You must query the server to determine exactly which version of BTRIEVE.NLM you have. On older versions of NetWare, you can do this with the "MODULES" command, which lists all the loaded modules on the server. Then, watch for the BTRIEVE.NLM to scroll by. For NetWare 4.11 and above, you can use the command "MODULES BTR*" to list only those modules that start with "BTR", which will save some searching. With the release of Pervasive.SQL 7, Pervasive Software started including the SQL engine "in the box" with the Btrieve engine.
    [Show full text]
  • Btrieve Data File Maintenance
    Btrieve Data File Maintenance A White Paper From For more information, see our web site at http://www.goldstarsoftware.com Btrieve Data File Maintenance Last Updated 04/07/2010 Btrieve data files do not require periodic maintenance, unlike some of the more administration-intensive database products out there. In fact, the majority of Btrieve files sit happily for their entire lives without ever having to be touched outside of the program that creates and accesses them. As a result, using BUTIL or some of the other utilities is relegated to the programmers in the world, since these are the people who can benefit most by their use. In fact, there are only two cases where file maintenance for a normally-running Btrieve database may be required. First, if the developer makes a change to the application that requires changing the size of the record in a file, a manual BUTIL rebuild process may be utilized. Oftentimes, the developer will create a version upgrade utility, or some other process to perform this function automatically. If this is done from the workstation, however, a long time may be needed to convert large files. It may be desirable to manually perform the process from the server instead. Second, if a database is very large and the application purges (deletes) a large number of records, you may wish to give some of the newly freed up storage space back to the operating system. This is important because Btrieve does not release empty data pages back to the operating system -- it just marks them as free pages for future use by the engine.
    [Show full text]
  • DOS Requester 1.02
    chapter 1 About the NetWare DOS Requester Overview This chapter introduces and briefly describes the NetWare DOS Requester. The following topics are covered in this chapter. Topic Page The New Workstation Software Components 1 Features of the NetWare DOS Requester 2 About the NetWare DOS Requester 3 The New Workstation Software Components The key components of the NetWare DOS and Windows environment are four terminate-and stay-resident (TSR) programs: ◆ LSL™ (Link Support Layer™) ◆ A LAN driver (example: NE2000™) ◆ IPXODI (Internetwork Packet Exchange™ Open Data Link Interface) ◆ NetWare DOS Requester (VLM.EXE and associated.VLM files) The NetWare DOS Requester replaces NETX. Almost all activity at the workstation now involves these four components. Figure 1-1 shows the difference between the NETX and the NetWare DOS Requester architectures. About the NetWare DOS Requester 1 Figure 1-1 NETX DOS Requester Comparison between NETX and NetWare DOS Requester NETX NETX.VLM DOS NetWare DOS Requester IPXODI DOS IPXODI Link Link Support Support Layer Layer LAN LAN driver driver Network Network board board Features of the NetWare DOS Requester The NetWare DOS Requester provides several improvements over NETX. It does the following: ◆ Provides a modular architecture that has advantages for current and future applications. ◆ Takes advantage of memory-swapping technology and DOS redirection capability. ◆ Includes Packet Burst protocol and Large Internet Packet (LIP). ◆ Supports the installed base of NetWare users by providing backward compatibility with NETX. ◆ Supports NetWare Directory Services™ in NetWare v4.0. 2 NetWare Workstation for DOS and Windows About the NetWare DOS Requester The NetWare DOS Requester consists of a number of files that provide NetWare support for a DOS workstation.
    [Show full text]
  • Btrieve Developer's Journal, Call Responsible for Getting BDJ out to You, and I Carolyn Lighty, Advertising Manager, at (800) Don’T Have Room to Thank Them All
    Btrieve® Winter 1995 Developers Journal Vol. III No. 4 THE INDEPENDENTSpecial Feature: SOURCE OF NEWS AND INFORMATION ABOUT BTRIEVE AND SCALABLE SQL DevelopmentSurfing Tools in Roundup January: Hot Destinations for Developers on the Web BTI AND OTHER SOFTWARE VENDORS TURN TO THE INTERNET TO GET THE WORD OUT Appearance of these web pages, like the applications of Btrieve itself, ranges By Jim Kyle, News Editor Btrieve Technologies Inc. created a web from deceptively simple to extremely page, in addition to its support forum on complicated. A few sites, such as that of For the past several months, its been CompuServe. A number of other firms did BTI, provide magnificently detailed almost impossible to pick up any the same. When we began surveying the graphics. Unfortunately, the more publication (technical or otherwise) net to see how many Btrieve-related sites complex the graphic that finally appears, without finding at least one article dealing we could locate, most of the names best- the longer the time required to download with the information superhighway. It known to Btrieve users and developers the data so you can see it! Some of the appears that The Internet has surpassed popped out immediately. more striking pages, such as that from even client/server as the buzzword of The three dozen or so sites in the the Canadian consulting firm ThinkNet, the year! accompanying list almost certainly form show an awareness of this fact; they Well, we at the Journal are no only a sample of those in existence. Weve combine relatively simple graphic exception to this rule.
    [Show full text]
  • Novell Netware®
    Novell Confidential Manual (ENU) 15 April 2004 Novell NetWare® 6.5 www.novell.com NOVELL STORAGE SERVICESTM July 2, 2004 ADMINISTRATION GUIDE Novell Confidential Manual (ENU) 15 April 2004 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside. Copyright © 1993-2004 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher. U.S. Patent No. 5,157,663; 5,349,642; 5,455,932; 5,553,139; 5,553,143; 5,572,528; 5,594,863; 5,608,903; 5,633,931; 5,652,854;
    [Show full text]
  • Btrieve Error Codes 3000 - 3099 ← Pervasive PSQL Microkernel Router Status Codes
    Btrieve Error Codes 3000 - 3099 ← Pervasive PSQL MicroKernel Router Status Codes This section lists the status codes you can receive from the MicroKernel router, which receives requests from the Btrieve requesters and routes them to the correct version of the MicroKernel. 3000: The MicroKernel router encountered a memory allocation error The MicroKernel router could not internally allocate memory. Check the Pervasive Event Log (PVSW.LOG) for more information. 3001: Local access is unavailable to the MicroKernel router A call to the MicroKernel failed. This is most likely the result of an incorrect configuration. For example, if the MicroKernel is unavailable because of configuration settings and the file to be opened is local, then the MicroKernel router returns this status code. 3002: The MicroKernel router resource DLL is unavailable The MicroKernel resource DLL is either missing or incompatible with the current version of the router. If this happens, the MicroKernel reverts to its default settings and continues to run. Check the Pervasive Event Log (PVSW.LOG) for more information. 3003: The MicroKernel router detected an incompatible network component The networking services component is not compatible with this version of the MicroKernel router. The most likely cause is that the Networking services DLL has been replaced by an older version. Check the Pervasive Event Log (PVSW.LOG) for more information. 3004: The MicroKernel is not responding to the MicroKernel router The MicroKernel is not responding to requests from the MicroKernel router. Verify that the MicroKernel is running. 3005: The MicroKernel router encountered an operating system error The MicroKernel router encountered an unexpected error from the operating system, such as a shared memory failure.
    [Show full text]
  • Watcom Linker
    Watcom Linker User's Guide Edition 11.0c Notice of Copyright Copyright 2000 Sybase, Inc. and its subsidiaries. All rights reserved. No part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without the prior written permission of Sybase, Inc. and its subsidiaries. Printed in U.S.A. ii Preface The Watcom Linker User's Guide describes how to use the Watcom Linker under DOS, OS/2, Windows 95, Windows NT and QNX. The Watcom Linker can generate executable files that run under DOS, FlashTek's DOS extender, Phar Lap's 386|DOS-Extender and TNT DOS extender, Tenberry Software's DOS/4G, Microsoft Windows 3.x, Microsoft Windows NT, Microsoft Windows 95, IBM OS/2, QNX, and Novell's NetWare 386 operating system. The Watcom Linker can also generate ELF format executable files for those systems that will support ELF. The Microsoft Response File conversion utility, MS2WLINK, is also described in this book. Acknowledgements This book was produced with the Watcom GML electronic publishing system, a software tool developed by WATCOM. In this system, writers use an ASCII text editor to create source files containing text annotated with tags. These tags label the structural elements of the document, such as chapters, sections, paragraphs, and lists. The Watcom GML software, which runs on a variety of operating systems, interprets the tags to format the text into a form such as you see here. Writers can produce output for a variety of printers, including laser printers, using separately specified layout directives for such things as font selection, column width and height, number of columns, etc.
    [Show full text]
  • Entering Your Pervasive PSQL V8/V9 Database Engine License
    Entering Your Pervasive PSQL V8/v9 Database Engine License A White Paper From For more information, see our web site at http://www.goldstarsoftware.com Entering Your Pervasive PSQL V8/v9 Database License Last Updated: 12/18/2018 The Pervasive database engine is licensed via an electronic license key which is provided with the engine license. For versions 8.x and 9.x, this license is a 24-character (text) keycode that contains information about the product version, platform, and user count. In order to be properly recognized by your system, the license key must be provided to the software. This is done via the License Administrator tool. Using the GUI License Administrator To use the graphical License Administrator tool, follow these simple steps: 1) Go to the physical server itself. Please note that you can NOT do the install or basic management processes from a Remote Desktop (RDP) or Terminal Services session. 2) On the server, select Start/All Programs/Pervasive/Other Utilities/License Administrator. The following box will appear. 3) Enter your license keycode into the 4 boxes provided (each of 6 characters). 4) Click on Apply License Key to enter your license key. You should receive a message about the license being applied successfully, and the License Administrator should show the new license. Using the Command Line License Administrator To use the graphical License Administrator tool, follow these simple steps: 1) Go to the physical server itself. Please note that you can NOT do the install or basic management processes from a Remote Desktop (RDP) or Terminal Services session.
    [Show full text]