1 StreamServe Persuasion SP5 Microsoft SQL Server Database Guidelines Rev A
2 StreamServe Persuasion SP5 Microsoft SQL Server Database Guidelines Rev A STREAMSERVE, INC. ALL RIGHTS RESERVED United States patent #7,127,520 No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of StreamServe, Inc. Information in this document is subject to change without notice. StreamServe Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in this book. All registered names, product names and trademarks of other companies mentioned in this documentation are used for identification purposes only and are acknowledged as property of the respective company. Companies, names and data used in examples in this document are fictitious unless otherwise noted. StreamServe, Inc. offers no guarantees and assumes no responsibility or liability of any type with respect to third party products and services, including any liability resulting from incompatibility between the third party products and services and the products and services offered by StreamServe, Inc. By using StreamServe and the third party products mentioned in this document, you agree that you will not hold StreamServe, Inc. responsible or liable with respect to the third party products and services or seek to do so. The trademarks, logos, and service marks in this document are the property of StreamServe, Inc. or other third parties. You are not permitted to use the marks without the prior written consent of StreamServe, Inc. or the third party that owns the marks. Use of the StreamServe product with third party products not mentioned in this document is entirely at your own risk, also as regards the StreamServe products. StreamServe Web Site
3 3 Contents About StreamServe repositories...5 Overview of StreamServe repositories...6 StreamServe Enterprise Repository... 7 Runtime repository... 8 StreamServe archive... 9 Web content repository Tools for handling StreamServe repositories...11 Installing StreamServe repositories...13 Hardware and software requirements...14 Software requirements Hardware requirements Server configuration Installing an SQL Server database...16 Selecting collation Creating StreamServe repositories...17 Checking StreamServe repositories...18 Adjusting StreamServe repositories...19 Estimating the sizes for databases and transaction logs Estimating the database size Estimating the transaction log size Creating new filegroups Placing log files on different disks Indexing Columns suitable for indexing Indexing columns in the runtime repository Indexing columns in the StreamServe archive Using ODBC script functions with StreamServe and 64-bit SQL Server...25 Uninstalling StreamServe repositories...26 Maintaining StreamServe repositories...27 Top jobs, input jobs and output jobs...29 Deleting expired jobs from the runtime repository...30 Job deletion process Prerequisites and recommendations Design Center configurations Job deletion schedule Scheduling StreamServers to delete jobs Scheduling Task Schedulers to delete jobs Scheduling the database to delete jobs Updating top job statuses in the runtime repository...37 Job status update process Recommendations... 38
4 4 Scheduling StreamServers to update job statuses Scheduling Task Schedulers to update job statuses Scheduling the database to update job statuses Running index maintenance Most fragmented tables Index maintenance process Prerequisites and recommendations Scheduling Task Schedulers to run index maintenance Creating a connection profile Scheduling the database to run index maintenance Monitoring jobs in the runtime repository Queries when monitoring jobs and job statuses Queries when monitoring delete performance Performing backup of StreamServe repositories Appendix A - Time scheduling syntax... 57
5 About StreamServe repositories 5 About StreamServe repositories This document provides an overview of how to install, maintain, and back up the StreamServe repositories running on Microsoft SQL Server. Intended audience This document is intended for developers, for example StreamServe consultants, who are also familiar with Microsoft SQL Server databases. The document also contains some information that may be of interest for a database administrator, for example information about the tables with the highest growth rate and how StreamServe jobs are deleted from the runtime repository. Information about third party products This document does not describe how to carry out configurations in third party products, for example in Microsoft SQL Server Management Studio. For such information, see Microsoft SQL Server Online Books. In this section Overview of StreamServe repositories on page 6. Tools for handling StreamServe repositories on page 11.
6 6 Overview of StreamServe repositories About StreamServe repositories Overview of StreamServe repositories StreamServe uses the following repositories: StreamServe Enterprise Repository. Runtime repository. StreamServe archive (for StreamStudio Collector). Web content repository (for StreamStudio Composition Center). Figure 1 Overview, StreamServe repositories and components For detailed information about the StreamServe components that interacts with the repositories, see the Control Center documentation.
7 Overview of StreamServe repositories 7 About StreamServe repositories StreamServe Enterprise Repository A StreamServe Enterprise Repository contains information about computers, StreamServe applications, and StreamServe application domains for a company or organization. You use one central enterprise repository, installed on a specified database server. If document types are used to categorize documents (for example, as invoices or orders), the enterprise repository is the master storage for these document types. The enterprise repository is also the master storage for the StreamStudio Composition Center template versions. All communication with the enterprise repository is handled via a management gateway. For example, Control Center communicates with the enterprise repository through a management gateway. Several management gateways can connect to the same enterprise repository. Figure 2 Communicating with the enterprise repository Default database name Default database user name StrsSER StrsSERAccess The user is used by the management gateway to access the specific enterprise repository.
8 8 Overview of StreamServe repositories About StreamServe repositories Runtime repository The runtime repository stores jobs and job related information in queues. The repository also contains security profiles and web access information for the StreamStudio web applications. Any persistent resources are also stored in the repository. For example, document definitions for StreamStudio Composition Center and exception rules to pause service-enabled StreamServe Messages. If you pause Messages, the Messages are stored in a separate queue called the Message storage. If you use the Document Broker Plus solution, the documents are stored in a queue called the Post-processing storage. Each StreamServe application domain requires a separate runtime repository. For example, one repository can be used for the StreamServe applications in development, and another for the StreamServe applications in production. One runtime repository is shared by all the applications in the application domain. The runtime repository is accessed by StreamServer, Archiver and Task Scheduler applications. When a StreamStudio web portal accesses the runtime repository, the requests and responses are sent through the service gateway. Figure 3 Communicating with the runtime repository Default database name Default database user name StrsData strsdataandqueues The StreamServer user. The user handles all StreamServe jobs and queues. strssecurity The service gateway user. The user handles the security related tables in the runtime repository, and the user authentication. strsweb The StreamStudio user. The users that you create in StreamStudio use this user to connect to the runtime repository.
9 Overview of StreamServe repositories 9 About StreamServe repositories StreamServe archive The StreamServe archive stores output documents and related metadata to be accessed from StreamStudio Collector. The StreamServe archive is optimized for searching and querying for documents. Each application domain can access one single StreamServe archive. However, one StreamServe archive can be shared by several application domains. An Archiver application transfers documents and related metadata from the runtime repository to the StreamServe archive according to schedules defined in Control Center. When the Collector user searches for documents in the StreamServe archive, all requests and responses are sent through the service gateway. Figure 4 Communicating with the StreamServe archive Default database name Default database user name Default repository name is the name that the Control Center user assigns when the StreamServe archive is created. For naming conventions, see the Control Center documentation. strsweb The user that Collector uses to access the StreamServe archive.
10 10 Overview of StreamServe repositories About StreamServe repositories Web content repository The web content repository is used by StreamStudio Composition Center for storing document definitions, resources, and rules during the document design phase. When a document definition is approved, the document definition (together with its resources and rules), is set to published in the runtime repository, and is available to the StreamServer application that produces the document. The web content repository communicates exclusively with Composition Center. Figure 5 Communicating with the web content repository Default database name Default database user name StrsWeb strswebcontent The user that Composition Center uses to access the web content repository.
11 Tools for handling StreamServe repositories 11 About StreamServe repositories Tools for handling StreamServe repositories When handling StreamServe repositories, it is recommended to use the tools, applications and scripts provided by StreamServe. Priority order Use the priority order below when deciding which tool to use: 1 Handle as much as possible using the configuration tools provided by StreamServe, for example in Design Center, in Control Center or in the StreamStudio web applications. 2 Use StreamServe Database Administration Tool only for tasks which cannot be performed in the configuration tools above. For more information about this tool, see the Database Administration Tool documentation. 3 Use the appropriate SQL Server tool, for example SQL Server Management Studio, only for tasks which cannot be performed using the StreamServe tools. When running external tools, you should primarily use the database scripts provided by StreamServe. For example, the StreamServe maintenance scripts referred to in this document.
12 12 Tools for handling StreamServe repositories About StreamServe repositories
13 Installing StreamServe repositories 13 Installing StreamServe repositories This chapter contains information on how to install and configure an SQL Server database for StreamServe and how to create the StreamServe repositories. In this section Hardware and software requirements on page 14. Installing an SQL Server database on page 16. Creating StreamServe repositories on page 17. Checking StreamServe repositories on page 18. Adjusting StreamServe repositories on page 19. Using ODBC script functions with StreamServe and 64-bit SQL Server on page 25. Uninstalling StreamServe repositories on page 26.
14 14 Hardware and software requirements Installing StreamServe repositories Hardware and software requirements The requirements below applies for the database server where you install the runtime repository and the StreamServe archive. In this section Software requirements on page 14. Hardware requirements on page 14. Server configuration on page 14. Software requirements Microsoft SQL Server For a complete list of supported versions, see the Supported platforms and software documentation. Hardware requirements 2 CPUs (minimum). 8 GB RAM (recommended minimum). It is recommended to run 64-bit SQL Server. 2 physical hard drives (the minimum requirement to store the database file and the transaction log on separate disks). It is recommended to use one of the following alternatives: Ultra SCSI (Small Computer System Interface) drives either in an SAN (Storage Area Network) environment or with high quality controller cards. If write caching disk controllers are used, these must be specifically designed for use in a data critical transactional database management system (DBMS) environment. SSD (Solid State Drive) disks, with the latest version of controller cards. To achieve fault tolerance, disk mirroring can be used. Server configuration Always place data on striped disks. Note that the most important is the maximum number of I/O:s per second, rather than the disk throughput. It is recommended to use RAID 1+0 for data files. Use the RAID hardware. Optimize your RAID controller by setting the read/write cache. You can use Windows Performance Monitor to discover the read/write ratio on your disk sub-system and help set the controller to the optimal value.
15 Hardware and software requirements 15 Installing StreamServe repositories Identify your access patterns and learn how your user access data depends on these patterns, on the indexes and on the read/write ratio. Based on this, you can decide whether to use multiple filegroups over multiple disks or just one single filegroup. Always store the transaction log on its own physical disk. Use the fastest available disks for the log files, and protect the log file disk.
16 16 Installing an SQL Server database Installing StreamServe repositories Installing an SQL Server database To be able to create the StreamServe repositories, there must be a SQL Server database available. In a production environment, you should use the Enterprise Edition of the database, Microsoft SQL Server. In a development and testing environment, you can use the Express Edition of the database, Microsoft SQL Server Express. Database configuration Configure the database according to the following: Enable TCP/IP. Specify Mixed Mode authentication. Specify a static TCP port number for accessing the database from all IP addresses. Note: Do not specify any dynamic TCP ports. Select to automatically create and update statistics. Select a proper collation. See Selecting collation below. Configure the database manually using the appropriate SQLServer tool, for example SQL Server Management Studio. For more information, see Microsoft SQL Server Books Online. Selecting collation A collation specifies rules for how character strings are sorted and compared, based on the norms of particular languages and locales. The default setting is the collation from the computer where SQL Server is installed. For example, if you install SQL Server in Finland, a Finnish collation is suggested. When you search for documents in StreamStudio Collector, the collation decides how the search result is sorted. If the collation is case sensitive, this also affects the search result. To avoid conflicts in different StreamServe repositories, you must set the same collation for the database where you install the runtime repository and for the database where you install the StreamServe archive. For information and recommendations, see Microsoft SQL Server Books Online.
17 Creating StreamServe repositories 17 Installing StreamServe repositories Creating StreamServe repositories You use StreamServe Control Center to configure and create the StreamServe repositories. You can either create the repositories directly in Control Center, or you can generate the database scripts in Control Center and then run the scripts using an external tool. For example, if the company security policy prevents Control Center from connecting to the database, or if you want to have full traceability of the repository creation. If Control Center is not available at all, you can carry out the corresponding procedures using the command line utilities. For more information, see the StreamServe Command line utilities documentation. Modifying repository users In the Control Center configurations, default repository users are suggested (see Overview of StreamServe repositories on page 6). It is recommended to change these users before creating the repositories. If Control Center is not available, the users can be modified directly in the template files, located in: Windows: <StreamServe installation>\applications\management\<version>\ etc\databasescripts\<version>\sqlserver\security UNIX: <StreamServe installation>/applications/managementgateway/ etc/databasescripts/<version>/sqlserver/security Prerequisites An SQL Server database must be installed before you create the StreamServe repositories, see Installing an SQL Server database on page 16. To create the StreamServe repositories See the Control Center documentation for detailed information on how to: Configure the StreamServe repositories. Create the StreamServe repositories directly in Control Center. Generate the database scripts in Control Center and then execute the scripts. Note: Since the scripts contains passwords, it is recommended to delete the scripts after you have created a repository.
18 18 Checking StreamServe repositories Installing StreamServe repositories Checking StreamServe repositories After creating a repository, it is recommended to check the repository. Check the log files for errors When creating a repository in Control Center, you can check a short version of the log file in Control Center, or you can open the full log file in a text editor from within Control Center. When executing the generated scripts using an external tool, you can use the logging features of this tool. Perform a sanity test You should always perform a sanity check to make sure the repository was created according to the configurations.
19 Adjusting StreamServe repositories 19 Installing StreamServe repositories Adjusting StreamServe repositories An enterprise repository that you create in Control Center can be used for development and testing purposes and may also be sufficient for a production environment. If specific security or performance requirements apply, you may have to adjust the enterprise repository to fit the actual conditions. A runtime repository and a StreamServe archive that you create in Control Center are sufficient for development and testing purposes. However, before using these repositories in a production environment, you most likely have to adjust the repositories to fit the actual conditions. For example, configure number of disks, filegroups, set the size and growth parameters of the database file and the transaction log file, and index columns. It is recommended to create the repositories using Control Center and then adjust the repositories using the appropriate SQL Server tool, for example SQL Server Management Studio. In this section Estimating the sizes for databases and transaction logs on page 19. Creating new filegroups on page 21. Placing log files on different disks on page 21. Indexing on page 22. Estimating the sizes for databases and transaction logs To prevent the disk drives from running out of size, it is recommended to specify a maximum size for both the database file and for the transaction logs. Underestimating the sizes of the database file and the transaction logs may result in automatic file growth and decreased performance. In this section Estimating the database size on page 20. Estimating the transaction log size on page 20.
20 20 Adjusting StreamServe repositories Installing StreamServe repositories Estimating the database size You can estimate the size of the database file based on the sizes of the database tables. You may be able to use the reporting function in the SQL Server tool to find out the actual size of each table. For example, the reporting function in SQL Server Management Studio. For more information, see Microsoft SQL Server Online Books. If the reporting function is not available in your SQL Server tool, you can use a script provided by StreamServe (dbo.alltables_spaceused.sql) to find out the actual sizes. See below. Note that a large table size does not necessary mean a large index size and vice versa. For example, in the runtime repository, the BinaryObject table has the biggest table size, but the Part table has biggest index size. If you have separated the data files into different filegroups, you must be aware of which files are the biggest ones. To find out the size of tables and indexes (SQL Server Express) 1 Log in to StreamShare and download the dbo.alltables_spaceused.sql script from: 2 Execute dbo.alltables_spaceused.sql to create the stored procedure dbo.alltables_spaceused. 3 Run the following command in the Query Analyzer to return the actual size of the tables and indexes: EXEC dbo.alltables_spaceused Estimating the transaction log size A general rule of thumb is that the transaction log size should be 20-25% of the database size. However, the smaller the size of the database, the greater the size of the transaction log, and vice versa. For example, if the estimated database size is 10 MB, you set the size of the transaction log to 4-5 MB. If the estimated database size is over 500 MB, you set the size of the transaction log to 50 MB.
21 Adjusting StreamServe repositories 21 Installing StreamServe repositories Creating new filegroups If you are running a non-raid disk set and the repository exceeds 100 MB, you may consider creating user-defined filegroups. Even if you are using a RAID system, you may still benefit from using filegroups since maintenance and backups can be scheduled at different times for different filegroups. Filegroups also enable a more effective backup strategy for large databases. If possible, it is recommended to use one disk for each filegroup. If you use a filegroup with many files within, make sure to spread them across several disk drives. Performance will be improved as long as the hardware is sufficient enough to optimize reading and writing to multiple disk drives concurrently. If indexes are placed into their own filegroup, the indexes and the data pages can be handled as separate read elements. If the associated filegroups are placed on separate physical disks, each disk can be read without interfering with the reading of the other. While an index is read in a sequential manner, the data can be accessed randomly, without the need for manipulating the physical arm of a hard drive back and forth from the index and the data. This can improve performance, and at the same time save the hardware. Reducing the disk queue length If the disk queue length (the number of data and log files in queue) on the SQL Server has an average above three, it is recommended to reduce the number of files and filegroups. You can use the Windows Performance Monitor and the Disk Queue Length counter to determine the appropriate number of data and log files. Once you have made the changes, you must continue the monitoring to ensure that your disk I/O is optimized. Placing log files on different disks Place the SQL Server log files on different physical disks than the data files. As a minimum requirement, the disks containing the log files must have sufficient disk I/O performance, since logging is very a write-intensive action.
22 22 Adjusting StreamServe repositories Installing StreamServe repositories Indexing For most tables, performance will be improved by indexing one or several of the columns. You should consider indexing columns that are used when filtering out a relatively small amount of rows from the tables. Indexing columns improves the speed of the data retrieval operations, but at the cost of increased storage space and slower writes. If a table is subjected to lots of inserts, increasing the number of indexes may have negative effect on the insert performance. You must take this into consideration when deciding whether to index or not. You index columns using the appropriate SQL Server tool, for example SQL Server Management Studio. For more information, see Microsoft SQL Server Books Online. In this section Columns suitable for indexing on page 22. Indexing columns in the runtime repository on page 23. Indexing columns in the StreamServe archive on page 24. Related topics Running index maintenance on page 42. Columns suitable for indexing The columns most suitable for indexing are usually the ones with user defined metadata, configured in StreamServe Design Center. Consult the end-users for information about which document types and which metadata are most frequently used and index the corresponding columns.
23 Adjusting StreamServe repositories 23 Installing StreamServe repositories Indexing columns in the runtime repository If the runtime repository contains Message storages or Post-processing storages, you should consider indexing these storages. Message storage When a Message is paused by an exception rule, the Message is stored in the Message storage. The Messages can then be invoked via service calls, for example web service calls from Ad Hoc Correspondence or Correspondence Reviewer. If a large amount of rows are stored in a Message storage, the service call performance may be improved by indexing one or several of the columns. The columns most suitable for indexing are the ones for user defined metadata (that is, configured with the Message context in Design Center). Example 1 Indexing a column in the Message storage In this example, an index is added to the column COL_Surname in a Message storage called cxmessage_letter. The column is indexed using the following command: CREATE INDEX ixlcol_surname ON stc.cxmessage_letter(col_surname); Post-processing storage When Document Broker Plus is used, the documents are stored in a Postprocessing storage. Metadata is used when searching for, retrieving, and postprocessing the documents. If a large amount of rows are stored in the storage, the search performance may be improved by indexing one or several of the columns. The columns most suitable for indexing are the ones for user defined metadata (that is, configured with the Post-processing context in Design Center). Example 2 Indexing a column in the Post-processing storage In this example, an index is added to the column COL_Surname in the Postprocessing storage called cxpost_letter. The column is indexed using the following command: CREATE INDEX ixlcol_surname ON stc.cxpost_letter(col_surname);
24 24 Adjusting StreamServe repositories Installing StreamServe repositories Indexing columns in the StreamServe archive When an end-user searches for documents in StreamStudio Collector, metadata is used as search criteria. If a large amount of rows are stored in the metadata tables, the search performance may be improved by indexing the columns for this metadata. The columns most suitable for indexing are the ones for user defined metadata (configured with the Archive context in Design Center). Example 3 Indexing metadata In this example, an index is added to the metadata column Customer Name for the document type table META_Letters. CREATE INDEX ixlcustomername ON stc.meta_letters("customer Name");
25 Using ODBC script functions with StreamServe and 64-bit SQL Server 25 Installing StreamServe repositories Using ODBC script functions with StreamServe and 64-bit SQL Server StreamServe Persuasion is running in 32-bit mode on both 32-bit (x86) and 64-bit (x64) versions of Microsoft Windows. In order for Persuasion s ODBC script functions to work properly with 64-bit versions of SQL Server, you must manually define a 32-bit ODBC data source (DSN) on the Persuasion host machine. Note: As an alternative, you can use the StreamServe DataDirect driver. To manually add a 32-bit DSN on 64-bit Windows 1 Open Odbcad32.exe, located in C:\Windows\SysWoW64. The 32-bit version of the Microsoft ODBC Data Source Administrator opens. 2 In the Data Source Administrator tool, create the DSN, pointing to the 64- bit SQL Server you want to use. Remember to test the DSN. 3 Use the new DSN in all ODBC-related scripts.
26 26 Uninstalling StreamServe repositories Installing StreamServe repositories Uninstalling StreamServe repositories When you uninstall StreamServe, you can choose to remove the StreamServe components. This uninstalls the files and services for the StreamServe repositories, but does not delete the repositories or the repository users. Under certain circumstances, you may want to drop a repository. For example, if you upgrade to a later StreamServe release, and want to create a new enterprise repository instead of upgrading the existing repository. When you drop a repository, all data within the repository is lost. Prerequisites Before dropping a repository, the following must be fulfilled: The StreamServe components must be removed. If not, the repository services are not deleted, resulting in a corrupt StreamServe installation. For information on how to uninstall and remove StreamServe components, see the Installation Guide. There must be no active sessions running against the repository. You can use the Activity Monitor in SQL Server Management Studio to find out if there are any active sessions. For more information, see the Microsoft SQL Server Online Books. To drop a repository You can drop the repository directly from SQL Server Management Studio. For more information, see the Microsoft SQL Server Online Books.
StreamServe Persuasion SP5 Oracle Database Database Guidelines Rev A StreamServe Persuasion SP5 Oracle Database Database Guidelines Rev A 2001-2011 STREAMSERVE, INC. ALL RIGHTS RESERVED United States patent
StreamServe Persuasion SP5 Control Center User Guide Rev C StreamServe Persuasion SP5 Control Center User Guide Rev C OPEN TEXT CORPORATION ALL RIGHTS RESERVED United States and other international patents
StreamServe Persuasion SP4 Installation Guide Rev B StreamServe Persuasion SP4 Installation Guide Rev B 2001-2009 STREAMSERVE, INC. ALL RIGHTS RESERVED United States patent #7,127,520 No part of this document
StreamServe Persuasion SP5 Ad Hoc Correspondence and Correspondence Reviewer User Guide Rev B StreamServe Persuasion SP5 Ad Hoc Correspondence and Correspondence Reviewer User Guide Rev B 2001-2010 STREAMSERVE,
StreamServe Persuasion SP5 Upgrading instructions Reference Guide Rev A Upgrading instructionsstreamserve Persuasion SP5 Reference Guide Rev A 2001-2010 STREAMSERVE, INC. ALL RIGHTS RESERVED United States
StreamServe Persuasion SP5 StreamStudio Administrator s Guide Rev B StreamServe Persuasion SP5 StreamStudio Administrator s Guide Rev B OPEN TEXT CORPORATION ALL RIGHTS RESERVED United States and other
StreamServe Persuasion SP5 Document Broker Plus User Guide Rev A StreamServe Persuasion SP5 Document Broker Plus User Guide Rev A 2001-2010 STREAMSERVE, INC. ALL RIGHTS RESERVED United States patent #7,127,520
Adobe LiveCycle Production Print ES2 Version 9.0 Installation Guide Rev A Adobe LiveCycle Production Print ES2 Installation Guide Rev A 2001-2009 STREAMSERVE, INC. ALL RIGHTS RESERVED United States patent
Interworks Interworks Cloud Platform Installation Guide Published: March, 2014 This document contains information proprietary to Interworks and its receipt or possession does not convey any rights to reproduce,
StreamServe Job Gateway User Guide 4.1.2 SP2 Rev A StreamServe Job Gateway User Guide 4.1.2 SP2 Rev A 2007 StreamServe, Inc. StreamServe is a trademark of StreamServe, Inc. No part of this document may
StreamServe Persuasion SP5 Supported platforms and software Reference Guide Rev A StreamServe Persuasion SP5 Reference Guide Rev A 2001-2010 STREAMSERVE, INC. ALL RIGHTS RESERVED United States patent #7,127,520
Using Microsoft Windows Authentication for Microsoft SQL Server Connections in Data Archive 2014 Informatica Corporation. No part of this document may be reproduced or transmitted in any form, by any means
FileMaker 12 ODBC and JDBC Guide 2004 2012 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker and Bento are trademarks of FileMaker, Inc.
DB Audit Expert 3.1 Performance Auditing Add-on Version 1.1 for Microsoft SQL Server 2000 & 2005 Supported database systems: Microsoft SQL Server 2000 Microsoft SQL Server 2005 Copyright SoftTree Technologies,
StreamServe Email User Guide 4.1.2 SP2 Rev A StreamServe Email User Guide 4.1.2 SP2 Rev A 2007 StreamServe, Inc. StreamServe is a trademark of StreamServe, Inc. No part of this document may be reproduced
Preparing a SQL Server for EmpowerID installation By: Jamis Eichenauer Last Updated: October 7, 2014 Contents Hardware preparation... 3 Software preparation... 3 SQL Server preparation... 4 Full-Text Search
Matisse Installation Guide for MS Windows 10th Edition April 2004 Matisse Installation Guide for MS Windows Copyright 1992 2004 Matisse Software Inc. All Rights Reserved. Matisse Software Inc. 433 Airport
Operating System Installation Guide This guide provides instructions on the following: Installing the Windows Server 2008 operating systems on page 1 Installing the Windows Small Business Server 2011 operating
OneStop Reporting 3.7 Installation Guide Updated: 2013-01-31 Copyright OneStop Reporting AS www.onestopreporting.com Table of Contents System Requirements... 1 Obtaining the Software... 2 Obtaining Your
FileMaker 13 ODBC and JDBC Guide 2004 2013 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker and Bento are trademarks of FileMaker, Inc.
Metalogix SharePoint Backup Publication Date: August 24, 2015 All Rights Reserved. This software is protected by copyright law and international treaties. Unauthorized reproduction or distribution of this
GFI MailArchiver for Exchange 4 Manual By GFI Software http://www.gfi.com Email: email@example.com Information in this document is subject to change without notice. Companies, names, and data used in examples
Jet Data Manager 2012 User Guide Welcome This documentation provides descriptions of the concepts and features of the Jet Data Manager and how to use with them. With the Jet Data Manager you can transform
Setting up an MS SQL Server for IGSS Table of Contents Table of Contents...1 Introduction... 2 The Microsoft SQL Server database...2 Setting up an MS SQL Server...3 Installing the MS SQL Server software...3
Sage 100 ERP Installation and System Administrator s Guide This is a publication of Sage Software, Inc. Version 2014 Copyright 2013 Sage Software, Inc. All rights reserved. Sage, the Sage logos, and the
StreamServe Persuasion SP4 Reference Guide Rev A StreamServe Persuasion SP4 Reference Guide Rev A 2001-2009 STREAMSERVE, INC. ALL RIGHTS RESERVED United States patent #7,127,520 No part of this document
Hardware, Software & System Requirements for SQL Server 2008 R2 Express Edition To get the overview of SQL Server 2008 R2 Express Edition, click here. Please refer links given below for all the details
SQL Server Setup Guide for BusinessObjects Planning BusinessObjects Planning XI Release 2 Copyright 2007 Business Objects. All rights reserved. Business Objects owns the following U.S. patents, which may
NETWRIX EVENT LOG MANAGER QUICK-START GUIDE FOR THE ENTERPRISE EDITION Product Version: 4.0 July/2012. Legal Notice The information in this publication is furnished for information use only, and does not
Release Notes for Websense Email Security v7.2 Websense Email Security version 7.2 is a feature release that includes support for Windows Server 2008 as well as support for Microsoft SQL Server 2008. Version
SafeCom G2 Enterprise Disaster Recovery Manual D60612-06 September 2009 Trademarks: SafeCom, SafeCom Go, SafeCom P:Go, SafeCom OnLDAP, SafeCom epay and the SafeCom logo are trademarks of SafeCom a/s. Company
Historian SQL Server 2012 EIO0000001701 04-10-2013 Historian SQL Server 2012 Installation Guide 04-10-2013 EIO0000001701.00 www.schneider-electric.com The information provided in this documentation contains
NovaBACKUP xsp Version 15.0 Upgrade Guide NovaStor / November 2013 2013 NovaStor, all rights reserved. All trademarks are the property of their respective owners. Features and specifications are subject
Aradial Technologies Ltd. Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted. No part of this document
Setting Up ALERE with Client/Server Data TIW Technology, Inc. November 2014 ALERE is a registered trademark of TIW Technology, Inc. The following are registered trademarks or trademarks: FoxPro, SQL Server,
Running a Workflow on a PowerCenter Grid 2010-2014 Informatica Corporation. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise)
BrightStor ARCserve Backup for Windows Agent for Microsoft SQL Server r11.5 D01173-2E This documentation and related computer software program (hereinafter referred to as the "Documentation") is for the
CA Unified Infrastructure Management Probe Guide for Informix Database Monitoring informix v4.1 series Copyright Notice This online help system (the "System") is for your informational purposes only and
Installation Guide NetIQ AppManager April 2016 www.netiq.com/documentation Legal Notice NetIQ AppManager is covered by United States Patent No(s): 05829001, 05986653, 05999178, 06078324, 06397359, 06408335.
Diamond II v2.3 Service Pack 4 Installation Manual P/N 460987001B ISS 26APR11 Copyright Disclaimer Trademarks and patents Intended use Software license agreement FCC compliance Certification and compliance
New and Changed Application Services in Informatica 10.0 1993-2015 Informatica LLC. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording
SafeCom Smart Printing Administrator s Quick Guide D10600-08 March 2012 Trademarks: SafeCom, SafeCom Go, SafeCom P:Go, SafeCom epay and the SafeCom logo are trademarks of SafeCom a/s. Company and product
GUARD1 PLUS SE Administrator's Manual Version 4.4 30700 Bainbridge Road Solon, Ohio 44139 Phone 216-595-0890 Fax 216-595-0991 firstname.lastname@example.org www.guard1.com i 2010 TimeKeeping Systems, Inc. GUARD1 PLUS
Installation & Configuration Guide Bluebeam Studio Enterprise ( Software ) 2014 Bluebeam Software, Inc. All Rights Reserved. Patents Pending in the U.S. and/or other countries. Bluebeam and Revu are trademarks
CA ARCserve Backup Patch Manager for Windows User Guide r16 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation
Veeam Backup Enterprise Manager Version 7.0 User Guide August, 2013 2013 Veeam Software. All rights reserved. All trademarks are the property of their respective owners. No part of this publication may
FileMaker 11 ODBC and JDBC Guide 2004 2010 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker is a trademark of FileMaker, Inc. registered
2014 Dell Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement.
MANJRASOFT PTY LTD Aneka 3.0 Manjrasoft 5/13/2013 This document describes in detail the steps involved in installing and configuring an Aneka Cloud. It covers the prerequisites for the installation, the
ImageNow for Microsoft SQL Server Best Practices Guide ImageNow Version: 6.7. x Written by: Product Documentation, R&D Date: July 2013 2013 Perceptive Software. All rights reserved CaptureNow, ImageNow,
Simba XMLA Provider for Oracle OLAP 2.0 April 23, 2013 Simba Technologies Inc. Copyright 2013 Simba Technologies Inc. All Rights Reserved. Information in this document is subject to change without notice.
Introduction EASYLABEL 6 has several new features for saving the history of label formats. This history can include information about when label formats were edited and printed. In order to save this history,
TSM Studio Server User Guide 184.108.40.206 1 Table of Contents Disclaimer... 4 What is TSM Studio Server?... 5 System Requirements... 6 Database Requirements... 6 Installing TSM Studio Server... 7 TSM Studio
Installing Windows Rights Management Services with Service Pack 2 Step-by- Step Guide Microsoft Corporation Published: October 2006 Author: Brian Lich Editor: Carolyn Eller Abstract This step-by-step guide
3245 University Avenue, Suite 1122 San Diego, California 92104 USA SOFTWARE INSTALLATION INSTRUCTIONS CLIENT/SERVER EDITION AND WEB COMPONENT VERSION 10 Document Number: SII-TT-002 Date Issued: July 8,
i Copyright Copyright 2015 Arbutus Software Inc. All rights reserved. This manual may contain dated information. Use of these materials is based on the understanding that this manual may not contain all
MGC WebCommander Web Server Manager Installation and Configuration Guide Version 8.0 Copyright 2006 Polycom, Inc. All Rights Reserved Catalog No. DOC2138B Version 8.0 Proprietary and Confidential The information
Archive Attender Version 3.5 Getting Started Guide Sherpa Software (800) 255-5155 www.sherpasoftware.com Page 1 Under the copyright laws, neither the documentation nor the software can be copied, photocopied,
50238: Introduction to SQL Server 2008 Administration 5 days Course Description This five-day instructor-led course provides students with the knowledge and skills to administer SQL Server 2008. The course
Moving the TRITON Reporting Databases Topic 50530 Web, Data, and Email Security Versions 7.7.x, 7.8.x Updated 06-Nov-2013 If you need to move your Microsoft SQL Server database to a new location (directory,
Installation Guide Lenel OnGuard 2009 Installation Guide, product version 6.3. This guide is item number DOC-110, revision 1.038, May 2009 Copyright 1992-2009 Lenel Systems International, Inc. Information
Migrating helpdesk to a new server Table of Contents 1. Helpdesk Migration... 2 Configure Virtual Web on IIS 6 Windows 2003 Server:... 2 Role Services required on IIS 7 Windows 2008 / 2012 Server:... 2
Aug/12/2002 Page 1 of 5 Administering a Microsoft SQL Server 2000 Database Catalog No: RS-MOC2072 MOC Course Number: 2072 5 days Tuition: $2,070 Introduction This course provides students with the knowledge
Dell Statistica 13.0 2015 Dell Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or
NovaBACKUP xsp Version 12.2 Upgrade Guide NovaStor / August 2011 Rev 20110815 2011 NovaStor, all rights reserved. All trademarks are the property of their respective owners. Features and specifications
Installation Instruction STATISTICA Enterprise Small Business Notes: ❶ The installation of STATISTICA Enterprise Small Business entails two parts: a) a server installation, and b) workstation installations
Technical Note VirtualCenter Database Maintenance VirtualCenter 2.0.x and Microsoft SQL Server This document discusses ways to maintain the VirtualCenter database for increased performance and manageability.
Quick Install Guide Lumension Endpoint Management and Security Suite 7.1 Lumension Endpoint Management and Security Suite - 2 - Notices Version Information Lumension Endpoint Management and Security Suite
Magaya Software Installation Guide MAGAYA SOFTWARE INSTALLATION GUIDE INTRODUCTION Introduction This installation guide explains the system requirements for installing any Magaya software, the steps to
How To Install SQL Server 2014 Express Edition Updated: 2/4/2016 2016 Shelby Systems, Inc. All Rights Reserved Other brand and product names are trademarks or registered trademarks of the respective holders.
Foglight Managing Hyper-V Systems User and Reference Guide 2014 Quest Software, Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this