Why is RedGate SQL Test still turning TRUSTWORTHY on?
We are running SQL 2017, and RedGate's documentation (https://documentation.red-gate.com/display/SQT3/Adding+a+database+to+SQL+Test) says that turning TRUSTWORTHY on is still necessary for MS SQL Server 2017 and higher.
I've verified that we are using the latest version of the opensource tSQLt framework, and the documentation for that page implies that the TRUSTWORTHY option should not be necessary (https://tsqlt.org/748/tsqlt-v1-0-5873-27393-release-notes/).
Reading Phil Factor's postings on intrusion detection (https://www.red-gate.com/hub/product-learning/sql-monitor/spotting-unauthorized-configuration-settings-sql-server) and other postings such as https://www.sqlservercentral.com/blogs/please-please-please-stop-using-impersonation-trustworthy-and-cross-db-ownership-chaining, TRUSTWORTHY is consistently listed as bad practice. Consequently I would like to turn it off. But I can't risk compromising our SQL Test unit tests.
Why is SQL Test still requiring this option when the framework says it is not necessary?
Thank you in advance,
DBAJohnny
I've verified that we are using the latest version of the opensource tSQLt framework, and the documentation for that page implies that the TRUSTWORTHY option should not be necessary (https://tsqlt.org/748/tsqlt-v1-0-5873-27393-release-notes/).
Reading Phil Factor's postings on intrusion detection (https://www.red-gate.com/hub/product-learning/sql-monitor/spotting-unauthorized-configuration-settings-sql-server) and other postings such as https://www.sqlservercentral.com/blogs/please-please-please-stop-using-impersonation-trustworthy-and-cross-db-ownership-chaining, TRUSTWORTHY is consistently listed as bad practice. Consequently I would like to turn it off. But I can't risk compromising our SQL Test unit tests.
Why is SQL Test still requiring this option when the framework says it is not necessary?
Thank you in advance,
DBAJohnny
