databaseEZ is a tool that offers you robust features from parsing over 130 database properties including some that aren’t even available in the Notes or Admin clients, as well as it lets you modify and all of it en-masse. In this section, we'll answer questions you might be wondering about: How does it "work"? How (and where) is it installed? Are there any risks? Is there an "undo" button? Etc. Here you go!
What type of installation does databaseEZ require?
As the rest of the Ytria tools, databaseEZ is installed on the client side ONLY, there is no need to install anything on the server, and being a local install means no system downtime.
How does databaseEZ "work"?
databaseEZ is a standalone compiled application coded in an efficient, low-level language. When installed, it's executable file (databaseEZ.exe) is detached into your Notes Program Directory. Each time you start databaseEZ, a new Notes session is created, independent from your Notes client session. This means that databaseEZ runs parallel to your Notes client and thus will not interfere in any way. In fact, you can think of databaseEZ as a special "Notes client" to help you oversee and manage your database properties, issue console commands, get view and folder index sizes and more, across an entire server. You can even select which ID you want to work with—without having to switch IDs in your Notes client!
How does databaseEZ affect security?
That's a good question! When working with applications (especially user mail files) security IS a crucial subject. Although databaseEZ offers you a multitude of features that surpass the functionality available in both the Administrator and Designer clients (such as the ability to view basic application properties and settings, even if you aren’t part of their ACLs), our tools NEVER bypass Notes security. Certain key options, such as modifying properties, issuing console commands or enabling Full Access Administration, require you to have the proper access rights in order to use them.
Are my modifications safe?
With databaseEZ, you can modify hundreds of databases, and any of their properties in merely a few clicks. With such power available, how can you know that you're making the right changes? Don't worry, we've got you covered! Your modifications are protected by a two-step saving process which allows you to review your changes before deploying them—regardless of the modification you've performed.
What about speed? Do I get all this info right away?
The fact that databaseEZ is an independent, compiled program, puts it in the position to outperform built-in Notes and Domino solutions. But beyond that, databaseEZ can handle hundreds (or even thousands) of databases, thousands of activity log lines, giving you a much better overview of your global database situation. Loading all of this information can take a bit of time. Don't worry though, we've built a bunch of pre-loading filter options into databaseEZ so you can pinpoint the information that you absolutely need to load – such as the types of applications to load. There is also a two step loading process to optimize performance.
How does logging pertain to databaseEZ?
databaseEZ operates through the official Notes API channels; for example a console command will always leave proper trace, as well as your session and read / edit operations will be logged in the log file, however, we offer much more extensive history and log options that the native solutions. You have the option to create a special Modification Log database in which every single operation performed using our EZ Suite tools will be logged. You can place this database on either your local machine, or one of your servers. You can even use our licensing system to route logging for all EZ Suite users into a central log database.