Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Microsoft Structured Query Language (SQL) Server

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Microsoft Structured Query Language (SQL) Server is Microsoft`s relational database management system designed for the enterprise environment. Microsoft offers several editions of Structured Query Language (SQL) Server, including Business Intelligence, Enterprise, Standard, Workgroup and Express. All editions are included in this entry. Microsoft Structured Query Language (SQL) Server has many components and add-ons that are included with this entry. See the component tab for more details. Additionally, only certain editions of Structured Query Language (SQL) Server support Transparent Data Encryption (TDE) which may be needed to protect sensitive data at rest in some situations. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.3
Decision Date:	03/18/2024 at 23:38:56 UTC
Aliases:	MS SQL Server; Attunity Connectors for Oracle and Teradata; Windows Internal Database (WID); Microsoft SQL Server Express; SQL Express
Introduced By:	TRM Analysis
Vendor Name:	Microsoft

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
SQL Server 2000	11/30/2000	04/09/2013	04/04/2013
SQL Server 2005	01/14/2006	04/12/2016	04/12/2016
SQL Server 2008	11/07/2008	07/09/2019	07/09/2019
SQL Server 2008 R2	07/20/2010	07/09/2019	07/09/2019
SQL Server 2012	05/20/2012	07/12/2022	07/12/2022
SQL Server 2014	06/05/2014	07/09/2019	07/09/2024
SQL Server 2016	06/01/2016	07/13/2021	07/14/2026
SQL Server 2017 Win	10/02/2017	10/11/2022	10/12/2027
SQL Server 2017 Lin	11/02/2017	10/11/2022	10/12/2027
SQL Server 2019 Win	11/04/2019	01/07/2025	01/08/2030
SQL Server 2019 Lin	11/04/2019	01/07/2025	01/08/2030
SQL Server 2022 Win	11/16/2022	01/11/2028	01/11/2033
SQL Server 2022 Lin	11/16/2022	01/11/2028	01/11/2033

Current Decision Matrix (03/13/2024)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2022

CY2023

CY2024

Future>

Release

SQL Server 2000

Prohibited

Unapproved

SQL Server 2005

Prohibited

Unapproved

SQL Server 2008

Prohibited

Unapproved

Prohibited

Unapproved

SQL Server 2008 R2

Prohibited

Unapproved

Prohibited

Unapproved

SQL Server 2012

Divest
[17, 23, 24, 27, 28]

Unapproved

SQL Server 2014

Divest
[17, 23, 24, 27, 28]

Divest
[17, 23, 24, 28, 29]

Divest
[17, 23, 24, 28, 29, 30, 31]

Divest
[29, 30, 31, 32, 33, 34, 35]

Divest
[29, 30, 31, 33, 34, 35, 36]

Divest
[31, 33, 35, 36, 37, 38, 39]

Unapproved

SQL Server 2016

Approved w/Constraints
[17, 23, 24, 27, 28]

Approved w/Constraints
[17, 23, 24, 28, 29]

Approved w/Constraints
[17, 23, 24, 28, 29, 30, 31]

Approved w/Constraints
[29, 30, 31, 32, 33, 34, 35]

Approved w/Constraints
[29, 30, 31, 33, 34, 35, 36]

Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39]

SQL Server 2017 Win

Unapproved

SQL Server 2017 Lin

Unapproved

SQL Server 2019 Win

Approved w/Constraints
[17, 23, 24, 27, 28]

Approved w/Constraints
[17, 23, 24, 28, 29]

Approved w/Constraints
[17, 23, 24, 28, 29, 30, 31]

Approved w/Constraints
[29, 30, 31, 32, 33, 34, 35]

Approved w/Constraints
[29, 30, 31, 33, 34, 35, 36]

Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39]

SQL Server 2019 Lin

Approved w/Constraints
[1, 17, 23, 24, 27, 28]

Approved w/Constraints
[1, 17, 23, 24, 28, 29]

Approved w/Constraints
[17, 23, 24, 28, 29, 30, 31]

Approved w/Constraints
[29, 30, 31, 32, 33, 34, 35]

Divest
[29, 30, 31, 32, 33, 34, 35]

Unapproved

SQL Server 2022 Win

Unapproved

Approved w/Constraints
[29, 30, 31, 32, 33, 34, 35]

Approved w/Constraints
[29, 30, 31, 33, 34, 35, 36]

Approved w/Constraints
[31, 33, 35, 36, 37, 38, 39]

SQL Server 2022 Lin

Unapproved

Decision Constraints


[1]	This Technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population.

[2]	VA has a License Agreement in place for this technology. All license needs for this technology should be coordinated through the Technology Innovation Program (TIP). Refer to the license section of this entry for more details. Configuration and deployment standards for SQL Server images and their host Windows Server images are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx Unapproved versions and evaluation versions constrained from full production use can be used only if a waiver, signed by the Deputy CIO of ASD and based upon a recommendation from the AERB, has been granted to the project team or organization that wishes to use the technology. (ref: and FAQ`s #4 and FAQ #5 for information on Decisions and AERB Waivers.) SQL Server 2014 is under evaluation and is currently not approved for production except as part of an official Enterprise System Engineering (ESE) production pilot or production test of this version as approved by ESE Core Systems Engineering. Use of SQL Server 2014 in production should be limited to only solid business cases where the benefit outweighs the risks of operating on the older SQL Server 2012 baseline. In order to use SQL Server 2014, the DISA STIG for SQL Server 2012 must be applied in lieu of a current SQL Server 2014 baseline and this exception reviewed and approved via the AERB waiver process. Once updated STIGs, guidance, and baselines are available for SQL Server 2014, any waivered projects will be expected to migrate to the new SQL Server 2014 standards. SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 should be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012 baseline. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012 must be applied and this exception reviewed and approved via the AERB waiver process.

[3]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[4]	In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process.

[5]	Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities.

[6]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[7]	VA has a License Agreement in place for this technology. All license needs for this technology should be coordinated through the Technology Innovation Program (TIP). Refer to the license section of this entry for more details. Configuration and deployment standards for SQL Server images and their host Windows Server images are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx Unapproved versions and evaluation versions constrained from full production use can be used only if a waiver, signed by the Deputy CIO of ASD and based upon a recommendation from the AERB, has been granted to the project team or organization that wishes to use the technology. (ref: and FAQ`s #4 and FAQ #5 for information on Decisions and AERB Waivers.) SQL Server 2014 is under evaluation and is currently not approved for production except as part of an official Enterprise System Engineering (ESE) production pilot or production test of this version as approved by ESE Core Systems Engineering. Use of SQL Server 2014 in production should be limited to only solid business cases where the benefit outweighs the risks of operating on the older SQL Server 2012 baseline. In order to use SQL Server 2014, the DISA STIG for SQL Server 2012 must be applied in lieu of a current SQL Server 2014 baseline and this exception reviewed and approved via the AERB waiver process. Once updated STIGs, guidance, and baselines are available for SQL Server 2014, any waivered projects will be expected to migrate to the new SQL Server 2014 standards. SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 should be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012 baseline. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012 must be applied and this exception reviewed and approved via the AERB waiver process. SQL Server Reporting Services (SSRS) is not to be used for new projects or added to existing projects until such time as the SSRS product is made fully Section 508 complaint by the vendor. In order to use SSRS in new projects or add SSRS into existing projects after 4/8/2015, the exception must be reviewed and approved via the AERB waiver process.

[8]	As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.

[9]	VA has a License Agreement in place for this technology. All license needs for this technology should be coordinated through the Technology Innovation Program (TIP). Refer to the license section of this entry for more details. Configuration and deployment standards for SQL Server images and their host Windows Server images are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx Unapproved versions and evaluation versions constrained from full production use can be used only if a waiver, signed by the Deputy CIO of ASD and based upon a recommendation from the AERB, has been granted to the project team or organization that wishes to use the technology. (ref: and FAQ`s #4 and FAQ #5 for information on Decisions and AERB Waivers.) SQL Server 2014 is under evaluation and is currently not approved for production except as part of an official Enterprise System Engineering (ESE) production pilot or production test of this version as approved by ESE Core Systems Engineering. Use of SQL Server 2014 in production should be limited to only solid business cases where the benefit outweighs the risks of operating on the older SQL Server 2012 baseline. In order to use SQL Server 2014, the DISA STIG for SQL Server 2012 must be applied in lieu of a current SQL Server 2014 baseline and this exception reviewed and approved via the AERB waiver process. Once updated STIGs, guidance, and baselines are available for SQL Server 2014, any waivered projects will be expected to migrate to the new SQL Server 2014 standards. SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 should be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012 baseline. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012 must be applied and this exception reviewed and approved via the AERB waiver process. Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and should not be used by any end-user applications.

[10]	VA has a License Agreement in place for this technology. All license needs for this technology should be coordinated through the Technology Innovation Program (TIP). Refer to the license section of this entry for more details. Configuration and deployment standards for SQL Server images and their host Windows Server images are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx Unapproved versions and evaluation versions constrained from full production use can be used only if a waiver, signed by the Deputy CIO of ASD and based upon a recommendation from the AERB, has been granted to the project team or organization that wishes to use the technology. (ref: and FAQ`s #4 and FAQ #5 for information on Decisions and AERB Waivers.) SQL Server 2014 and 2016 are under evaluation and are currently not approved for production except as part of an official Enterprise System Engineering (ESE) production pilot or production test as approved by ESE Core Systems Engineering. Use of SQL Server 2014 or 2016 in production should be limited to only solid business cases where the benefit outweighs the risks of operating on the older SQL Server 2012 baseline. In order to use SQL Server 2014 or 2016, the DISA STIG for SQL Server 2012 must be applied in lieu of a current SQL Server 2014 or 2016 baseline and this exception reviewed and approved via the AERB waiver process. Once updated STIGs, guidance, and baselines are available for SQL Server 2014 or 2016, any waivered projects will be expected to migrate to the new SQL Server 2014 or 2016 standards. SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 should be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012 baseline. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012 must be applied and this exception reviewed and approved via the AERB waiver process. Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and should not be used by any end-user applications.

[11]	VA has a License Agreement in place for this technology. All license needs for this technology must be coordinated through the Technology Innovation Program (TIP). Refer to the license section of this entry for more details. Configuration and deployment standards for SQL Server images and their host Windows Server images are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering (ESE) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx Unapproved versions and evaluation versions constrained from full production use can be used only if a waiver, signed by the Deputy CIO of ASD and based upon a recommendation from the AERB, has been granted to the project team or organization that wishes to use the technology. (ref: and FAQ`s #4 and FAQ #5 for information on Decisions and AERB Waivers.) SQL 2016 is under evaluation and are currently not approved for production except as part of an official Enterprise System Engineering (ESE) production pilot or production test as approved by ESE Core Systems Engineering. Use of SQL Server 2016 in production must be limited to only solid business cases where the benefit outweighs the risks of operating on the older SQL Server 2014 baselines. In order to use SQL Server 2016, the DISA STIG for SQL Server 2014 must be applied in lieu of a current SQL Server 2016 baseline and this exception reviewed and approved via the AERB waiver process. Once updated STIGs, guidance, and baselines are available for SQL Server 2016, any waivered projects will be expected to migrate to the new SQL Server 2016 standards. SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012 or 2014 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012 or 2014 must be applied and this exception reviewed and approved via the AERB waiver process. Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications.

[12]	VA has a License Agreement in place for this technology. All license needs for this technology must be coordinated through the Technology Innovation Program (TIP). Refer to the license section of this entry for more details. Configuration and deployment standards for SQL Server images and their host Windows Server images are defined and maintained by the Core Systems Engineering organization within VA Solution Delivery (SD) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx SQL 2016 requires risk acceptance and mitigation by the implementing organization approved by the project ISO. While Solution Delivery highly recommends that no project in VA use SQL Server 2016 until the DISA STIGs are released and the corresponding VA baseline for SQL Server 2016 is ratified, there are some projects within VA that are willing to accept the risks of not following the recommendations of Solution Delivery. The risk and responsibility of proceeding to use SQL Server 2016 Database and applying the SQL Server 2014 baseline to it, rests solely with the project. Solution Delivery does not endorse or advocate proceeding without an established baseline utilizing published SQL Server 2016 DISA STIGs. See the SQL Server 2016 Alpha Baseline in the reference tab for more information. SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012 or 2014 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012 or 2014 must be applied and this exception reviewed and approved via the STAT waiver process. Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications.

[13]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[14]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[15]	VA has a License Agreement in place for this technology. All license needs for this technology must be coordinated through the Technology Innovation Program (TIP). Refer to the license section of this entry for more details. Configuration and deployment standards for SQL Server images and their host Windows Server images are defined and maintained by the Core Systems Engineering organization within VA Solution Delivery (SD) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx At this time there is no VA baseline for SQL Server 2017. Until a baseline has been created and published on the BCM website, SQL Server 2017 is unapproved. Users may use SQL Server 2012, 2014 and also 2016 with risk acceptance and following all listed constraints. SQL 2016 requires risk acceptance and mitigation by the implementing organization approved by the project ISO. While Solution Delivery highly recommends that no project in VA use SQL Server 2016 until the DISA STIGs are released and the corresponding VA baseline for SQL Server 2016 is ratified, there are some projects within VA that are willing to accept the risks of not following the recommendations of Solution Delivery. The risk and responsibility of proceeding to use SQL Server 2016 Database and applying the SQL Server 2014 baseline to it, rests solely with the project. Solution Delivery does not endorse or advocate proceeding without an established baseline utilizing published SQL Server 2016 DISA STIGs. See the SQL Server 2016 Alpha Baseline in the reference tab for more information. SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012 or 2014 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012 or 2014 must be applied and this exception reviewed and approved via the STAT waiver process. Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications.

[16]	This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004, VA Directive 6517 and VA Directive 6513. The local ISO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place.

[17]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities.

[18]	VA has a License Agreement in place for this technology. All license needs for this technology must be coordinated through the Technology Innovation Program (TIP). Refer to the license section of this entry for more details. Configuration and deployment standards for SQL Server images and their host Windows Server images are defined and maintained by the Core Systems Engineering organization within VA Solution Delivery (SD) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx At this time there is no VA baseline for SQL Server 2017. Until a baseline has been created and published on the BCM website, SQL Server 2017 is unapproved. Users may use SQL Server 2012, 2014, and 2016 following all listed constraints. SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012, 2014, or 2016 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012, 2014, or 2016 must be applied and this exception reviewed and approved via the STAT waiver process. Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications.

[19]	Users must ensure they are only using Structured Query Language (SQL) Server with Windows Platforms Structured Query Language (SQL) Server 2017 and 2019 are in planning and only Solution Delivery Platform Engineering may use or authorize the technology for planning and pilot evaluation purposes until the VA baseline for SQL Server 2017 and 2019 is published. No production deployment date for SQL Server 2017 and 2019 have been set as of this writing. VA has a License Agreement in place for this technology. All license needs for this technology must be coordinated through the Technology Innovation Program (TIP). Refer to the license section of this entry for more details. Configuration and deployment standards for SQL Server images and their host Windows Server images are defined and maintained by the Core Systems Engineering organization within VA Solution Delivery (SD) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012, 2014, or 2016 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012, 2014, or 2016 must be applied and this exception reviewed and approved via the STAT waiver process. Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications.

[20]	This Technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. Contact your local CIO office if more information is needed in regards to the use of this technology.

[21]	Users must ensure they are only using Structured Query Language (SQL) Server with Windows Platforms Structured Query Language (SQL) Server 2019 is in planning and only Solution Delivery Platform Engineering may use or authorize the technology for planning and pilot evaluation purposes until the VA baseline for SQL Server 2019 is published. No production deployment date for SQL Server 2019 have been set as of this writing. As of this writing VA has no plans to support SQL Server 2017 and will bypass support of this version. VA has a License Agreement in place for this technology. All license needs for this technology must be coordinated through the Technology Innovation Program (TIP). Refer to the license section of this entry for more details. Configuration and deployment standards for SQL Server images and their host Windows Server images are defined and maintained by the Core Systems Engineering organization within VA Solution Delivery (SD) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012, 2014, or 2016 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012, 2014, or 2016 must be applied and this exception reviewed and approved via the STAT waiver process. Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications.

[22]	Users must ensure they are only using Structured Query Language (SQL) Server with Windows Platforms As of this writing VA has no plans to support SQL Server 2017 and will bypass support of this version. VA has a License Agreement in place for this technology. All license needs for this technology must be coordinated through the Technology Innovation Program (TIP). Refer to the license section of this entry for more details. Configuration and deployment standards for SQL Server images and their host Windows Server images are defined and maintained by the Core Systems Engineering organization within VA Solution Delivery (SD) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, and 2008 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2012, 2014, 2016 or 2019 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2012, 2014, or 2016 must be applied and this exception reviewed and approved via the POAM process. Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications.

[23]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[24]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[25]	This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004, VA Directive 6517 and VA Directive 6513. The local ISO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place.

[26]	Users must ensure they are only using Structured Query Language (SQL) Server with Windows Platforms Users much ensure that Microsoft Structured Query Language (SQL) Server is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) As of this writing VA has no plans to support SQL Server 2017 and will bypass support of this version. VA has a License Agreement in place for this technology. All license needs for this technology must be coordinated through the Technology Innovation Program (TIP). Refer to the license section of this entry for more details. Configuration and deployment standards for SQL Server images and their host Windows Server images are defined and maintained by the Core Systems Engineering organization within VA Solution Delivery (SD) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, 2008 and 2012 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2014, 2016 or 2019 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2014, or 2016 must be applied and this exception reviewed and approved via the POAM process. Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications.

[27]	At the time of writing, the baseline configuration supports only Windows Server installations. Users must not utilize this technology on Linux environments until a baseline configuration is developed for Linux systems. As of this writing VA has no plans to support SQL Server 2017 and will bypass support of this version. VA has a License Agreement in place for this technology. All license needs for this technology must be coordinated through the Technology Innovation Program (TIP). Refer to the license section of this entry for more details. Configuration and deployment standards for SQL Server images and their host Windows Server images are defined and maintained by the Core Systems Engineering organization within VA Solution Delivery (SD) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, 2008 and 2012 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2014, 2016 or 2019 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2014, or 2016 must be applied and this exception reviewed and approved via the POAM process. Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications.

[28]	In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISO can advise on the ESCCB review process.

[29]	At the time of writing, the baseline configuration supports only Windows Server installations. Users must not utilize this technology on Linux environments until a baseline configuration is developed for Linux systems. As of this writing VA has no plans to support SQL Server 2017 and will bypass support of this version. VA has a License Agreement in place for this technology. All license needs for this technology must be coordinated through the Technology Innovation Program (TIP). Refer to the license section of this entry for more details. Configuration and deployment standards for SQL Server images and their host Windows Server images are defined and maintained by the Core Systems Engineering organization within VA Solution Delivery (SD) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx SQL Server 2000, 2005, and 2008 are unapproved. Therefore, use of SQL Server 2000, 2005, 2008 and 2012 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2016 or 2019 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2014, or 2016 must be applied and this exception reviewed and approved via the POAM process. Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications.

[30]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the VA OIT Product Engineering team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[31]	This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product.

[32]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

[33]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities.

[34]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[35]	In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISSO (Information System Security Officer) can advise on the ESCCB review process.

[36]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

[37]	At the time of writing, the baseline configuration supports only Windows Server installations. Users must not utilize this technology on Linux environments until a baseline configuration is developed for Linux systems. As of this writing VA has no plans to support SQL Server 2017 and will bypass support of this version. VA has a License Agreement in place for this technology. All license needs for this technology must be coordinated through the Technology Innovation Program (TIP). Refer to the license section of this entry for more details. Configuration and deployment standards for SQL Server images and their host Windows Server images are defined and maintained by the Core Systems Engineering organization within VA Solution Delivery (SD) and must be followed and adhered to unless an appropriate waiver is granted. Detailed information can be found at the following location: https://dvagov.sharepoint.com/sites/OITBCM/lists/secure_configuration_baselines/generalview.aspx SQL Server 2000, 2005, 2008, and 2012 are unapproved. Therefore, use of SQL Server 2000, 2005, 2008 and 2012 must be limited to only solid business cases where the benefit outweighs the risks of operating to the newer SQL Server 2016 or 2019 baselines. In order to use older versions of SQL Server, the DISA STIG for SQL Server 2014, or 2016 must be applied and this exception reviewed and approved via the POAM process. Windows Internal Database (WID) is a variant of SQL Server Express 2005-2012 that is included with Windows Server and other free Microsoft products released after 2007 that require a SQL Server database backend. Windows Internal Database (WID) is authorized only for use by the Microsoft products that include it by design and must not be used by any end-user applications. Users must not utilize Structured Query Language (SQL) Backup Pro, as it is at the time of writing, unapproved in the TRM.

[38]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes.

[39]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request, visit the Product Marketplace. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

Note:

At the time of writing, version 2022 (Windows & Linux) build 2022.160.4105.2 is the most current version.
A baseline configuration of this technology was developed by the BCM team. At the time of writing, the approved baseline versions are 2016, 2019, & 2022. The VA will bypass usage of SQL Server 2017.

The following reference(s) are associated with this entry:
Type	Name	Source	Description
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
Master Data Services (MDS)	Master Data Services (MDS) is the SQL Server solution for master data management. Master data management (MDM) describes the efforts made by an organization to discover and define non-transactional lists of data, with the goal of compiling maintainable master lists.
Microsoft Azure Structured Query Language (SQL) Server	Azure SQL Database is an always-up-to-date, fully managed relational database service built for the cloud. This site provides an overview of Microsoft Azure Structured Query Language (SQL) Server, the cloud implementation of Microsoft Structured Query Language (SQL) Server.
Microsoft Connectors for Oracle and Teradata by Attunity	Developed by Attunity with Microsoft, these connectors use direct integration into internal SSIS buffering APIs, cutting through .NET and other layers. These connectors also use the high speed load/extract utilities offered by Oracle and Teradata. Microsoft provides versions of these connectors that support corresponding specific versions of SQL Server. These connectors may be used with all approved versions of SQL Server identified by this TRM entry.
Microsoft Object Linking and Embedding, Database (OLE DB) Driver for SQL Server	OLE DB Driver for SQL Server was designed to provide a simplified method of gaining native data access to SQL Server using OLE DB. It provides a way to innovate and evolve new data access features without changing the current Windows Dynamic Access Control (DAC) components, which are now part of the Microsoft Windows platform.
Microsoft Open Database Connectivity (ODBC) Driver for Structured Query Language (SQL) Server	ODBC is the primary native data access application programming interface (API) for applications written in C and C++ for SQL Server.
Microsoft SQL Server T-SQL ScriptDom	ScriptDom being a full-fidelity parser, is great for statically analyzing Transact-SQL (T-SQL) code to proactively identify anti-patterns.
Microsoft Structured Query Language (SQL) Server Data-Tier Application Framework	A data-tier application (DAC) is a logical database entity that defines all of the SQL Server objects - such as tables, views, and instance objects, including logins - associated with a user`s database.
Microsoft Structured Query Language (SQL) Server Setup	SQL Server Setup includes a shared feature option for installing a standalone machine learning server that runs outside of SQL Server. It`s called Machine Learning Server (Standalone) and includes Python and R.
Microsoft Structured Query Language (SQL) Server Volume Shadow Copy Service (VSS) Writer (an extension of Windows Server VSS)	The SQL Writer Service provides added functionality for backup and restore of SQL Server through the Volume Shadow Copy Service framework. Volume Shadow Copy Service is a part of the Windows Server Operating system and is approved as part of that TRM entry. The Microsoft SQL Server Writer Service is a component of SQL Server that allows SQL Server to utilize VSS.
Structured Query Language (SQL) Server - Analysis Services (SSAS)	Microsoft SQL Server Analysis Services (SSAS) is an Online Analytical Processing, OLAP, data mining and reporting tool in Microsoft SQL Server.
Structured Query Language (SQL) Server Browser	The SQL Server Browser program runs as a Windows service. SQL Server Browser listens for incoming requests for Microsoft SQL Server resources and provide information about SQL Server instances installed on the computer.
Structured Query Language (SQL) Server Data Quality Services (DQS)	SQL Server Data Quality Services (DQS) is a knowledge-driven data quality component for data cleansing that consists of the Data Quality Server and the Data Quality Client.
Structured Query Language (SQL) Server Enterprise Manager	SQL Server Enterprise Manager is the primary administrative tool for Microsoft SQL Server 2000 and provides a Microsoft Management Console (MMC) compliant user interface. This component became SQL Server Management Studio (SSMS) in later releases.
Structured Query Language (SQL) Server Integration Services (SSIS)	SQL Server Integration Services (SSIS) enables you to utilize extract, transform and load (ETL) data from any data source type without the need for direct coding.
Structured Query Language (SQL) Server Management Studio (SSMS)	SQL Server Management Studio (SSMS) is an integrated environment for accessing, configuring, managing, administering, and developing all components of SQL Server. Note: Beginning with MS SQL Server 2016 SQL Server Management Studio (SSMS) will no longer be a component of the SQL Server database engine. SSMS will be an independent software requiring its own install. SSMS is only a component of MS SQL Server 2014 and earlier. A new TRM entry has been created for SSMS, please reference this entry for the latest versions and features of SSMS.
Structured Query Language (SQL) Server Native Client	SQL Server Native Client, also known as SQL Server Native Client (SNAC), refers to the Open Database Connectivity (ODBC) and Object Linking and Embedding, Database (OLE DB) drivers for SQL Server, prior to SQL Server 2022 (16.x).
Structured Query Language (SQL) Server Reporting Services (SSRS)	SQL Server Reporting Services (SSRS) is a server-based report generation software system that is included in most versions SQL Server. Report Builder is a component of the SQL Server Reporting Services (SSRS); however, Report Builder does have its own TRM entry because Report Builder can be installed as stand-alone software.
Transact-SQL (T-SQL) reference (Database Engine)	T-SQL is central to using Microsoft Structured Query Language (SQL) products and services. All tools and applications that communicate with a SQL Server database do so by sending T-SQL commands.
Visual Studio 2010 Shell is installed with Structured Query Language (SQL) Server 2014 and 2012	When you install SQL Server 2014 or SQL Server 2012, you find that SSMS requires Visual Studio 2010 Shell (Isolated) and SSDT requires Visual Studio 2010 Shell (Integrated). SQL Server Management Studio (SSMS) ships with SQL Server Database Engine in those versions. According to Microsoft lifecycle policy of Visual Studio 2010, the support ended on July 14, 2020. However, if Visual Studio 2010 Shell (Isolated) or Shell (Integrated) is installed with SQL Server 2014 or SQL Server 2012, Visual Studio 2010 Shell will be supported until the end of support for SQL Server 2014 (July 09, 2024) or for SQL Server 2012 (July 12, 2022).


Information Management Technologies Data Management	Relational DBMS	Microsoft SQL Server and Oracle DB are the preferred Relational DBMS platforms in VA. Per ELT decision, all future requests for Relational DBMS technologies will be Unapproved.	1/13/2015 12:00:00 AM

- The information contained on this page is accurate as of the Decision Date (03/18/2024 at 23:38:56 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (03/13/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (03/13/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES