January 7, 2015 at 8:11 pm
Comments posted to this topic are about the item Installing tSQLt
January 7, 2015 at 10:44 pm
A quick edit:
Soundforge.net
should be:
Sourceforge.net
January 8, 2015 at 9:41 am
January 8, 2015 at 10:16 am
Robert.Sterbal (1/7/2015)
A quick edit:Soundforge.net
should be:
Sourceforge.net
Thanks
January 8, 2015 at 10:16 am
March 11, 2016 at 5:03 am
Our team did evaluate tSQLt framework for a data comparison project that we undertook a while ago. What we found was that tSQLt simply started to hang up for very long periods of time (we would wait for hours and ultimately kill it) when attempting to process a large amount of data (>10,000 records) and was especially bad if we had non-relational data (e.g. XML) on the record.
Our fall back was a comparison using RedGate SQL DataCompare (which worked like a charm, by the way :-))
Thanks & Regards,
Nakul Vachhrajani.
http://nakulvachhrajani.com
Follow me on
Twitter: @sqltwins
March 11, 2016 at 1:44 pm
Your tests shouldn't be processing that much data. Use test data that represents what you want to test, which should be a few documents.
This isn't really built for scale/performance testing.
March 19, 2016 at 7:23 am
As of the 1/31/2016 release you needn't set TRUSTWORTHY to ON.
March 19, 2016 at 11:43 am
Good catch and thanks
January 17, 2019 at 2:21 am
Hello all,
I know this is an old thread but any feedback would be appreciated.
I am busy implementing tSQLt in my SSDT project.
I am considering a dedicated database approach, in that each developer has their own copy of the db to develop on.
Does anyone have any thoughts / advice as to where the tSQLt framework should sit in terms of the database it is installed on?
Do you advise it being installed in your dev database or a separate unit tests database?
January 17, 2019 at 9:18 am
This needs to be in the database in which it will work. I don't think you can set this in a separate database.
January 17, 2019 at 11:09 pm
Ok great. Thanks Steve, I appreciate your feedback.
January 18, 2019 at 12:52 am
With SQLServer 2017 or the current Azure SQL Managed Instance, you also need to set configuration clr strict security to 0 !
( it is 1 by default !! )
exec sp_configure 'clr strict security', 0;
reconfigure;
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply