SELECT TOP 1000 * FROM "foo"."dbo"."bar";
That means that as soon as you have a few MB worth of data the tab takes ages to load and HeidiSQL gets unresponsive afterwards. (Right now it was using as much memory as Firefox and I only have one row with a 40 MB picture. When I finally managed to focus on another table memory usage dropped.)