Search

PowerPivot (2013) No columns detected by IdahoGal1

Active

1
0
Sign in
to vote
Type: Bug
ID: 777421
Opened: 1/24/2013 9:52:29 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
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 #TempSQLInstances
WHERE [Server] IS NOT NULL

to this:

SELECT [Division], [Domain], [Organization], [Team], [Environment],
             [Server], [InstanceName], [DatabaseName], [LogFile], [VLF Count],
             [LogFileSize], [Number of Log Files], [CollectionDate]
FROM #TempSQLInstances
WHERE [Server] IS NOT NULL
Details (expand)

Product Language

English

Version

SQL Server 2012 SP1

Category

Analysis Services

Operating System

Windows 7 Enterprise

Operating System Language

US English

Steps to Reproduce

Create an sproc that returns a result set with more than 9 aliased columns. See details in description above.

Actual Results

The data connector started failing once the additional column name was added with the error message ‘SQL statement is not valid. There are no columns detected in the statement’

Expected Results

I expected the data connection to validate and return results.    Once I removed the aliased column names, it succeeded.

Platform

32

Virtualization

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 2/12/2013 at 12:37 PM
Hello,

Thank you for filling this issue. We will look at this for a future release.

Thanks,
The Analysis Services Team
Sign in to post a workaround.