Forum Discussion
Gateway - Data Source best practice
I would use a single source for the top most folder. Performance will be the same but maintenance will be simpler.
Thank you for this reply, lbendlin . I really appreciate your time and thoughts.
In our current state of affairs (I think often of Ellie Arroway's response to Congress when asked what she'd ask an intelligent being, should she encounter one on her trip through space: "...how did you survive this technological adolescence without destroying yourself?"), we have a system user permissioned at the gateway who that then, in turn, has server/database/schema access to our various SQL servers (down to EXEC permission by schema). This doesn't necessarily address the oversharing issue, but we're only a team of 4 on the reporting team, and we're trying to come up with ways to leverage dataflows that we can use to enable self-service access for the other folks in our org (premium capacity).
I think our infrastucture team was looking at the proliferation of data sources on our main gateway and thinking, "there's got to be a better way." But maybe there's not? Lots still to learn. Thanks again for your time!
We are pushing the rope on that one too. For example we do not allow file connections on our enterprise gateways (we tell users to use folder/sharepoint folder connections). But we also have data sources where we absolutely must separate the users, so we have no choice but to duplicate the connection.
The gateway management pages have gotten a bit better at handling many hundreds of connections. The REST API also helps to mitigate some of the extra effort (although it is missing critical parts like connection user role management or connection test skipping)