Greetings!
We have not updated Total Network Inventory for a long time, and there were serious reasons for this – we laid the foundation for a complete transition of the architecture to working with databases.
TNI is a product with a long history, dating back to 2006. All this time, we have been tirelessly developing the functionality of the software, making it better and more convenient. This is confirmed by the large number of regular Total Network Inventory users who have been with us for many years.
But, along with the developed functionality for inventorying the hardware and software of computers in corporate networks, TNI also brings with it the legacy of the old architecture – a file-based data storage, with its inability to cope with new customer requirements. Therefore, it’s time for Total Network Inventory to change!
Six months ago, we began a major effort to switch the program architecture to work with databases. We present the first and most important stage of TNI’s transition to new technologies:
Total Network Inventory has now the ability to work with SQL servers, which will make the program a full-fledged reliable multi-user product. Today’s release provides basic functionality for working with the PostgreSQL SQL server. This is the first step of many towards the further development of the new Total Network Inventory architecture.
More information about working with multi-user storage can be found in the TNI manual.
Working with file storage is still supported and does not require installation of SQL server, but only in single-user mode.
In the future, TNI will completely abandon storing information in files. We will improve the internal architecture to for better performance and scalability, add integration with other modern systems, and many other popular functions.
The first thing we decided to do based on the new architecture was a new TNI Users mode. This mode provides the ability to manage software users, allowing you to create accounts and define their access rights to various operating modes in TNI. In addition, for each user you can set individual access rights to the storages themselves. Now, your Total Network Inventory colleagues can get exactly the tools and capabilities they need, making work more flexible and secure.
Other improvements and fixes are available in the version history.
See you!
Nahhh!!! You have started to make things just more complicated introducing postgreSQL database, now users have to deal/learn/troubleshoot DB related issues.
Using postgreSQL should be an option and keep TNI storage as default storage method.
I will stay with version not using any database. Current storage method just works like a charm. Why to break thing that already works very well?
; (
Hi!
Using DB is an option, and you still can stay on ordinary storage. There is no need to use PostgreSQL unless you have to.
We transform TNI to databases since we have to develop the product further.
Yes, this may be slightly complex but it allows expanding the software features and adding new possibilities.
At last! I presume thus TNI won’t have to rely on 256 string symbol limit for recording assed paths!
I’ve been waiting for this for a long time! I hope database transition will allow our complex/nested AD tree to finally display as deep as it is.