Enhancement to meta-data comparing
The database-schema comparison functionality is further refined to display and generate the fix scripts for differences across stored procedure’s definitions. To illustrate (Figure 1), all or some procedures can be selected to be compared across all or some client-instances.
Figure 1 – Selecting stored procedures to compare
The differences in definition can then be individually viewed and fixed (Figure 2, pointer 1) or a script can be generated for the entire list (Figure 2, pointer 2). On viewing the differences, a line by line comparison is made (Figure 3). Selecting ‘Fix All’ generates the script (Figure 4) that can be sent to the selected client-servers.
Figure 2 – Results list of comparison
Figure 3 – Line by line comparison view
Figure 4 – Generated script to fix differences
After running the generated fix script, the comparison on procedures can be rerun and the results should have no exceptions (Figure 5).
Figure 5 – Result after fix script
Data synchronization enhancements
A monitoring screen for data being sent to client-servers (‘Reverse Data Sync’) is an addition to the ‘Data Sync Monitoring’ section, and monitoring of synchronization tables has further improved to now include the option to ‘Preview’ the data on the client-server (Figure 6, pointer 3). Functionality to display history and/or previously installed client-servers (Figure 6, pointer 2) and the ‘User Comment’ column (Figure 6, pointer 4) has also been added for auditability.
Figure 6 – Data synchronization monitoring
The addition of a bulk installer (Figure 7), makes deployment of a new distributed installation of Conductor4SQL a lot speedier. A great amount of development has allowed the pre-installation diagnostics to be run, in addition to the actual installation of a new client-server.
Figure 7 – Location of Bulk installing option
Running the ‘Checker’ (Figure 8, pointer 4) makes obtaining a list of install exceptions quick and simple, a function that has not formerly been attained this easily. Additionally, the business and grouping attributes of client-servers can be completed with the bulk installing feature (Figure 8, pointers 1 and 3). The rollout of an integrated, enterprise-wide server environment can thus be achieved in record time.
Figure 8 – Bulk installer application screen
The new feature to manage projects allows for projects to be created for your SQL environment (Figure 9, pointer 1), with all relevant scripts assigned to a version. The execution order of scripts can be updated (Figure 9, pointer 2) and the project can be released to selected client-servers (Figure 10). Scripts are also editable from within the projects section (Figure 9, pointer 3).
Figure 9 – C4SQL project and versioning management screen
Figure 10 – Option to release version to client-servers
Enhancement to scheduled queries
Saved user commands can be scheduled using a ‘Use Time to live’ option. This prevents a scheduled command from executing during unsuitable times, in the case where a client-server is offline and has commands waiting in its queue to execute.
Figure 11 – Scheduled queries ‘Time to live’ option to allow time period for execution of script
The user interface now lets users set up emailing lists to receive notifications (Figure 12). After an email is set up, it can be assigned to one or many event alerts (Figure 14), to send a summarized email of events. Auditing events from all client-servers that are centralized by Conductor4SQL can thus be configured to notify users via email in this manner. The auditing view has also improved to be centrally searchable and has an increased number of search fields (Figure 13). In addition, certain events which are not of auditing interest can also be excluded from being stored (Figure 15).
Figure 12 – Setting up email list to receive system notifications
Figure 13 – Central auditing screen with search fields
Figure 14 – Managing event alerts
Figure 15 – Configuring events to exclude from auditing
Improvement to dynamic database functionality
The feature to store a default database name for client-server installations, where each client-server has a unique database name has been improved by an added ‘Use Database’ option, available when sending scripts (Figure 16). Any workaround or template script is made redundant on the execution of scripts needing its own transaction.
Script security configuration
Users can also add security context to saved user-scripts to either be ‘Not editable by other users’ or ‘Not viewable to other users’ (Figure 16).
Figure 16 – User command screen with option to add to Project/Version and security setting
Synced data recovery
Data synchronized to the central server from client-server installations can be recovered and returned to client-servers in the event of synced data being lost from client-servers. With a new Disaster Recovery section, lost or partially recovered data can be compared with, and sent to a re-installed client-server to restore previously centralized data to a client-server database. This utilizes the reverse synchronization ability of Conductor4SQL allowing data to be sent in reverse directions, from the central server to client servers. Figure 17 displays the screen where a user can preview and select the data to recover.
Figure 17 – Synced data recovery screen
Reporting services reports
Version 3 offers a reporting section, which provides administrators with a convenient selection of reports to present data collected from client-servers. This has been a much anticipated feature of the product, supplementing the management of the Conductor4SQL environment. The majority of reports are fitted with a filtering and date-range selection.
Figure 18 – Example report
Client overview screen
Remodeling of the display when viewing a client-server’s detail allows the number of messages on the various queues to be displayed, assisting in a simplified overview of the queues. In turn this makes the option available to view the details of messages on a queue by merely selecting an adjacent icon. Under ‘Advanced’ options there is the functionality to open the client-server in SQL server management studio and the option to systematically restore communication with a problematic client.
Figure 19 – Enhanced client-server overview screen with ‘Advanced’ and ‘View messages’ options