I’m a sorry and sore case again. My back gave out a few minutes into the first half of a game of Basketball on Saturday. Despite initial cries of “foul” from my teammates I quickly realised that the only reason I’d fallen to the floor in pain was an all too familiar but dreaded feeling in my lower back. One I’d hoped I’d never have to endure again. It’s so annoying as I’d been trying really hard to keep up the stretching and strengthening exercises given to me since the last incident. I realise this also doesn’t just impact me - it messed up the rest of the weekend for my whole family, which is extremely frustrating. Maybe it’s an indicator that I need to think about other forms of exercise, and my body isn’t as young and flexible as it once might have been? Or maybe the timing is appropriate for me to make the transition from player to supportive parent. We’ll see.
Using the Sync Framework (aka Sync Services for ADO.NET) can feel a bit like a black box. You implement some classes, override some methods, call Synchronize() and it all just magically happens..
Except when it doesn’t. Sometime strange things can happen, and it would be nice to know a bit more about what Sync is doing under the hood. Unfortunately this is one product that Microsoft haven’t release source code for, so you can’t step into it with your debugger.
That was where I thought the story ended until I stumbled upon this topic on MSDN – How to trace the Synchronization Process.
So add some stuff to your app.config file and you should get a little more information about what is really going on.
I see that Adelaide’s own SQL Server-specialist consulting company – LobsterPot Solutions – are now a Microsoft Certified Partner (Data Management Solutions, Business Intelligence).
Well done Rob!