SPDocKit
Try it for FreeContact UsProduct Site
  • SPDocKit by Syskit
  • Release Notes
    • SPDocKit 12
    • SPDocKit 11.1.0
    • SPDocKit 11
    • SPDocKit 10
    • SPDocKit 9.1.0
    • SPDocKit 9
    • SPDocKit 8.0.3
    • SPDocKit 8
  • Requirements
    • SharePoint On-Premises User Permissions Requirements
    • Supported SharePoint Editions
    • System Requirements
    • Server Load Permission Requirements
    • Service Application Permission Requirements
  • Installation
    • Install SPDocKit
    • Upgrade to the Latest Version
    • Uninstall SPDocKit
  • Activation
    • Activate SPDocKit
    • Manage License
    • Activation Privacy Statement
  • Configuration
    • Configure SPDocKit
    • Configure SPDocKit Database
    • Import and Export SPDocKit Settings
  • Create SharePoint Farm Snapshots
    • Snapshots Screen
    • Manual Snapshots
    • Automatic Snapshots
  • Explore Reports & Create Documentation
    • Farm Explorer
      • Farm Explorer Screen
      • Farm Dashboard
      • Farm Explorer Reports
      • Farm Documentation
      • Passwords and Product keys
      • Generate an AutoSPInstaller XML Configuration File
      • Change the Limit on Site Topology Report
    • Site Explorer
      • Site Explorer Screen
    • Permission Reports
      • Permissions Reports screen
    • Analytics and Usage Reports
      • Analytics and Usage Reports Screen
      • Analytics Dashboard
      • Site Collection Analytics
      • Document Extensions Reports
    • Audit Reports
      • Audit Reports Screen
      • Audit Dashboard
      • Audit Log Details
      • Administrative Actions
      • Audit Settings
    • Best Practices
      • Best Practices Screen
      • Best Practices Reports
    • Subscriptions and Alerts
      • Subscriptions and Alerts
      • Create New Subscription
      • Create New Alert
    • Customizing Reports
      • Customize View
      • Add Comments
  • Compare SharePoint Configurations
    • Compare Wizard
    • Compare SharePoint Farms
    • Compare Servers
    • Compare Web Applications
    • Compare Site Collections
    • Compare SharePoint Permissions
    • Compare Web.Config Files
  • Manage SharePoint Permissions
    • Permissions Explorer Screen
    • Manage Permissions Ribbon Actions
    • Users and Groups Actions
      • Manage Groups Wizard
      • Group Memberships Wizard
      • Copy Permissions Wizard
      • Move Permissions Wizard
      • Manage Permissions Wizard
      • Remove Permissions Wizard
    • Securable Objects Actions
      • Break/Restore Permission Inheritance Wizard
      • Restore Permissions
      • Copy Object Permissions Wizard
    • Site Collection Actions
      • Site Collection Administrators Wizard
      • Permission Levels Wizard
      • Clean Site Collections Wizard
    • Add Tags
    • SPDocKit Permission Management Event Log
  • Configure & Extend SPDocKit
    • Backstage Screen
    • Options Wizard
    • License Management
    • Role Based Security
    • Extend SPDocKit
      • Install SPDocKit Extensions
      • Download SPDocKit Extensions
      • Activate SPCAF Extension
  • Query & Change SharePoint Settings
    • Queries and Rules Screen
    • Create SharePoint Governance Policy Rule
    • Create SPDocKit Query
    • Change SPDocKit Query Results Limit
    • Create Audit Queries and Rules
  • FAQ
    • Requirements
    • Installation
    • Activation
    • Configuration
    • Features
    • Security
    • Miscellaneous
    • SPDocKit Insights Removed
    • SPDocKit Insights Migration
  • Known Issues
    • CREATE TABLE permissions denied
    • Custom features missing in reports
    • Data retention not working properly
    • Distributed Cache loading issue
    • Load crashes with NullReference exception
    • Available Windows updates
    • Permissions Wizard issue
    • PowerPivot FileNotFoundException issue
    • SQL Clusters support
    • Storage Metrics report subscription
    • Unaccounted differences in the UPA settings
    • Custom Query issue with URL export
    • Recursive groups issue with export
  • Troubleshooting
    • SharePoint
      • Could not access content database
      • The service application ‘UPA Name’ does not have any proxies that are default in a proxy group
    • Server Load & User Permissions
      • RPC Server is Unavailable
      • Error occurred while loading Web Application
      • Error occurred while trying to load 'Problems and Solutions' and 'Rule Definitions'
      • Error while loading IIS Settings Information
      • Errors while trying to load the SharePoint farm
      • Errors while loading server information
      • Failed at retrieving SQL Accounts from the following servers
      • My permissions loading status is reported as ”Failed”
      • Service was unable to read Active Directory properties
      • SQL Server is unavailable
      • Error adding service account to "spdockit_service_role" database role
    • SQL Server Connection
      • SPDocKit won’t connect to a provided server and database
      • Configure SQL server to listen on a specific port
      • Is SQL Server configured to use a named instance
      • Inbound traffic on TCP Port 1433 needs to be allowed on the SQL
      • Service user does not have rights to connect to the SQL server
      • TCP/IP network traffic not enabled on the SQL Server
Powered by GitBook
On this page
  • SPDocKit Farm
  • SPDockit Workstation
  • Multiple farms in a single SPDocKit database
  • Multiple Databases on a Workstation
  • Edit a connection

Was this helpful?

  1. Configuration

Configure SPDocKit Database

This article explains how to configure the database for SPDocKit.

PreviousConfigure SPDocKitNextImport and Export SPDocKit Settings

Last updated 2 years ago

Was this helpful?

SPDocKit uses a database for storing data gathered from your SharePoint farm.

From SPDocKit 8 onwards, the use of a dedicated SPDocKit database is required!

Please note! This should be a SPDocKit-dedicated database; please do not provide SharePoint databases here.

SPDocKit Farm

To configure a database on the server installation of SPDocKit, follow the steps below:

  1. Select Configuration from the left navigation bar on the Backstage Screen and then click the Configure button.

  2. On the Database wizard page, select whether to create a new database or use the existing one. Read more about the .

  3. On the Database Configuration wizard page, specify the SQL Server, Database Name, and authentication. It is possible to overwrite the existing database under the same name.

    • If you are using the default instance, type "servername", or "servername.yourdomain.loc".

    • If you are using a named instance, type "servername\instancename", or "servername.yourdomain.loc\instancename".

    • If your SQL Server is on a non-standard port (different from 1433), type "severname,port" or "servername\instance,port". (FQDN formats are also supported)

    After providing the information, click the Test Connection button to ensure that the settings are correct.

  4. Click Next, wait a few seconds, and your SPDocKit database will be ready to use!

SPDockit Workstation

Please note! Only SPDocKits installed on SharePoint servers can create databases. Workstations cannot create their own database; they must connect to already existing databases.

To select a database on a workstation installation of SPDocKit, follow these steps:

  1. Select Configuration from the left navigation bar on the Backstage Screen, and then click the Configure button.

  2. During the Database Configuration step, specify the SQL Server, Database Name, and authentication for a existing SPDocKit database.

    • If you are using the default instance, type "servername", or "servername.yourdomain.loc".

    • If you are using a named instance type, "servername\instancename", or "servername.yourdomain.loc\instancename".

    • If your SQL Server is on a non-standard port (different from 1433), type "severname,port" or "servername\instance,port". (FQDN formats are also supported)

    After providing the information, click the Test Connection button to ensure that the settings are correct.

  3. Click Next, wait a few seconds and your SPDocKit database will be ready to use!

Multiple farms in a single SPDocKit database

You can document multiple SharePoint farms using one SPDocKit database. When installing SPDocKit on your desired farms, provide the same database details for each installation, and you will be able to explore reports from multiple farms in each SPDocKit instance.

  1. If you have multiple SPDocKit instances, each using its own database, you will have to decide whether you want to reuse one database to become a central database for all the instances or create a brand new one.

Please note! It is not possible to merge data from multiple SPDocKit databases into a single database.

  1. For each SPDocKit instance, go to the Configuration tab and click Configure to open the Configuration Wizard. If the database you want to use as a central database already exists, just input the SQL Server and database name into the wizard and complete the wizard. If the database does not exist, create it only once with one instance of SPDocKit and choose to use an existing database for every other instance.

  2. After that, check one more thing: go to Options, then go to Service Settings, and check the SPDocKit Database field under Snapshot Location. This will ensure that all snapshot data is saved to the database and available from all connected SPDocKit instances.

SPDocKit installed on a workstation can also be connected to such a database without being a part of a SharePoint farm. This way, you can monitor multiple farms without the need to connect to a single SharePoint server.

Some of the pros and cons of using this kind of setup are:

+ You have one centralized place where you can track data from all your connected SharePoint farms.
+ It’s easier to compare changes between farms.
- As any database grows and stores more data, executed queries will require more time to execute. Generating reports might slow down a bit.

Multiple Databases on a Workstation

This section will explain how to use the Database Connection chooser, a feature used to quickly change between databases on a workstation.

You can find the Database Connection Chooser in the top right corner of the application.

When you install SPDocKit for the first time, the installation will ask you to use the Configuration Wizard. The database you set up there will be the Default one. After that, you can use the Database Connections option to quickly set up other connections.

To add a new database connection, follow these steps:

  1. Click on the Database Connections drop-down button, which can be found above the ribbon and on the right, and choose Edit.

    Alternatively, in the Backstage (File > Configuration), under Configuration settings, click Database Connections.

  2. After that, click the Add button. The New Database Connection dialog will open.

    Here, you can input your Connection Name, the SQL Server you wish to use, and, of course, the database you want to connect to. To access the database, you can use either Windows or SQL authentication. Press OK and a Progress dialog will appear. This dialog will output any errors that have occurred. If no errors have occurred, you can Close the window and continue on to the next step.

  3. You will be returned to the Database Connection window. Select the connection you just made and click Set as Active. In a few moments, the database connection will change — and that is it!

To change the database, you can use the Database Connection dialog to list all created connections and the Set as Active button to connect to a database. A much simpler solution is to use the drop-down. Click on the connection you want and the database will be switched immediately.

Edit a connection

In the main Database Connection dialog, select the connection you want and click the Edit button. You can edit a connection's name, but you can also completely change the SQL Server or the database you are using. When you are done, click OK.

To delete a connection, select it and click the Delete button.

SPDocKit database requirements