Now here’s a catch. I was trying all night long to figure out why Visual Studio was hanging on me, every time I wanted to add a Teradata based relational data source. Turns out that the list of available objects gets populated with all the objects in the current server, regardles of permissions. So connecting this way to a medium sized server, may take 20 minutes, which is unusually slow IMO.
Usually I am very patient, but this one I didn’t have time to wait for. Luckily a co-worker made me wait it out and I could move on…
3 thoughts on “Teradata based Data Source Views in Analysis Services”
Wow great article
I guess Jens, in order to overcome this condition we have to use RESTRICT to SCHEMA feature and give the appropriate databse name in that Text Box.
Yeah, so once you find out that a database in Teradata in some ways act as SCHEMA in SQL Server, you can actually get some throughput 🙂
Thanks for the comment