Difference between revisions of "CORE:Frequently Asked Questions"
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
* [[Moving SwSQL Databases to another drive]] | * [[Moving SwSQL Databases to another drive]] | ||
* [[Unable to connect to target database: Call to SQLError Failed]] | * [[Unable to connect to target database: Call to SQLError Failed]] | ||
| − | *[[Causes of Database table corruption]] | + | * [[Causes of Database table corruption]] |
| − | *[[Repairing a Corrupt Index File]] | + | * [[Repairing a Corrupt Index File]] |
===Security=== | ===Security=== | ||
| Line 26: | Line 26: | ||
===The Apache Web Server=== | ===The Apache Web Server=== | ||
| − | *[[Unable to start SwHTTPServer due to port conflict]] | + | * [[Unable to start SwHTTPServer due to port conflict]] |
Revision as of 12:39, 26 January 2018
Database
- Size Comparison of SwSQL with MS SQL
- How to Repair a Corrupt Index File | (Forum thread)
- Increasing the Maximum Size of the Analyst E-Mail Address Field | (Forum thread)
- Adding Extra Filter Columns to the Call-Index Table
- How to Run a Batch Update of All Customer Records for Web Access | (Forum thread)
- Changing the SwSQL Account Password | (Forum thread)
- How to Identify the Database that Holds a Specific Table
- How to repair all system tables (sw_systemdb)| wiki
- The Root Causes of Database Table Corruption
- Database Migration using the Database Migration Wizard
- Minimum Number of Characters search
- How to add a column to the database using the Database Schema Editor
- Moving SwSQL Databases to another drive
- Unable to connect to target database: Call to SQLError Failed
- Causes of Database table corruption
- Repairing a Corrupt Index File
Security
- Security audits reporting potential vulnerabilities in Core Services 3.X
- Apache Web Server Hardening
- Setting Up Single Sign-On for the Web Client
- Setting Up Single Sign-On for SelfService
- Configuring SSL and Using Your Own Certificate/Key on the Web Server