Geek asks and answers

TSQLt TRUSTWORTHY and CLR requirement

For tSQLt, to check the database, you must set TRUSTWORTHY ON for the database and enable SQL CLR for the server.

Why is this required? Is it possible to achieve the same / similar functionality without a CLR object?

+3
source share
3 answers

The following functions are fully implemented as CLR code, and it would be especially difficult (and possibly impossible) to do without CLR:

  • CaptureOuput: Useful for recording and checking output printed on the console.
  • SuppressOutput: Used internally to help clear the console of warnings that result from renaming objects (especially in FakeTable).
  • ResultSetFilter: , , .
  • AssertResultSetsHaveSameMetaData: .
  • NewConnection: SQL . , . ( , TRUSTWORTHY ON ).

, tSQLt CLR , , ; (, FakeTable SpyProcedure).

, tSQLt , - ( , ). , , tSQLt, , CLR .

+4

tSQLt, , , , SQL CLR.

TRUSTWORTHY ON, - . http://msdn.microsoft.com/en-us/library/ms345106.aspx.

, , - DbFit

+2

More articles:


All Articles