patternMinor
Best way to build a server inventory db and web interface?
Viewed 0 times
inventoryandwayinterfacewebserverbuildbest
Problem
My team is looking to build a rich inventory of servers at our enterprise. We are trying to consolidate several different excel documents into one database.
I found a great utility called AppGini (http://bigprof.com/appgini/) that can generate some pretty sweet material in short order. Our only problem is we might end up having 40 potential fields for each server...
Demo database here: http://bigprof.com/demo/employees_view.php
IE, it's a really wide spreadsheet, lots of columns. A lot of that data is not needed and would be annoying on a webpage (nobody wants to scroll left to right in a browser) The pages that AppGini generates can't give custom views.
For example; I might only want to see "Name", "Description", "Administrative Contact" but another person might need "Name", "Services", "Stack", "Ports" - I hope that makes sense. We all need to see something different.
What is the best way to go about this? Are there any similar programs to AppGini or utilities that I'm not familiar with that might be able to do this for me?
I found a great utility called AppGini (http://bigprof.com/appgini/) that can generate some pretty sweet material in short order. Our only problem is we might end up having 40 potential fields for each server...
Demo database here: http://bigprof.com/demo/employees_view.php
IE, it's a really wide spreadsheet, lots of columns. A lot of that data is not needed and would be annoying on a webpage (nobody wants to scroll left to right in a browser) The pages that AppGini generates can't give custom views.
For example; I might only want to see "Name", "Description", "Administrative Contact" but another person might need "Name", "Services", "Stack", "Ports" - I hope that makes sense. We all need to see something different.
What is the best way to go about this? Are there any similar programs to AppGini or utilities that I'm not familiar with that might be able to do this for me?
Solution
It sounds like you have two separate issues at play here. The first one is how and where to store the data. The second one is how to present it.
I suggest building a SQL database to store your data. That way you have full control over what is being stored, and where.
Once you have the data stored, you can use Microsoft Reporting Services to quickly build some reports based on templates. You can create as many reports as you like, hosting them locally and granting access to various users as required.
Heck, you could even just use Excel, and have "live" spreadsheets connecting to the database for their data, but that would not be web based. Reporting services can definitely deploy to a website.
I suggest building a SQL database to store your data. That way you have full control over what is being stored, and where.
Once you have the data stored, you can use Microsoft Reporting Services to quickly build some reports based on templates. You can create as many reports as you like, hosting them locally and granting access to various users as required.
Heck, you could even just use Excel, and have "live" spreadsheets connecting to the database for their data, but that would not be web based. Reporting services can definitely deploy to a website.
Context
StackExchange Database Administrators Q#7717, answer score: 5
Revisions (0)
No revisions yet.