News & Events

Demand Technology Software releases version 1.3 of the SDK for building a SQL Server-based PDB.

New NTSMFPDB™ Software Development Kit version 1.3 is now available.

11/11/2005

News Release

Naples, Fla. (11/11/2005) — Demand Technology Software announced the immediate availability of version 1.3 of the Software Development Kit (SDK) for building and maintaining a Microsoft SQL Server-based Performance Database (PDB). The latest version of the SDK features improved operations capabilities, including support for a database base update Audit Trail and support for loading summarized History files.

The NTSMDPDB SDK is available free of charge to all current Performance Sentry/NTSMF customers.

The version 1.3 enhancements include:

•	A new DBUpdateAuditTrail Table that stores information from PDB update runs, whether performed during batch processing using the NtDACmd command line interface or interactively using the TestDriver web site screens. The TestDriver web site also includes a new tracking report that makes it easy to identify .smf data files which were not processed successfully during a bulk update run.
•	A new database Reload feature which makes it possible to build an historical database populated from data in summarized history files created by the DMSumSMF utility program. Several TestDriver screen programs were also enhanced to facilitate switching back and forth between a PDB detail database and an historical database.

To install and run the NTSMFPDB SDK requires the following run-time environment:

•	Performance Sentry collection service version 2.4.7.1, or higher
•	.NET Framework version 1.1 (runtime version is included)
•	Internet Information Server version 5.0, or higher to run the optional ASP.NET applications
•	Microsoft SQL Server 2000 (Enterprise Edition preferred). Note: either a local or remote copy of SQL Server can be accessed.

The NTSMFPDB™ toolkit includes source code and ready-to-run, compiled versions of programs that can be used to load NTSMF data collection files into a SQL Server database for reporting. For more details, refer to the original SDK 1.0 announcement.

News & Events

Media Contact