Posts Categorized: Technical Blog
What if I found a way to get the blog entries, and plop them on mailboxes on my mail server? That would take care of ubiquitous access. And since I would have control on the software, I could probably manage to filter out dupes. I sat down and began to hack on this. The result is mailfeed (clever project name pending). I’m still not sure if it’s a good idea, but at least its execution showcase how much niftiness can be crammed within 144 lines of code. But let me show you…
My first stab at SQLiteTAP is on GitHub. I’m writing it as a SQLite extension, so I had to brush up very rusty C skills. But after a few hours pouring over the documentation, and poking here and there, I have a working implementation of ‘plan’ and ‘ok’. Nothing earth-shattering, I’ll concede, but a nice start nonetheless.
This blog entry is light on technical content and heavy on “about me” stuff. So unless you’re interested in the hot spots where to dispatch ninja assassins to take me down this year (or perhaps just where we might cross paths and shake hands), feel free to close this tab.
I recently worked on a case where Service Pack 2 for SQL 2008 clustered instance failed with this error (Summary.txt). The resolution (or workaround I would say) is simple, use a local disk to launch SP2 setup, here’s a step by step how to.
I’m traveling quite a bit in the next few weeks, here’s where you can find me…
As previously reported, last week-end’s activities could be summarized as me going to town on a yak herd with a lawnmower. And although the rest of Saturday and this morning haven’t been as fast and furious as Saturday morning, there’s a few more things to report:
So HP Cloud is finally yielding for some beta rain since their announcement late September. It started late September when I signed up for private beta testing. Two weeks ago, I got invited to join the beta and start testing the platform, here’s whats offered.
I’ve revived Perl::Achievements. I thought that would keep the wolves at bay, but noooo… Not a hour after the announcement was sent, I got a new feature request. I really should not but… okay, I wanted to do it anyway and if somebody is actually asking for it, why the heck not? Plus, it’ll give me the opportunity to see if my Template::Caribou is up to snuff. A few hours later, I have a bug report for MooseX::App::Cmd and (after some touch-ups) released the first version of Template::Caribou on CPAN.
Perl::Achievements is now on CPAN. The goal of the app is the same as presented in the original blog entry. I’ve, however, fleshed out a little bit more the documentation, tidied up the code a wee bit (well, it’s still a mess, but it’s using a lot of cool stuff, so it’s a shiny mess), and changed the innards just a tad. Wanna use it?
Today we have an alert from one of the client server about blocking,Yes, I’ve found the culprit SPID that is occupying more resources, using DBCC INPUTBUFFER(SPID). so, instead of seeing what exactly this SPID is doing I have received SP_EXECUTESQL, surprised!!! No, it’s bound to happen when SPID is running dynamic TSQL (using SP_EXECUTESQL) and/or cursor. But, yes, at the same time I would like to know what it is running behind the scene. There are two options that came to my mind