G’day, I’m Ken – originally from Australia but now living in New Delhi, India after spending 7 years living in London.
I write software and dabble in business intelligence for a living and have an interest in building real-time event processing systems.
See my code on GitHub
Follow me on Twitter @kzhen
Connect with me on LinkedIn
Disorderly Development 
[…] Finally I have changed the message box at the beginning to a Debuger.Launch which works much better – thanks to Ken (blog) […]
Hi Ken
Is any way to download your simple application in C#,that generate DDL from sales force for SQL server
Thank you
Albert
Hi Albert, I’ve pushed the code up to my GitHub account – https://github.com/kzhen/SSIS-SalesForce-Connector/ – I haven’t looked at this code since 2013 so can’t make any guarantees that it will still work. Let me know if you have any problems and I’ll do what I can to help resolve them.
You will need to make sure you have SQL Server 2012 Client Tools (I think that’s what it’s called) installed, as well as the Pragmatic Works TaskFactory product installed (http://pragmaticworks.com/Products/Task-Factory). You’ll then need to fix the broken references in the project before you build and run it.
Ken
Hello, Ross!
I’ve read your article at https://kzhendev.wordpress.com/2014/01/08/setting-up-ssdt-database-projects-and-tsqlt/ and found it very interesting. I newby in tSQLt (start reading about it in this weekend). Can you explain some points what I misunderstood?
You create two different database’s project: for business t-sql code itself and for tests respectivly. And then deploing them in two different databases too? I can’t understand how tests will be perfomed on objects in different DBs.
In documentation at tsqlt.org says what tsqlt must be in same DB as the code.
Thank you.