Hi All,
A number of users here at the RA have found that having direct access to the database would greatly facilitate their work. I know that there are security issues involved, but none of us here are Microsoft server experts, so I was wondering if someone could explain why server partitioning for different organisations as described here https://docs.microsoft.com/en-us/azure/architecture/best-practices/data-partitioning, coupled with use of asymmetric keys (https://docs.microsoft.com/en-us/sql/relational-databases/security/sql-server-certificates-and-asymmetric-keys?view=sql-server-ver15) would still cause issues.
The main use cases our team has found are:
Directly querying data with python through a SQL connection would greatly streamline workflow for analysis, and might actually be necessary to create self-updating algorithms.
The software development team here use DataGrip (https://www.jetbrains.com/datagrip/) - an IDE that allows access to MySQL, PostrgreSQL and MSSQL in one place. We can now work on all our other databases in one place and it would be a huge help to access Tessitura's MSSQL server in the same way.
Is there any way we could have this access now? Is this a functionality that is being considered for future releases?
Thanks,
Carlo
Good afternoon,
Circling back from a RAMP perspective. The impresario (Tessitura) database contains both payment card data and personally identifiable information; direct database connections do not allow for the level of security and inspection required by PCI or GDPR, therefore the recommended practice is to use the APIs which are coded to comply with both PCI/PA-DSS and GDPR regulations. We will reach out offline to discuss what you are trying to accomplish and help with some resources to get you pointed in the right direction.
Anna
Anna Wessely (Past Staff Member),
Could you please share the resources with me as well? We are in a similar situation.
Thank you,
Rachel
I'd like to understand what policy is as well.
--Tom