[Video] SQLDocKit Introductory Webinar

Thank you for joining us last week for yet another SQLDocKit webinar and finding out more about our new SQL Server inventory and management tool, SQLDocKit!

We had a lot of fun presenting the SQLDocKit introductory webinar, especially because our participants had some very interesting questions will discuss further below.

Some of the key segments we discuss in this webinar is as follows:

  • SQL Server inventory and management
  • SQLDocKit quick overview
  • SQLDocKit demo presentation
  • Upcoming features in future releases

Today Microsoft SQL plays an important role in any larger company. What’s also important is keeping track of resources and financial funds. That’s why IT management and the financial department have grown to be of utmost importance for a company’s smooth functioning.

SQL Servers are not that easy to acquire. They have complex licensing options and multiple editions. All of this leads to confusion, and it usually starts off with a question you don’t have a straightforward answer to:

How many SQL Servers do I have in my environment?

Encouraged by our own situation, where even we in the software development industry could not answer the question above, we decided to create a tool able to autodetect and inventory SQL Servers. That’s how we came up with SQLDocKit.

SQLDocKit is now in charge of SQL Server inventory and management in our company, as well as many other companies that needed SQLDocKit’s help.

It takes care of the SQL Server environment with features like:

  • Autodiscovery
  • Topology and SQL Server inventory
  • License compliance
  • Validation for best practices
  • SQL Server documentation
  • Track changes and compare

Since you had quite a few questions, let’s go through them, and then if you’re interested in a more detailed explanation of what SQLDocKit can do, check out the webinar video.

Embark on a SQLDocKit journey with your guide Toni Frankola, who will be showing a demo of SQLDocKit and providing a quick overview.

Table of contents

00:53 Presenting Acceleratio
03:57 SQLDocKit Overview
18:08 Demo by Toni Frankola
50:33 What’s next with SQLDocKit
52:10 Q&A

Q: Is it possible to retrieve a SQL Server even if you don’t have access to that particular server?

A: You need to have a user who is a Windows administrator to detect whether an SQL Server is installed on that particular box. Once we detect a SQL Server, SQLDocKit will show that there indeed is a SQL Server. You need to give the user permissions to access the SQL Server so we can retrieve information about SQL Server settings and databases.

Q: Do I need to install a client?

A: SQLDocKit is a Windows-based application and needs to be installed somewhere. It can be installed on your workstation or laptopm. However, it is important that this box is in the same domain so it can retrieve information from your SQL Server.

Q: Can SQLDocKit gather agent jobs?

A: Currently, that’s not the case; however, we’re working on it. It will be in the next SQLDocKit release next month.

Q: How much stress is placed on SQL Server CPU and memory in the snapshot taking process?

A: Not a noticeable amount, since we’re using basic T-SQL commands to retrieve SQL Server settings.

Q: Can I get a list of best practices that SQLDocKit currently applies to SQL databases?

A: Yes, of course.

Q: Is there a chance to check SQL Servers if I have no AD, and only Local Admins?

A: At this moment, no. It will be shipped in the next version—stay tuned. You will be able to specify custom credentials, including Windows custom credentials, which applies when you don’t have a domain or SQL authentication credentials to be able to connect to the databases in different domains. You will have the ability to connect to something that’s not even your domain, such as an Azure domain. If your database is in Azure, then we won’t be able to retrieve information about installed programs on that virtual machine, but we will still be able to gather information on settings, databases, files, etc.

Q: Is a “run only” version planed, like in SPDocKit?

A: Not at this point, no.

Q: I noticed that it captures the storage and sizes of databases—does it keep a history of those values? For example, in January 1 it was 200GB, January 2 it was 205GB.

A: Yes, it does.

Q: Will SQLDocKit be able to see if my Server is virtual?

A: At this point SQLDocKit doesn’t have this option, but we’re working on it for the next release.

I must admit, I was very thrilled to see so many questions and to be honest, our plans for future SQLDocKit release have just become greater due to your inspiring feedback.

While we’re on the topic of new features, I’ve noticed you guys have a lot of suggestions for what we could implement next in SQLDocKit. The good news is we’re working on it, and as far as features go, this is what we have planned out so far:

  • Database-level permissions
  • Multi-domain support
  • Email alerts – best practices
  • Licensing reports
  • Improved documentation
  • Additional best practices reports
  • Brand-new inventory reports

The Q&A section didn’t cover all your questions? Write to us!

For our next webinar to be even more interesting, we’d like to know if you have any more questions, or if we perhaps haven’t answered all of them.

What do you think of SQLDocKit? Your questions, as well as your comments, are welcome. With the right feedback, it’s always easier to improve SQLDocKit!

Now listen to this:

SQLDocKit has a free 30-day trial. Here’s your big opportunity to test our tool and tell us your impressions. Is there something we could improve? Which new features are you looking for? Start a conversation in the comment section below or contact our support team.