|
What's New?
System Requirements
Contents of the Download Package
Installing This Module
Known Issues
Previous Releases
Contact Information
Legal Notice
|
|
AppManager for Microsoft SQL Server provides a comprehensive solution for monitoring the performance and availability of your
Microsoft SQL Server environment. This module provides Knowledge Scripts that present a complete view of Microsoft SQL Server
performance on your servers.
This release improves usability and resolves previous issues. Many of these improvements were made in direct response to suggestions from our customers.
We thank you for your time and valuable input. We hope you continue to help us ensure our products meet all your needs. You can post feedback in
the AppManager forum on Qmunity, our community Web site that also includes
product notifications, blogs, and product user groups.
For more information about this release and for the latest management guides, see the
AppManager Documentation page. To download this module and view the latest release notes, see the
AppManager Module Upgrades & Trials page.
What's New?
This release of AppManager for Microsoft SQL Server provides the following enhancements:
- Support for Windows Server 2012. This release now supports monitoring Microsoft SQL Server installed on Windows Server 2012. For more information, see the System Requirements.
To get the updates provided in this release, you must install the module to the repository (QDB) and propagate changes to any running jobs for the
Knowledge Scripts that were updated in this release. AppManager 7.x does not automatically update renamed or copied Knowledge Scripts.
For more information, see the "Upgrading Knowledge Script Jobs" section in the management guide.
This release of AppManager for Microsoft SQL Server replaces all previous releases.
Return to Top
System Requirements
For the most recently updated list of supported application versions, see the AppManager Supported Products page. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below.
AppManager for Microsoft SQL Server has the following system requirements:
- AppManager version 7.0 or later installed on the AppManager repository (QDB) computer, on the Microsoft SQL Server computers
you want to monitor (agents), and on all console computers.
Note Support for Windows Server 2008 on AppManager 7.x requires AppManager Windows Agent hotfix 71704 or later. For more information, see the AppManager Suite Hotfixes Web page.
- One of the following Microsoft operating systems installed on the agent computers:
- Windows Server 2012
Note For clustered SQL Server monitoring, you must ensure that AppManager for Microsoft Windows 7.8 or later is installed on the agent computer.
- Windows Server 2008 R2
- Windows Server 2008 (32-bit or 64-bit)
- Windows Server 2003 R2 (32-bit or 64-bit)
- One of the following versions of Microsoft SQL Server installed on the agent computers:
- SQL Server 2012 (32-bit or 64-bit)
Note The account that is used to run the SQL knowledge scripts should have sysadmin and public role permissions granted.
- SQL Server 2008 R2 (32-bit or 64-bit)
- SQL Server 2008 (32-bit or 64-bit)
- SQL Server 2005 Service Pack 2 (32-bit or 64-bit)
- AppManager for Microsoft Windows module installed on the AppManager repository (QDB) computer, on the Microsoft SQL Server computers you want to monitor (agents), and on all console computers
Note Support for Windows Server 2008 R2 on AppManager 7.x requires the AppManager for Windows module, version 7.6.170.0 or later. For more information, see the AppManager Module Upgrades & Trials page.
For more information, see the AppManager for Microsoft SQL Server Management Guide, included in the download package.
Return to Top
Contents of the Download Package
AppManager for Microsoft SQL Server includes a managed object, qsqla4.dll, and Knowledge Scripts to discover and monitor Microsoft SQL Server resources. The download package includes this Readme, a management guide, Help for Knowledge Scripts, and several files that are used during installation:
AM70-SQL-7.5.17.0.msi, the module installer. AM70-SQL-7.5.17.0.ini, a configuration file used with the AppManager setup program. AM70-SQL-7.5.17.0.xml, a configuration file used for deploying the module with Control Center. This is the file you check into the Control Center Web Depot.AM70-SQL-7.5.17.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation. DefaultRule_SQL.xml, a configuration file used for deploying the module with Control Center.
ckSQL.exe, the pre-installation check used with the AppManager setup program.
When you download the module, these files are copied by default to the local folder on the download computer. Consider copying these files to the \windows_installation\setup\Setup Files folder on the same distribution computer on which you saved your main AppManager software and documentation. By doing so, you maintain all AppManager software in one location that is easily accessible when you want to add more repositories, management servers, or agents.
Return to Top
Installing This Module
Run the module installer to install the module components in the following locations:
- On the Microsoft SQL Server computers you want to monitor (agents) to install the agent components
- On all console computers to install the Help and console extensions
Run the module installer only once on each of these computers.
You must also install the Knowledge Scripts. You can install these components into local or remote QDBs. When installing to the primary QDB,
select the option to install Knowledge Scripts, and then specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name.
Important If you use Control Center 7.x, run the module installer for each QDB attached to Control Center. If you use Control Center 8.x, run the module installer only for the primary QDB, and Control Center will automatically replicate this module to secondary QDBs.
Install Knowledge Scripts and Analysis Center reports only once per QDB. The module installer now installs Knowledge Scripts for each module directly into the QDB instead of to the \AppManager\qdb\kp folder as in previous releases.
For more information about installing the module, see the AppManager for Microsoft SQL Server Management Guide, included in the download package.
Return to Top
Known Issues
NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
Return to Top
Previous Releases
This release of AppManager for Microsoft SQL Server includes enhancements added in previous releases.
Release 7.4.45.0, August 2012
This release of AppManager for Microsoft SQL Server resolved the following issue:
- Data streams and events for the SQL_DBOption Knowledge Script do not correspond to existing databases. This release resolves an issue where some
data streams and events for the SQL_DBOption Knowledge Script did not correspond to databases that existed on the SQL Server. This problem could occur when you
created or deleted databases after running Discovery_SQL Knowledge Script. With this release, the SQL_DBOption Knowledge Script creates data streams and events for the correct
set of databases. (ENG321055)
Release 7.4.38.0, June 2012
This release of AppManager for Microsoft SQL Server provided the following enhancements:
- Support for SQL Server 2012. This release now supports SQL Server 2012. For more information, see the System Requirements.
This release also resolved the following issues:
- SQL_LoginFailures Knowledge Script does not report SQL login failures properly. This release resolves an issue that occurred when a failed attempt to log in to a user account raised events for the previous failed attempts, even if the user is not listed in the Comma-separated user names to monitor parameter. With this release, the SQL_LoginFailures Knowledge Script raises events only for those users specified in the Comma-separated user names to monitor parameter. If this parameter is blank, the Knowledge Script raises an event for all the failed attempts to log in to a user account. (ENG316723)
- Email does not display SQL sentences completely if quotations are used within the SQL query. This release resolves an issue where emails generated when any of the following Knowledge Scripts was run did not display the SQL sentences completely if quotes were used within a SQL query. The email displayed the SQL sentences till the start of the quotes and get truncated at the quotes.
- SQL_TopLockUsers
- SQL_TopMemoryUsers
- SQL_TopResourceUsers
- SQL_TopIOUsers
- SQL_TopCPUUsers
- SQL_RunSQL
With this release, the SQL sentences in the email are displayed completely even if there are quotations within the SQL query. (ENG318102)
- Pre-installation check report improvements. This release resolves an issue where the pre-installation check displays that the requirements are met but, the pre-installation check report states as failed. With this release, the pre-installation check report is improved to eliminate the criteria that are not required for the module to install successfully. (ENG299093)
- Email for SQL_RunSql Knowledge Script events do not contain all event information. This release resolves an issue where emails generated when SQL_RunSql events occurred did not include the data from the message tab of the event when you set the Action_SMTPMail parameter to include that information. With this release, the missing information is included in the email. (ENG269029)
- Analysis Center does not display the server name for metrics generated by the SQL_DBStats Knowledge Script. This release resolves an issue where Analysis Center displayed only the database name as the object information label for data from the SQL_DBStats Knowledge Script, which made it difficult to distinguish the metrics in the reports. With this release, the Analysis Center displays both the database name and the server name. (ENG294294)
- SQL_MonitorJobs Knowledge Script reports false alerts. This release resolves an issue where the SQL_MonitorJobs Knowledge Script generated duplicate alerts when you restarted the AppManager agent while the job is running. With this release, the SQL_MonitorJobs Knowledge Script does not report false alerts. (ENG274177)
- Multiple copyright and version details in the NetIQ banner. This release resolves an issue where copyright and version details were displayed twice in the NetIQ banner. With this release, the copyright and version details are displayed only once in the banner. (ENG313437)
Release 7.3.121.0, November 2011
This release resolved the following issues:
- SQL_LoginFailures Knowledge Script does not properly filter by user account. This release resolves an issue that occurred when you specified one or more values
in the
Comma-separated user names to monitor parameter of the SQL_LoginFailures Knowledge Script and a failed attempt to log into a
different user account raised an event in some situations. With this release, the SQL_LoginFailures Knowledge Script only raises events for user accounts that you
specify in that parameter or for all user accounts if the parameter is blank. (ENG312984)
- SQL_Connectivity Knowledge Script does not raise events. This release resolves an issue where the SQL_Connectivity Knowledge Script from versions
7.3.111.0 and 7.3.116.0 of the AppManager for Microsoft SQL Server module did not raise any events in some environments. With this release, the
SQL_Connectivity Knowledge Script works as expected. (ENG312263)
- Two data streams from the SQL_ServerDown Knowledge Script have the same description. This release resolves an issue where the MSSQLServer and SQLSERVERAGENT
data streams generated by the SQL_ServerDown Knowledge Script had the same legend,
SQL Server down time. With this release, the
SQLSERVERAGENT data stream now has the legend SQL Server Agent down time. If you use Analysis Center to run reports based on these data streams, be aware that the reports will change to
use the new legends. (ENG311193)
Release 7.3.116.0, September 2011
This release resolved the following issues:
- Some Knowledge Scripts do not interpret log files. The SQL_BackupJob, SQL_ErrorLog, SQL_ErrorLogEx, and SQL_LogShipping Knowledge Scripts
fail with a
Buffer Overrun error when reading log files that contain dashed lines. Log files normally do not contain dashed lines. However,
when the SQL server encounters memory pressure, the output of the dbcc MemoryStatus command is written to the log file, resulting in dashed lines being inserted in the file.
With this release, the processing logic can interpret a log file with dashed lines. (ENG310661)
- Exclude filter does not work on SQL_Accessibility Knowledge Script. This release resolves an issue where the exclude filter does not work on
the SQL_Accessibility Knowledge Script when you include an asterisk, *, as a wildcard character. With this release, the
filter works as expected. (ENG311195)
Release 7.3.111.0, July 2011
This release resolved the following issues:
- Cannot collect data from computers with names longer than 15 characters. This release resolves an issue where
Knowledge Scripts are not collecting data from computers with names longer than 15 characters if the database is registered with the AppManager console using the
fully qualified domain name instead of the simple computer name. With this release, Knowledge Scripts collect data when the database is registered using the fully qualified domain name. (ENG297095)
- SQL_DBMirroring Knowledge Script does not collect data. This release resolves an issue where the SQL_DBMirroring Knowledge Script does not collect
data when event notification is turned off. With this release, if you set the data collection parameter to yes, data is collected even when event notification is set to no. (ENG307345)
- SQL_MonitorJob Knowledge Script incorrectly reports new failed jobs. This release resolves an issue where the SQL_MonitorJob
Knowledge Script reports events for new jobs failing in the first iteration, even though the job failures
were pre-existing. With this release, the SQL_MonitorJob Knowledge Script no longer raises an event for new job failures during the first iteration. (ENG278612)
- Buffer overrun possible when using SQL_NetError Knowledge Script. This release resolves an issue where the SQL_NetError Knowledge Script
has the potential to corrupt memory in some environments. With this release, the SQL_NetError Knowledge Script cannot create a buffer overrun. (ENG297666)
- Events refer to incorrect SQL server. This release resolves an issue in multiple Knowledge Scripts where the text inside an event refers
to an incorrect SQL server name. With this release, the correct SQL server is referenced in the text. (ENG303950)
Release 7.3.101.0, March 2011
This release resolved the following issues:
- Available data space reverts to zero in the DataSpace Knowledge Script. This release resolves an issue in version 7.3.82.0 in which the value for the available data space being used for each database in megabytes always reverted to zero. With this release, the script properly calculates the available data space in megabytes. (ENG305046)
- The DBLocks Knowledge Script causes excessive CPU and memory usage. This release resolves an issue in which the DBLocks Knowledge Script caused high CPU and memory usage after the first iteration of the job. With this release, the script contains new parameters that control the number of database locks to report and enable you to limit the amount of information generated by this script. For more information, see the Help for the DBLocks Knowledge Script. (ENG296537, DOC302185)
- The DBLocks Knowledge Script does not collect data if any exclusions are set. With this release, the DBLocks script collects data properly when exclusions are set. (ENG302499)
Release 7.3.82.0, December 2010
This release resolved the following issue:
- Prerequisite report does not display results for SQL Server 2008. This release resolves an issue where the prerequisite verification process
generates a report that does not display results for Microsoft SQL Server 2008. (ENG261938)
- BlockedProcesses Knowledge Script reports database error. This release resolves an issue where the BlockedProcesses
Knowledge Script job incorrectly pairs the resource names and the corresponding SQL Server
instance names and reports the following error:
SQL::RunSqlValue6() exited: [Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionWrite
(send). (ENG283260)
- Dataspace Knowledge Script does not report events for very large databases. This release resolves an issue where the
Dataspace Knowledge Script job does not reliably report events that exceed the
DB Space threshold you set in the Knowledge Script when the database is larger than 2 TB. (ENG299857)
- Temporary logs are not deleted. This release resolves an issue where the BackupJob Knowledge Script creates logs in the
netiq_debug folder and does not remove or overwrite the log files. (ENG284830)
- MemUtil Knowledge Script reports incorrect events for exceeding the memory threshold. This release resolves an issue where
the MemUtil Knowledge Script reports events for memory usage even though the memory usage does not exceed the threshold value. (ENG298830)
Release 7.3.61.0, May 2010
This release resolved the following issue:
- RunSQL job does not import all queries from file. This release resolves an issue in which the RunSQL Knowledge Script job imports almost all SQL queries from the file you specify. The script fails to import the last query in the file. For example, if the remote file contains eight queries, the script imports seven. If the file contains only one query, the script imports nothing. With this release, the RunSQL Knowledge Script correctly imports all queries in the remote file you specify. (ENG287676)
In addition, this release provided the following enhancements:
- Support for Windows Server 2008 R2. With this release, AppManager monitors Microsoft SQL Server installed on Microsoft Windows Server 2008 R2.
- Support for Microsoft SQL Server 2008 R2. With this release, AppManager monitors Microsoft SQL Server 2008 R2.
- Support for Microsoft SQL Server 2008 SP1. With this release, AppManager monitors Microsoft SQL Server 2008 SP1.
Release 7.3.54.0, March 2010
This release resolved the following issue:
- Action_RunSQL job fails when stored procedure returns no results. This release resolves an issue in which the Action_RunSQL Knowledge Script job fails when a called stored procedure returns no rows. The error message contains the following text:
Description: SQL::RunSqlValue3() exited: Operation is
not allowed when the object is closed, even though the procedure executes successfully. After you install this release, a code change prevents the Action_RunSQL job from failing when a stored procedure returns no rows. (ENG284755)
Release 7.3.52.0, February 2010
This release resolved the following issues:
- MemUtil job provides inconsistent threshold and data stream units. Before you install this release, the MemUtil Knowledge Script job uses inconsistent units for thresholds and collected data. After you install this release, threshold and collected data are consistently represented in MB. If you have existing collected data for Total Server Memory, understand that data will now be returned in MB. (ENG283518)
- AMAdmin_GreyMachines job fails when release 7.3.48.0 is installed. Before you install this release, a coding error in release 7.3.48.0 of the AppManager for Microsoft SQL Server management object causes several Knowledge Scripts to fail, including AMAdmin_GreyMachines. After you install this release, a code change in the management object enables all Knowledge Scripts that invoke it to run successfully. (ENG284010)
Release 7.3.48.0, February 2010
This release resolved the following issues:
- NearFileMaxSize job fails. Before you install this release, the NearFileMaxSize Knowledge Script job fails at the
GetDBNameAndFileName function. After you install this release, a code change improves error handling, allowing the job to proceed. (ENG276991)
- Module installation fails during the prerequisite check process. Before you install this release, installation of the module fails during the execution of
ckSQL.exe because the maximum number of allowed SQL instances is exceeded. After you install this release, a code change for ckSQL.exe increases the number of allowed SQL instances, permitting module installation to proceed. (ENG281917)
Release 7.3.38.0, October 2009
This release resolved the following issues:
- CPUUtil job cannot find performance counter. Before you install this release, the CPUUtil Knowledge Script job fails with a message that reads
Unable to read the perfmon counter: Process\IDProcess\sqlservr. This failure occurs if the syntax of the discovered path for the counter does not match the syntax of the path provided by the Microsoft function GetModuleFileNameEx. After you install this release, a change in the way the script interprets the path information allows it to find the sqlservr performance counter. (ENG262450)
- SQL Knowledge Script jobs fail on FQDN. Before you install this release, AppManager for Microsoft SQL Knowledge Scripts jobs fail to raise events or collect data points on server objects added to the Operator Console by Fully Qualified Domain Name (FQDN). The jobs do not fail on objects added to the Operator Console by IP address. After you install this release, applicable AppManager for SQL Knowledge Script jobs run successfully on server objects identified by either FQDN or IP address. (ENG270630)
- BackupJob job reports a successful backup as a failure. Before you install this release, the BackupJob Knowledge Script job raises an event indicating a SQL Server backup job has failed, although the most recent backup was successful. The job erroneously identifies an old backup, one from long before the current job iteration, as having failed during the current Knowledge Script job iteration. After you install this release, a change to the script's code allows it to raise events only for backup jobs that fail during the Knowledge Script job iteration. (ENG270806)
- Discovery_SQL unable to discover a very large database. Before you install this release, when the size of a database exceeds 2 TB, the Discovery_SQL Knowledge Script may be unable to discover the database. After you install this release, a change to the script's code allows the script to discover very large databases. (ENG274536)
Release 7.3.24.0, May 2009
This release provided the following enhancements:
- Support for Microsoft SQL Server 2008. With this release, AppManager monitors Microsoft SQL Server 2008.
- The ErrorLogEx Knowledge Script. This script monitors the Microsoft SQL Server error log for entries added since the last monitoring interval, and it allows you use regular expressions or literal searches to create search strings for the error log.
Hotfix 71333, November 2008
This release resolved the following issues:
- Some Knowledge Scripts fail when you run them on a SQL server with a large number of databases. Before you install this release, AppManager generates an error when you run one of the four Knowledge Scripts listed below on a SQL server with more than 100 databases. After you install this release, you can run any of these four scripts on a SQL server with more than 100 databases, up to the maximum amount of databases allowed by AppManager. (ENG255650)
The updated Knowledge Scripts are:
- RepLatency
- Replication
- RepTransactions
- RepTranSec
- Running Knowledge Scripts with very short intervals might cause the NetIQ agent to restart. Before you install this release, running Knowledge Scripts at very short intervals, such as less than one minute, might cause the NetIQ AppManager Client Resource Monitor service, also called the NetIQ agent, to restart. After you install this release, running scripts at very short intervals does not cause the NetIQ agent to restart. (ENG250118)
Hotfix 71292, October 2008
This release resolved an issue that occurs when the Accessibility Knowledge Script generates an event on excluded databases.
Before you install this release, if you run the Accessibility Knowledge Script on a SQL Server that has more than one database with a status of "Offline," and the offline databases are listed in the "Exclude these objects" parameter, the script raises an event that lists all excluded databases as inaccessible. After you install this release, this issue no longer occurs. (ENG241882)
Release 7.2, October 2008
This release resolved the following issues:
- Support for Windows Server 2008, 32-bit and 64-bit. You can now use AppManager for SQL Server with 32-bit and 64-bit Windows Server 2008 on the managed client. Support for Windows Server 2008 servers requires the AppManager agent for Windows Server 2008.
- Cluster installation. This release of AppManager for SQL Server supports multiple installations of SQL Server on a cluster.
- Receiving events for removed databases. In previous releases, you continued to receive events for databases that had been removed. This release resolves that issue. (ENG244011)
- Multiple Knowledge Scripts raise events for instances that the SQL Server does not own. Previously, a set of SQL jobs erroneously raised events indicating the server was not available. With this release, these SQL jobs ignore the instances that the monitored SQL Server does not own. (ENG245129)
This release included changes to the following Knowledge Scripts:
- DBMirrorStatus Knowledge Script. This new script tracks the status of each mirrored database (SQL Server 2005 and later). This script raises an event if one of the selected factors associated with the mirrored database changes, such as the mirror state, mirror role, or mirror partner, or if a new database is added or removed from mirroring. (DOC251395)
- MonitorJobs Knowledge Script. In previous releases of AppManager for SQL Server, AppManager raised events on agent jobs that failed to complete, but the data it returned was the date and time that the job was started, not when the job failed. The MonitorJobs script now raises events only when new job failures occur since the last monitoring interval. (ENG247624)
- RunSQL Knowledge Script. In previous releases, you could not run the RunSQL Knowledge Script in a clustered environment. This release resolves that issue. (ENG249073)
- DBStats Knowledge Script In previous releases, this script erroneously raised events on legacy databases. This release resolves the issue of continuing to receive events for a database you had previously removed. (ENG244011)
Release 7.1, May 2008
This release offered the following enhancements:
- New functionality in ServerDown Knowledge Script. A new parameter allows you to raise an event if the SQL Server server or agent processes are not found on the computer you are monitoring.
- Improved description of DataSpace Knowledge Script. The Help files for this script have been corrected to indicate that the script monitors for available data space. Previous versions of the Help files indicated that the script monitored for available disk space, which is not the script's proper function.
Return to Top
Contact Information
Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.
For detailed contact information, see the Support Contact Information page.
For general corporate and product information, see the NetIQ Corporate Web site.
For interactive conversations with your peers and NetIQ Corporation experts, become an active member of Qmunity, our community Web site that offers product forums, product notifications, blogs, and product user groups.
Return to Top
Legal Notice
THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU.
For purposes of clarity, any module, adapter or other similar material ("Module") is licensed under the terms and conditions of the End User License Agreement for the applicable version of the NetIQ product or software to which it relates or interoperates with, and by accessing, copying or using a Module you agree to be bound by such terms. If you do not agree to the terms of the End User License Agreement you are not authorized to use, access or copy a Module and you must destroy all copies of the Module and contact NetIQ for further instructions.
This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data.
This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time.
U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R. 227.7202-4 (for Department of Defense (DOD) acquisitions) and 48 C.F.R. 2.101 and 12.212 (for non-DOD acquisitions), the government's rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement.
© 2013 NetIQ Corporation and its affiliates. All Rights Reserved.
For information about NetIQ trademarks, see http://www.netiq.com/company/legal/.
Return to Top
| |