SQLServer 2005 trigger debugging

They've removed the T-SQL debugger in SQLServer 2005. Luckily I have 1 day left of my Visual Studio 2005 trial.

The way to debug a trigger is to create a stored procedure that exercises the trigger (mine just did an update on the table), set a breakpoint in the trigger where you want, and then step into the *stored procedure* by right clicking on it. Bobs your uncle, VS grinds away and you get to your breakpoint (eventually).

Fedora setup

Ok, on to setting up FC6. I've installed the base FC6 and picked out the development and MySQL packages. On configuration, I disabled the firewall and SELinux during testing. We'll decide what do about those on deployment.

Next I instaled the VMware tools (thanks for the mouse pointer help here http://www.thoughtpolice.co.uk/vmware/howto/fedora-core-6-vmware-tools-install.html and the vmxnet diver help here http://www.vmware.com/community/thread.jspa?messageID=556834).

To make sure the two are synchronised I'm planning to setup NTP on the second node pointing to the first one (I found instructions here http://wiki.novell.com/index.php/SUSE_Linux_Enterprise_Server) - but I want to get MySQL configured and running on the master first before I clone the system.

Testing MySQL Clustering

At work we're setting up a pool of LAMP servers and they will need some persistent storage. We're using MySQL in house for our other relational needs so I'm having a go at getting a 2-node high-availability/shared nothing/load balanced database cluster working.

I can't access the actual hardware yet, so I'm playing in a couple of virtual machines. The first step is to get them installed and stick MySQL on there. The LAMP servers are all using FC6 (for better or worse - maybe CentOS would have been better) so I'll use that. First step, getting the first node working so I can clone it and try out replication.