As engineers, developers, administrators, and other IT related disciplines, we govern our work by the scientific method. Or do we? What happens when we don’t? What are the implications if this happened a lot?
Read on the see the trouble that big data brings when trying to adhere to actual reproducible science…
The topic for this months T-SQL Tuesday #113 hosted by Todd Kleinhans (Blog / Twitter) is about “what do YOU use a database for”. We work all day, night, and weekend sometimes on our database craft. Todd asks:
So what do you use databases for in your personal life that you are willing to share?
Now that the basics of MSDTC have been covered in Part 1 we can move on to troubleshooting more specific issues. Here I cover other tricks that can ruin your day. There was a period of time where it felt like all I did was diagnose and fix MSDTC issues. This is the outcome of that frustration – a guide that you may find helpful and prevent the stress I experienced. So without further ado…
If you haven’t worked with MSDTC before you might mistake it for a simple straight forward service which is easy to setup, configure, and troubleshoot. I too once thought that until I stumbled into the thick forest of MSDTC with those promises and didn’t return for years all grizzly and worn (ok it wasn’t that bad).
What comes next is my contribution to those who follow into the dark denizens of MSDTC hoping to fix things so they can go home.