We are observing inconsistent behavior of a SQL Server system stored procedure across different execution environments.
The following query executes successfully on a **standard physical Windows environment**:
```sql
EXEC sp_columns_ex
@table_server = N'<ServerName>',
@table_name = N'<TableName>';
```
However, when the same query is executed from an application running inside a **containerized / virtualized Windows environment (KubeVirt)**, the procedure does not return any result and appears to remain blocked indefinitely. No SQL error or exception is reported.
Additional details:
* Database connection is established successfully
* Other SQL queries and stored procedures execute without issue
* Same SQL Server instance and database are used in both environments
* The issue is isolated to `sp_columns_ex`
* Increasing client-side command timeout does not resolve the behavior
This suggests a possible dependency on environment-specific metadata resolution or client/driver behavior.
**Queries for clarification:**
1. Is `sp_columns_ex` deprecated or known to have limitations in containerized or virtualized Windows environments?
2. Are there any SQL Server or client configuration settings that influence its execution?
3. What is the recommended, supported approach to retrieve table column metadata in an environment-independent manner?
Any guidance or best practices would be appreciated.