User Profile
pabechevb
Copper Contributor
Joined 5 years ago
User Widgets
Recent Discussions
Re: Polybase for D365 Datalake
datascientist1 take a detailed look at the error message, you must specify the collation when creating the external table definition, it's not enough to have the names and data types. Just add "collate SQL_Latin1_General_CPI_CS_AS" as indicated, and in the columns specified in the error message, and you'll be good to go.586Views0likes0CommentsRe: Polybase TSQL Compare Issues
Tenagra how did you generate the T-SQL for creating the external table? I've found issues when there's anything different, so a trick I use is to let Polybase tell me what data types it is seeing, for example "create external table p.Account (dummy int) with (location='account', data_source=[DataSource]);", then the error returned will tell me exactly what are the columns and collations I must use when creating the external table, so I just replace the dummy T-SQL with the one returned. I'm guessing between the NUMERIC(20,0) and the INT, Polybase is trying to do a conversion within the SQL statement being sent to MySQL, which the ODBC is catching up and failing before sending the request to MySQL. You can also try doing the conversion from NUMERIC(20,0) to INT before the table join and see what happens.1.7KViews0likes0Comments
Recent Blog Articles
No content to show