tag:blogger.com,1999:blog-1043329399531776224.post5003171284715670359..comments2014-08-14T02:10:57.679-07:00Comments on Developer Diary of Johan Sivertsen: SqlDataConnection and wasted timeAnonymoushttp://www.blogger.com/profile/06267922992176929546noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-1043329399531776224.post-33947174949518146472014-05-19T19:38:55.755-07:002014-05-19T19:38:55.755-07:00Looks like you don't have permission to access...Looks like you don't have permission to access the metadata table syscomments (or it doesn't exist). I haven't used Azure unfortunately but you might try a simple select * from syscomments as that same account to verify if you can see the metadata. If you can't, the connector is going to have a hard time working out all the types.Anonymoushttps://www.blogger.com/profile/11492394964570720228noreply@blogger.comtag:blogger.com,1999:blog-1043329399531776224.post-20167016755295533912014-05-19T07:05:04.967-07:002014-05-19T07:05:04.967-07:00I had a coworker express a similar problem with th...I had a coworker express a similar problem with this and the SqlDataConnection type provider. I don't recall whether he ever go that working or not. However, we typically use the SqlCommandProvider (https://github.com/fsprojects/FSharp.Data.SqlClient). This let's you just write the SQL you want and type checks its validity, generating types for you. It has worked great with Azure SQL Database. Another you might try is the SQLProvider (https://github.com/fsprojects/SQLProvider), which is closer in concept to the SqlEntityConnection provider.Ryanhttps://www.blogger.com/profile/10643337675808040478noreply@blogger.comtag:blogger.com,1999:blog-1043329399531776224.post-9482563379566177442014-05-19T07:03:56.053-07:002014-05-19T07:03:56.053-07:00This comment has been removed by the author.Anonymousnoreply@blogger.com