Overview & Introduction
PSIcapture and Microsoft SQL Server are integrated on a variety of fundamental levels. Information stored in what is generally termed "Metadata" that is associated with content imported and exported through PSIcapture is usually stored in a Microsoft SQL Server Database. Using SQL Databases (DBs) allows both PSIcapture and its users to access relevant information faster than ever. SQL DBs have been recognized as an industry standard for storing and managing data indices for generations.
Those generations of work continue to improve PSIcapture and its capabilities. However, depending on the scale and complexity of the operations performed by the users, administrators, and company employing PSIcapture, different versions of SQL Server may be appropriate.
Let's take a look at a couple examples of a SQL Variations that may be appropriate for your PSIcapture Installation:
Business 1: Independent Accounting Firm
A smaller business performing actions for 10-20 clients on a daily basis. Most of their clients send a maximum of 1-2 documents per day to be processed. There are some additional internal documents as well. PSIcapture is run on 1-3 machines maximum, and all machines run on standalone licensing. All machines are accessed on-site. Changes to Capture Profiles are made by a single PSIcapture Administrator.
Volume: 30-50 documents a day, 2-3 pages per document, standard filetypes, standard workflow.
SQL Solution: SQL Local DB, the default solution for PSIcapture, is most appropriate for this level of product usage, as a single machine acting as a Capture Server can maintain configuration changes without issue for this business environment.
Business 2: Local Payroll Auditing
A medium business performing actions for 30-50 clients on a daily basis, with fluctuating levels of volume in document processing depending on the timing of certain business operations. Most of their clients send a bulk collection of documents, sometimes spanning years at a time. There are a variety of additional internal documents as well. PSIcapture is run on 5-10 machines, and all machines are licensed via an independent license server machine. Most machines are accessed on-site, and some remotely on occasion. Changes to Capture Profiles are made by three PSIcapture Administrators.
Volume: 50-100 documents a day, 50-300 pages per document, various filetypes, split workflows.
SQL Solution: While SQL Local DB can sustain configuration changes for this business, their decision to use SQL Express, the free SQL Server solution available from Microsoft, to host their Configuration and Batch Manager Database Files, came from a desire to isolate the performance of a specific machine for managing a large Batch Manager Database file, which was set to the configuration's maximum size to accommodate an unusually large number of batches created on a regular basis.
Business 3: Enterprise AP Processing
A larger business performing actions for hundreds of clients on a daily basis, with multiple "Peak Hours" depending on the timing of certain business operations. Their clients send a consistent stream of content spanning a variety of businesses and workflow complexities. Their Classification Profiles are in the thousands. They have split off an entire group of machines to manage internal documents. PSIcapture is run on 15-30 machines, and all machines are licensed via isolated License Servers for each specific workflow type. Machines are hosted almost entirely on Cloud-based servers with highly modifiable hardware configurations, with few exceptions for a group of PSIcapture Administrators.
Volume: 5000-10000 documents per day, 5-25 pages per document, extensive filetypes, multiple split workflows across multiple networks.
SQL Solution: This business pushes PSIcapture to its processing limits, incorporating a host of diverse machines with customized hardware configurations for specific workflows. Because of the nature of their business and the need for redundancy and backup solutions to keep a smooth stream of workflow even at peak hours, the business has chosen to host their Configuration and Batch Manager Databases on SQL Server Enterprise edition, which allows them to not only quickly and easily copy configuration and batch data between locations, but also allows for quick switchover of SQL Server locations for these integral database files in the event of a power failure or otherwise. This also has the added benefit of handling the intense stream of updates from a variety of different machines hosting their own unique collections of configurations and batches.