tsqlt

I have a new project that needs SQL Server unit test, and CI/CD with VSTS. Below is the features that are required SQL server unit test against stored procedure, initial target tables setup for each test and clean up Unit test in sql CI/CD with VSTS and Git Easy setup and easy to use I looked into SSDT 2017, which seems good. But it seems it lacks a feature where common setup script can be shared easily between each test in Pre-Test step. It might lack other features that should be available for daily usage. But I might be wrong. Which tool fits better for general sql server unit testing in

New to the tSQLt world (great tool set) and encountered a minor issue with a stored procedure I am setting up a test for. If I for some reason have a stored procedure which connects to mutiple databases or even multiple SQL servers (Linked Servers). Is it possible to do unit tests with tSQLt in such a scenario? I commented already, but I would like to add some more. So as I said already, that you can do anything that fits into the single transaction. But for your case I would suggest to create synonyms for every cross database/instance object and then use synonyms everywhere. I've created

i have a table like this tab1 create table tab1(ID int identity(1,1), Type varchar(10),IsValued bit) tab1: ID Type IsValued ---------------- 1 S 1 2 R 0 3 R 0 4 S 1 5 S 1 6 R 0 7 S 1 instead of inserting value into IsValued column i want to create one constraint(NOT TRIGGER) when Type ='S' ,IsValued should be inserted as 1 and when Type ='R' ,IsValued should be inserted as 0 like : IsValued = case when Type ='S' then 1 when Type ='R' then 0 end How can i achieve this.. twoleggedhorse You want a computed column. For example: CREATE TABLE tab1 ( ID INT IDENTITY(1,1) ,[Type] VARCHAR(10) ,IsValued

I recently was calling a procedure that contained a rasierror in the code. The raiserror was in a try catch block. Also a BEGIN TRAN was in the same try catch block after the raiserror. The Catch block is designed to ROLLBACK the transaction if the error occurred in the transaction. The way it does this is to check the @@TRANCOUNT if it is greater that 0 I know that it had started a transaction and needs to ROLLBACK. When testing with tSQLt the @@TRANCOUNT is always >0 so if it ever hits the CATCH Block the ROLLBACK is executed and tSQLt fails (because tSQLt is running in a transaction). When

I really like tsqlt to test procs and functions, but really would like to be able to also execute SSIS packages and take advantage of FakeTable and AssertEquals to determine if it was the SSIS package did what it was supposed to. Has anyone explored this path, is it possible to call dtexec from with the transaction that tsqlt wraps your test in? I believe I can answer your question Andrey, although this is a little late in coming. But I believe that it will benefit others. We are using RedGate SQLTest(tSQLt) to do data quality testing as a part of our integration testing. For example to test