I am getting ready to install KSS in my Windows Server 2016 environment. I also have SQL Server 2017 Standard. The KSS Installation Guide seem vague to me. "If you choose to integrate KSS with a SQL server, the following requirements apply."
Does KSS require a database at all? Why would I choose not to integrate KSS with a database? How/where does it store filters, rules, etc?
Also, can anyone relate their experiences with disk storage requirements? This is for about 30 servers with a 90 day retention.
I was thinking of installing SQL Server, KSS (as a service), as well as the Kiwi Web Access component on a 3TB QNAP NAS directly attached to the KSS server.
The Kiwi Web Access component raises another concern. Does KSS use a proprietary web server or does installation of this functionality install additional Windows Roles and Features (e.g. IIS)? Can these roles be distributed (i.e. use a dedicated database server, a dedicated IIS server).
Anyone have experience running this in a virtual machine?
Is there a more technical/detailed reference you can point me to beyond the Release Notes, Installation Guide, Getting Started, and Administrator Guides?
@vint I've been running KSS with, and without, an external SQL server for a while. Several months ago I built new 2016 VMs for our Kiwi servers, as well as changed back over to flat/text files instead of external DB.
The benefit of running an external DB will likely depend on your available resources. If you have the time/experience to build things out using SQL server as your base, then you will likely get more than someone who doesn't (which I suppose is fairly obvious for most things). In regards to the KSS web access, unless something has changed, I believe that runs with a limit of 4 GB, or possibly 10 GB now, so it's not great for long term storage. The web access does NOT use IIS, it uses UltiDev (something like that) and, in my opinion, is not really the best if you have many users needing access, or you're using multiple Kiwi servers.
Having ran KSS many different ways, with and without external DBs, I'm currently in the camp of just storing the logs in various flat/text files, and NOT using an external DB. In my experience, as limited as it may be, I feel it's just too clunky to use either the web access or external DB. I've found that having a bunch of flat files, stored on a share, are much easier to search and reference data (we use Notepad++ to search through all files in a folder, so it's easy and quick to find things).
KSS is actually a pretty powerful tool, though the way it's setup to use is not all that user friendly. The web access is nice, but I don't really think it scales very well. The ability to store logs directly into a DB is great, but can get real messy, real quick. And finally, KSS as a service is great because you don't need to be there to start it up. When the server boots up, KSS starts running. Otherwise, someone would need to log into the server after a reboot to open the KSS program (I think).
I'm sure this was not the most helpful, but hopefully it can provide even a tiny little nugget of value somewhere. Best of luck on your install, and let us know how it goes.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.