This is the README file for SQLMagic release 3.35, build 1. This product incorporates FASTMM, which is copyright Professional Software Development / Pierre le Riche. The FASTMM code is released under the Mozilla Public License 1.1 (MPL 1.1, available from http://www.mozilla.org/MPL/MPL-1.1.html). The source code for FASTMM is available here: http://fastmm.sourceforge.net *IMPORTANT NOTE* To upgrade from a version of SQLMagic prior to release 3.30, you will need a new license. Release 3.30 licenses are still valid with release 3.35. Contents ======== 1 System Requirements. 2 Installation 3 Configuration Information. 4 Changes made in release 3.35. 5 Changes made in release 3.34. 6 Changes made in release 3.33. 7 Changes made in release 3.32. 8 Changes made in release 3.31. 9 Changes made in release 3.30. 10 Changes made in release 3.24. 11 Changes made in release 3.23. 12 Changes made in release 3.22. 13 Changes made in release 3.21. 14 Changes made in release 3.20. ============================================================================ 1 System Requirements =================== PC Windows XP or Windows 2000 Professional (SP2 or later). NonStop System Itanium H series, Himalaya S series (G03 or later), or K series (D40 or later). 2 Installation ============ SQLMagic consists of client components, which are installed on your PC, and server components which are installed on a HP NSK system. There are four SQLMagic setup programs, which can be downloaded from the merlon.com web site: 1 The full SQLMagic release (SQLMnnn.EXE) This installation includes all of the SQLMagic components, namely the SQLMagic client, the SQLView client, and the NSK server components. 2 The SQLMagic client program (SQLMCnnn.EXE) This installation only includes the SQLMagic client. 3 The SQLView client program (SQLVnnn.EXE) This installation only includes the SQLView client. 4 The SQLMagic server installer (SQLMSnnn.ZIP) This ZIP file contains the server installer program SQLMPACK. Note that in the name of these setup programs, the characters "nnn" represent the release number. For example, the 3.14 files are called SQLM314.EXE, SQLMC314.EXE, SQLV314.EXE, and SQLMS314.EXE. Installation of PC components ------------------------------- To install the SQLMagic client, run either the full release setup program, or the SQLMagic client setup program. You will be prompted to supply a setup password which is available by sending an email to sales@merlon.com. To install the SQLView client, run either the full release setup program, or the SQLView client setup program. The SQLMagic client must be installed on each PC which will run SQLMagic. The SQLView client must be installed on each PC which will run SQLView. To uninstall SQLMagic --------------------- 1 From the Windows Start menu, select Settings, Control Panel. 2 Double click on the Add/Remove Programs icon. 3 Select SQLMagic from the list of applications. 4 Click Add / Remove. Installation of NSK components ------------------------------- The server components need only be installed once. They are contained in a self-extracting archive called SQLMPACK.100. This file is placed in the SQLMagic directory (on your PC's hard drive) by the Full Release setup program. You can also obtain a copy by downloading the server-only release file SQLMSnnn.ZIP, and unzipping the file from there. Please note that if you install on a subvolume that already contains SQLMagic, all processes running from objects on that subvolume must be stopped to allow for the replacement of object files. The existing SQLMagic configuration and database will be preserved during installation. To install the server components: a) Copy the SQLMPACK.100 file from the PC's hard drive to a subvolume on the NSK system. The NSK file should be named SQLMPACK. NOTE: SQLMAGIC creates audited SQL tables in the installation subvolume. Therefore, you should install SQLMAGIC on a volume that supports TMF audited files. The SETUP program will display an error and terminate if you attempt to install SQLMagic on a non-audited volume. Use FTP, IXF, or some other file transfer program. Note that this is a binary file, and you must use a BINARY transfer method. b) Copy the LICENSE file you received from Merlon onto the same subvolume as SQLMPACK. This is an ASCII file, you should transfer the file in ASCII mode. It MUST be called LICENSE when copied to the NSK system. c) Use TACL to logon to the NSK system. Make the SQLMagic subvolume (which you selected in step a) the current subvolume. d) Change the SQLMPACK file's file code to 100, for example FUP ALTER SQLMPACK, CODE 100 e) Run the SQLMPACK program, and follow the instructions displayed on the screen. f) If you elected to use static servers, run the SMSTART macro to start the SQLMagic servers. If you elected to use dynamic servers, change the PORTCONF file to add an entry for the SQLMS program. (See configuration info below). 3 Configuration Information. ========================== In order to configure SQLMagic, you will need to know the following: a The name of a TCP/IP process running on the NSK system that can be used to connect from your PC. The default is $ZTC0, you may use a different value on your system. If Parallel TCPIP is installed on your system, use the name of a TCPSAM process instead of a TCP/IP process. Check with your system administrator. You will be asked for this name by the NSK SETUP program, which is started by SQLMPACK. b The TCP/IP address used by this TCP/IP (or TCPSAM) process, for example 192.168.1.2 You will be asked to enter this value when you first start the SQLMAGIC program on your PC. c TCP/IP port numbers which are available for use by SQLMagic. Port numbers are used to make a connection between a PC client and an SQLMagic server. SQLMagic servers can be configured to be static or dynamic. For Static servers, you will need one port number for each concurrent user of SQLMagic or SQLView, plus 1 more. These must be consecutive numbers. For Dynamic servers, you will need one port number. This port number must be mapped to the SQLMagic server program (SQLMS) in the TCP/IP PORTCONF file. (See your system administrator for help in updating this file). Static servers provide better performance, but run all the time. Dynamic servers are started as needed, they will be stopped when the PC disconnects. Note that the port numbers you choose must not be used by any other applications that share the same TCP/IP process with SQLMagic. Normally, you should use port numbers greater than 1023. (To find out which port numbers are in use, use the SCF STATUS PROCESS command for the TCP/IP process you plan to use). You will be asked to select either Static or Dynamic servers by the NSK SETUP program. You will be asked to select a range of port numbers by the NSK SETUP program, and also when you first start the SQLMAGIC or SQLVIEW program on your PC. (Of course, the numbers you enter must be the same in each case). d The SUPER ID password. This is required if you wish to use the COPY / PASTE statistics feature in SQLMagic. This feature allows you to copy SQL statistics from one table or index to another. If you wish to use this feature, the SQLMSL and COPYSTAT programs in the SQLMagic subvolume must be licensed. To license these programs, you must be logged on as SUPER.SUPER. This is the only time you need the super id password. 4 Changes made in release 3.35 ============================ a A number of memory leaks were corrected, including leaks that occurred when selecting or expanding the partitions folder for a table or index (SM45000770). b Memory management improvements were made to reduce the amount of virtual memory used in certain situations (SM45000770). c If an attempt to create or write to an SQLMagic INI file fails, the file IO error is displayed (SM45000770). d Response time on expansion and summary retrieval of partition information has been improved (SM45000771). e A number of defects have also been repaired. 5 Changes made in release 3.34 ============================ a Replace duplicates no longer causes a failure on imports to tables including a SYSKEY (SM45000751) b Data tab support has been corrected to handle the "," decimal separator (SM45000752). c Script generation for catalogs containing partitioned tables no longer create duplicate protection view definitions (SM45000754). d The 128 column limit on copy/paste statistics has been removed (SM45000755). e When copying statistics from a catalog containing a large number of objects, selection of the destination catalog returns a "no objects found" message. This has been corrected (SM45000756). f Error 13s have been corrected on catalog copy of statistics on systems with seven character names (SM45000757). g Cleanup of execution plans is now split into multiple TMF transactions to prevent timeouts on large databases (SM45000760). h The XPLA no longer generates extraneous TMF aborts to EMS on completion (SM45000761). i Reload can now simultaneously reload all partitions of a table or index (SM45000762). j The -p option has been added to the SCRIPT utility to include PHYSVOL when creating SMF objects (SM45000767). 6 Changes made in release 3.33. ============================= This release contains the following new features: a The CURRENT token (indicating the current date/time) is now allowed on PC import of date/time columns (SM45000747). b Import is now supported for protection views (SM45000749). 7 Changes made in release 3.32. ============================= This release contains the following new features: a Copy/Paste of statistics has been enhanced to include secondary partitions (SM45000722) b Latency on retrieval of partition information spanning multiple systems has been reduced (SM45000725) c A number of defects have also been repaired. 8 Changes made in release 3.31. ============================= This release contains the following new features: a Partitions of tables and indexes are now displayed in partition rather than disk order (SM45000628/SM45000682). b An additional function has been added to the Data menu to close all user tables currently opened by the current SQLMagic session (SM45000631). c Multiple statistics from catalog or project tables may now be copied and pasted to a different catalog or project in a single step (SM45000641). d The rows of a summary tab may now be copied to the Windows clipboard in CSV format (SM45000648). e NULL key field handling on partition management has been corrected (SM45000687). f The maximum size limit on individual partitions of a table being repartitioned has been corrected to accommodate format 2 tables (SM45000688). g SQLMagic no longer intermittently misses programs when generating explain plans for all programs in a catalog (SM45000691). h The criteria for SQLMagic queries may now include subqueries (SM45000692). i The SQLMagic help subsystem has been enhanced (SM45000693). j An option has been added to clean up explain plan history by number of plans rather than by date (SM45000694). k SQLMagic now allows deferred creation of constraints (SM45000695). 9 Changes made in release 3.30. ============================= IMPORTANT NOTE FOR WINDOWS XP AND 2000 USERS: As of this release, SQLMagic stores its client configuration (*.INI files) and session connection information (*.SSP files) in \Documents and Settings\\Application Data\MERLON\SQLMagic, rather than in the SQLMagic installation directory (default \Program Files\Merlon\SQLMagic 3.31) For existing clients, please move SQLMagic.INI, all files of type .SSP, as well as the \DATACFG, \QUERYCFG, \SUMMTCFG, \TABCFG subdirectories to the appropriate directory to maintain client configuration and to ensure existing sessions are still available. IMPORTANT NOTE FOR EXISTING USERS: If you wish to use separate report generation subvolume (c below) when upgrading the SQLMagic server in a previously defined environment, but do not wish to alter the SQLMagic configuration, Edit the SQTINI file and add the line EXSUBVOL=$vol.subvol to the [DB] section prior starting SQLMagic with either dynamic or static servers. This release contains the following new features: a SQLMagic has been certified for use on the Itanium platform (H-Series). b A new function has been added to the data tab allowing a selected row to be "cloned" - that is, a new row will be inserted with the column values of the selected row, which can then be modified before applying the insert (SM45000635). c A separate subvolume can be specified in SETUP as the location in which SQLMagic stores working data for report generation (SM45000639). d When exporting to or importing from ODBC data sources, a table owner may now be specified (SM45000640). e A number of defects have also been repaired. 10 Changes made in release 3.24. ============================= This release contains the following new features: a A new tool, script, has been added that will generate text defining SQL objects and their subordinates. This may be run from TACL or the Tools menu. b SQLMagic now automatically determines the previous and next partitions for one-way moves and merges, guaranteeing that adjacent partitions will be used. c "Create Like" for catalogs now supports subvolume-only mapping (maintaining disc names) d User-defined SYSKEY columns are now supported. e On the data tab, next and previous record buttons have been replaced with next and previous page to improve browsing. f The data tab line numbers are now optional via Show/Hide Row Numbers on the View menu. g SQL "cost" limits have been removed from the data tab on single tables, allowing users with limited access to perform simple browses. h When a project object is selected, the usages tab now includes references to and from objects outside of the project. i Cells in the Data tab may now be selected using the mouse and copied to the Windows clipboard or printed. j A constraints folder has been added at the catalog level to summarize all constraints defined within the catalog. k SQL comments are supported for collations, columns, constraints, indexes, tables and views. l The following enhancements have been added to the table repartition wizard: - An option has been added to set the initial volume list to the same as the selected table's current partition structure. - Remote discs may be selected as partitions. - Extent sizes may be specified rather than defaulting to the primary partition extents. - An empty primary partition may be specified. m Views may now be closed, which closes all underlying tables. n Aggregate EOF has been added to table and index properties. o Updating statistics for all tables in a catalog or project has been enhanced as follows: - The update may be run as a background task, rather than just generating a script. - Empty tables may be skipped. - You may specify that only tables with no statistics will be included. p The databases' summary tab may now be sorted by subvolume or file name. q Local system names may optionally be suppressed on the text tab. r A task manager icon has been added to the lower right corner of the client that reflects the state of the latest requested background task. s On Windows XP and Windows 2000, ini and session files will be stored in the user's application data path (under \Merlon\SQL Magic), rather than the program file directory. t A number of defects have also been repaired. 11 Changes made in release 3.23. ============================= This release contains the following new features: a SQLMagic is now compatible with XYPro Technology Corporation's XYGATE/AC product. 12 Changes made in release 3.22. ============================= This release contains the following new features: a OSS program management is included (SQL/MP table access only). b NSK browse of disk volumes appears in alphabetical, rather than logical device, order. c Context for the text editor tool is maintained separately for each window, allowing multiple text editors to be run simultanously without impacting each other's default files. d Data tab ordering is supported for protection views as well as tables. e Queries may be saved as views from the query builder tab. f An automatic join option has been added to associate multiple tables in a query. g Confirmation has been added for SQLMagic deletion of objects. h A purgedata option has been added to the object menu to support removal of all the rows in a table or table partition. 13 Changes made in release 3.21. ============================= This release contains the following new features: a Task manager retrieval of information on large numbers of tasks has been made faster. b An View Change Script function has been added to the Data Tab. This generates an SQLCI script of any changes that have been made to records within the data tab. c Cancelling of the addition of new Views in the databases tab now clears the "change arrows" that indicate a change is pending. d Support for native programs added to the Find tool, recompile and explain functions. e The cursor hourglass will now be cleared when completing the Explain All wizard. f Compiler options and the Create Table wizard are no longer available when a user without management access opens a project. g When switching projects, the usages tab was occasionally displaying the previously selected object rather than the object selected within the new project. h Reusing the same SQLMS to perform a project import objects function with related objects no longer causes an SQLMS failure. i Error conditions on project attributes no longer cause the SQLMS to loop. j Large lists of views were causing message overruns, resulting in invalid data appearing when the Views folder was selected. This has been corrected. k A limit of 2200 project members has been enforced due to Guardian DEFINE limitations. l Upon completion of an Add or Import objects to a project, the displayed properties of the project no longer disappear. m Intermittent error 12s on the SQTAZ and SQTBG files on initiation have been resolved. n Defines present when SQLMS are no longer propagated and thus will no longer override project defines. o "Recompile all" programs now functions correctly from within a project. p Project names set to lower or mixed case are now upshifted. 14 Changes made in release 3.20. ============================= This release contains the following new features: a You can now organize objects into Projects. Objects within a project are identified using define names instead of Guardian file names. b Three new attributes have been added to user profiles. Browse catalogs, Create Projects, and Open Projects. Using a combination of Projects and the new security attributes you can restrict the SQL objects to which a user has access. c Queries developed within a project can use define names to identify tables and views. A query designed in one project can be executed within another project provided the tables and views are compatible in each project. d SQLView can access tables and queries within a project. e SQLView users can be restricted to accessing tables, views, and queries within one or more projects. f The Configuration tab no longer appears in the left hand pane of the main window. To specify default SQL compiler options select Default Compiler Options from the Object or Project menus. g The server SETUP program now allows you to specify the subvolume where the SQLMagic database files are located. h A number of defects have also been repaired.