I had a working powerpivot model (Excel 2013) that called an sproc in the data connector. When I added a single additional column to the select statement in the sproc, validation of the data connection immediately started failing with ‘SQL statement is not valid. There are no columns detected in the statement’. The SQL logic already included a statement for ‘SET NOCOUNT ON’ and I manually verified that none of the statements in the sproc were returning any rows except the select statement. The work-around turned out to be to modified the SELECT logic in the sproc to NOT alias any column names and now the validation and query run. In order to get the data connection to validate and return results, the SELECT statement was modified from this: SELECT [Division] as 'Division', [Domain] as 'Domain', [Organization] as 'Organization', [Team] as 'Team', [Environment] as 'Environment', [Server] as 'Server', InstanceName as 'InstanceName', DatabaseName as 'DatabaseName', [LogFile] as 'LogFile', [VLF Count] as 'VLF Count', [LogFileSize] as 'LogFileSize', [Number of Log Files] as 'Number of Log Files', CollectionDate as 'CollectionDate'FROM #TempSQLInstancesWHERE [Server] IS NOT NULLto this:SELECT [Division], [Domain], [Organization], [Team], [Environment], [Server], [InstanceName], [DatabaseName], [LogFile], [VLF Count], [LogFileSize], [Number of Log Files], [CollectionDate] FROM #TempSQLInstancesWHERE [Server] IS NOT NULL
Product Language
Version
Category
Operating System
Operating System Language
Steps to Reproduce
Actual Results
Expected Results
Platform
Virtualization