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
With new year many new projects, new technologies, new frameworks and new ideas are springing up at the speed of light and bloggers in the database arena are keeping up with this pace and this Log Buffer Edition is also living up to that pace and covers some of those posts in Log Buffer #257.
In this post, I will share with you my experience installing OVMM 3.0.3 under OVM 3.0.3 Dom0 host, including, a short and sweet action plan to get it up and running ASAP, a detailed explanation with error messages and solutions, and clean run output
Searching for the blogging inspiration? On the look-out for that Eureka moment for your next blockbuster blog post? Finding the exact ingredients for your dream rambling? Well in the Log Buffer Edition, there are some awe-inspiring posts in this Log Buffer #256. Get Inspired, keep blogging.
The end is nigh for Adobe Flash at My Oracle Support. The first step will happen during this weekend’s planned maintenance of My Oracle support, when all of MOS will be down for 5 hours starting at midnight eastern, Saturday January 28. Once it comes back up, the unadvertised non-Flash supporthtml.oracle.com will come up as a quasi-user acceptance test of the new application, while the flash-based support.oracle.com stays as-is.
This is going to be a short one, but potentially useful for anybody writing a Dancer template module, or just plain curious about Dancer’s guts. So here goes.
A frequent inquiry concerning databases’ security is to retrieve the database role(s) associated with each user for auditing or troubleshooting purposes. Each database user (principal) can be retrieved from sys.database_principals and the associated database roles can be retrieved from sys.database_role_members The following code runs against ALL the databases using SP_MSForeachdb and all roles for one principal is concatenated in one row