Azure SQL time Data Type Throws Error on Linked Server Query

Azure SQL time Data Type Throws Error on Linked Server Query by Kalman Toth

Closed

as Won't Fix Help for as Won't Fix

Type:	Bug
ID:	780161
Opened:	2/27/2013 2:36:40 PM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

Here is the error with time data type:

SELECT * FROM [GAMMA_AZURE].AdventureWorks2012.HumanResources.Shift;
/*
Msg 7347, Level 16, State 1, Line 1
OLE DB provider 'MSDASQL' for linked server 'GAMMA_AZURE' returned data that does not match
expected data length for column '[GAMMA_AZURE].[AdventureWorks2012].[HumanResources].[Shift].StartTime'.
The (maximum) expected data length is 16, while the returned data length is 12.
*/

SELECT * FROM OPENQUERY([GAMMA_AZURE], 'SELECT * FROM AdventureWorks2012.HumanResources.Shift');
/*
Msg 7347, Level 16, State 1, Line 1
OLE DB provider 'MSDASQL' for linked server 'GAMMA_AZURE' returned data that does not match
expected data length for column '[MSDASQL].StartTime'. The (maximum) expected data length is 16,
while the returned data length is 12.
*/

Details (expand)

English

SQL Server 2012 - Developer Edition

SQL Azure Database

Windows 7 Professional

US English

Setup linked server to Azure SQL Database.

Query a table with time(7) data type.

SELECT * FROM [GAMMA_AZURE].AdventureWorks2012.HumanResources.Shift;

SELECT * FROM [GAMMA_AZURE].AdventureWorks2012.HumanResources.Shift;
/*
Msg 7347, Level 16, State 1, Line 1
OLE DB provider 'MSDASQL' for linked server 'GAMMA_AZURE' returned data that does not match
expected data length for column '[GAMMA_AZURE].[AdventureWorks2012].[HumanResources].[Shift].StartTime'.
The (maximum) expected data length is 16, while the returned data length is 12.
*/

SELECT * FROM OPENQUERY([GAMMA_AZURE], 'SELECT * FROM AdventureWorks2012.HumanResources.Shift');
/*
Msg 7347, Level 16, State 1, Line 1
OLE DB provider 'MSDASQL' for linked server 'GAMMA_AZURE' returned data that does not match
expected data length for column '[MSDASQL].StartTime'. The (maximum) expected data length is 16,
while the returned data length is 12.
*/

Data rows

0 attachments

The bug appears to be in the SQL Server 2012 metadata discovery stored procedure sys.sp_describe_first_result_set.
There is a MSDN Forum item with some more details on this topic: http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/487841e4-0107-4209-b6d9-e9af12af3f58