Title
SQL Server 2022 RTM (16.0.1000.6): Are R and Python external language catalog entries created by default?
Question
Hello Microsoft SQL Server Team,
We are validating the catalog baseline of an isolated SQL Server 2022 Developer Edition test environment.
Environment
- SQL Server 2022 Developer Edition (64-bit), version 16.0.1000.6 (RTM)
-
external scripts enabled: configured = 0, value_in_use = 0
-
IsAdvancedAnalyticsInstalled: 0
- No SQL Server Launchpad service was detected.
Observed catalog entries
The sys.external_languages catalog contains exactly two rows:
- R:
external_language_id = 1
- Python:
external_language_id = 2
Both rows have owner sys, principal_id = 4, owner type SQL_USER, and create_date = 2022-10-08 06:28:42.823.
The sys.external_language_files catalog contains exactly four associated rows:
- R, Windows (1):
RLauncher.dll
- R, Linux (2):
RLauncher.so
- Python, Windows (1):
PythonLauncher.dll
- Python, Linux (2):
PythonLauncher.so
We observed no parameters or environment variables in any of the four rows.
Questions
- Does a clean installation of SQL Server 2022 Developer Edition RTM create these two external-language rows and four associated file rows by default, even when Machine Learning Services is absent and external scripts are disabled?
- Is ownership by
sys with principal_id = 4 expected for these rows?
- Are the language IDs, platform mappings, and file names part of a documented system baseline? Which properties are guaranteed for this build, and which may vary between installations?
- Is there an official version-specific reference, installation manifest, or supported catalog property that distinguishes system-generated entries from unexpected or user-created entries?
- How does Microsoft recommend validating these entries without executing external scripts, enabling additional features, or modifying the database?
Why we need this confirmation
Our database qualification process uses a fail-closed catalog security guard that currently rejects any entry in sys.external_languages. We want to determine whether a narrowly defined exception for verified system-generated entries is appropriate while continuing to reject unexpected external-language objects.
We are seeking authoritative evidence specific to SQL Server 2022 RTM build 16.0.1000.6. References to official Microsoft documentation or confirmation from the SQL Server engineering team would be appreciated.
Thank you.