It doesn't sound like your code supports unit testing. You shouldn't really need to test private methods directly, you test the methods that call them, and you shouldn't be calling any code in a unit test that runs a stored procedure. Unit tests are for testing your code's logic and flow, they shouldn't access any external resources. You need to mock any code that accesses resources, so have a class that just handles your SP access and mock it during unit tests. As well as not needing to access any databases it also lets you simulate all possible results from calling those SPs such as the database being down, the data already existing and so on.