[Video] Webinar: Presenting SQLDocKit 6.4, with auditing of database permissions and SQL Server BI services inventory

We recently issued a new release of our SQL Server administration tool. In order to demonstrate and show you all that’s new in SQLDocKit, we’ve prepared an introductory webinar presenting new features that will help you with SQL Server administration and management:

  • discovery of SQL Servers across multiple domains;
  • inventory of SQL Server BI services: SSIS, SSAS, SSRS;
  • database role permissions auditing; and more.

In addition these features, we wanted to show you SQLDocKit Live Explorer and database management from our previous release as well.

You can view a video recording of our webinar below with a quick overview and demo of our product by SQLDocKit product owner Frane Borozan.

Table of contents

03:49 SQLDocKit features overview
11:11 Demo by Frane Borozan
12:25 Domain management
19:34 SQL Server inventory reports
30:34 Compare SQL Servers
35:11 Database management
40:56 Q&A

Video Summary

How does SQLDocKit autodiscovery work?

SQLDocKit is installed on a single server. We recommend having a dedicated server, but if you don’t have many SQL Servers, you can install it on servers where you are running some other services. The application doesn’t need to be installed on a SQL Server. All the data from the remote SQL Servers is captured through API. You can use any Windows Server to install the application.

In case you have multiple untrusted domains in your organization, SQLDocKit allows you to define credentials for the different domains from a single console. SQLDocKit is then able to connect to all these domains using different credentials and discover all the servers in these domains. It is very helpful for consultants to connect to their client’s network and discover all the SQL Servers they have in the domains.

We invested a lot of time in the SQLDocKit autodiscover feature so that you are always up-to-date on all the servers you have. The application can discover all the Organizational Units or you can define specific OUs in which you want to discover servers. If you don’t want to use autodiscovery, you can add SQL Servers manually.

SQLDocKit connects to the domain controller and gets the list of all the servers in your Active Directory. It connects to every server you have and searches for SQL Server services. If the service exists on a particular server, the tool will try to access the server and get all the details of that SQL Server. If SQL Server services is not started, you will not be able to connect to that SQL Server. So you’ll also have servers in the application that are not running at the moment, but you will know that server is sitting on that machine.

Presenting new SQLDocKit features

SQLDocKit allows you to take a snapshot of the current state of all your SQL Servers. Snapshots of your SQL environment can be automatically or manually created. You can use this information to create helpful inventory reports which include all information and details regarding SQL Servers; SQL Server BI Services SSIS, SSAS, SSRS; and databases, as well as the Windows Servers that are hosting these databases. You can check all the general info about memory, processors, security, server logins, etc. SQLDocKit discovers all databases and their owners. See all the details about databases from a single location.

With the latest release, we wanted to provide you all the information about SQL Server BI services, as well as role membership reports at the database level. Besides SQL Server services, we added reports about the SQL Server Agent and all the jobs that you have in SQL Server Agent. Get an overview of all the scheduled jobs, the owners of these jobs, the status of the jobs, etc.

Snapshots can also be easily compared to detect even the slightest differences between environments or SQL Servers.

We added Live Explorer in version 6.3, so you don’t need to create a snapshot first to see all database settings. You’re now able to perform multiple database management tasks, such as finding out all the users who have been connected to a selected database and easily disconnecting already connected users. Drop or detach the database, determine the database owner, change the owner, or change the database state.

This was just a quick overview of SQLDocKit’s features. All these features help you stay completely informed and keep your SQL environment secure. Watch the video to learn more or download a free SQLDocKit trial and see it in action.

Like always, we tried to answer to your questions after the demo, so here’s a recap of the Q&A.

Q: Where is SQLDocKit installed?

A: The tool is installed on a dedicated Windows server. It doesn’t need to be installed on a SQL Server.

Q: How are servers discovered? What permissions do I need?

A: On a Windows server, you need to have local admin permission over that Windows server and a sysadmin role for the SQL Server sitting on this Windows server.

Q: Am I able to compare Analysis Services?

A: Yes. All the settings that you can see in the application can be compared, including SQL Server services.

Q: How many snapshots I can have?

A: The number of snapshots is unlimited. They can be taken manually or automatically. You can perform multiple snapshots during the day or delete certain snapshots.

Q: Is there any kind of storage report?

A: Yes. Check out all SQLDocKit reports here.

If you have any questions, feel free to contact our support team or send us suggestions for our next webinar topic. We can arrange a personal demo for you as well.