2 Made a few changes to improve the quality on content
source | link

After a lot of digging around, I coulddidn’t get an answer andanywhere, then eventually I got Microsoft involved to help me with the problem.

MS solution architect confirmed that the Report Builder requires a direct connection to SQL Server when launched hence the working with data sets in the report builder failed. Apparently this is BY DESIGN and it is not going to change.

This was in SQL Server 2008 R2 but the same is true for SQL Server 2012, 2014 and 2016. Not sure about 2017 but I doubt it very much if that this has changed in 2017.

We ended up provided aproviding the client a machine on the network in DMZ to which end users connected remotely, only to work with the Report builder, it is a poor solution but it worked at that time and we needed a quick fix for it at that time.

After a lot of digging around I could get an answer and then eventually I got Microsoft involved to help me the problem.

MS solution architect confirmed that the Report Builder requires a direct connection to SQL Server when launched hence the working with data sets in the report builder failed. Apparently this is BY DESIGN and it is not going to change.

This was in SQL Server 2008 R2 but the same is true for SQL Server 2012, 2014 and 2016. Not sure about 2017 but I doubt it very much that this has changed in 2017.

We ended up provided a client machine on the network to which end users connected remotely only to work with Report builder, it is a poor solution but it worked at that time and we needed a quick fix for it at that time.

After a lot of digging around, I didn’t get anywhere, then eventually I got Microsoft involved to help me with the problem.

MS solution architect confirmed that the Report Builder requires a direct connection to SQL Server when launched hence the working with data sets in the report builder failed. Apparently this is BY DESIGN and it is not going to change.

This was in SQL Server 2008 R2 but the same is true for SQL Server 2012, 2014 and 2016. Not sure about 2017 but I doubt it very much if that has changed in 2017.

We ended up providing the client a machine on the network in DMZ to which end users connected remotely, only to work with the Report builder, it is a poor solution but it worked at that time and we needed a quick fix for it at that time.

1
source | link

After a lot of digging around I could get an answer and then eventually I got Microsoft involved to help me the problem.

MS solution architect confirmed that the Report Builder requires a direct connection to SQL Server when launched hence the working with data sets in the report builder failed. Apparently this is BY DESIGN and it is not going to change.

This was in SQL Server 2008 R2 but the same is true for SQL Server 2012, 2014 and 2016. Not sure about 2017 but I doubt it very much that this has changed in 2017.

We ended up provided a client machine on the network to which end users connected remotely only to work with Report builder, it is a poor solution but it worked at that time and we needed a quick fix for it at that time.