Posts Categorized: Technical Blog
Those of you who have seen me present about GoldenGate will know that I recommend using a heartbeat table to monitor GoldenGate lag. The heartbeat table is a great way to monitor GoldenGate replication because it can follow a single SQL insert through each major GoldenGate replication process, and report the replication lag attributable to each.
As we all are aware SQL Server 2012 virtual launch has arrived. Earlier I discussed what’s new in SQL Server 2012 setup, MS has released the SQL Server 2012 training kit and made it available for us to download.
I’ve been playing with SQL Server 2012, codenamed “Denali,” since the CTP days and am very happy with some of the features that they have introduced to address high availability and disaster recovery requirements. For me, these are more than enough reasons to consider upgrading to SQL Server 2012.
In recent past we had a situation where in, we were required to move MSDB, Model and Master databases to a new location, the reason being a faulty drive. While moving the system databases to the new location we needed to be extra cautious. Let’s see the process step-by-step.
The process of upgrading SQL Server is usually time consuming, costs money and requires availability of human resources. If you don’t see the immediate need…Why bother?! Before deciding on upgrading, you should be aware of the new features and make sure you will really benefit by the upgrade. From our experience at Pythian with dozens of clients and hundreds of environments, what could be worth upgrading to SQL Server 2012?
Here are some of the top features related to the database engine (Part I):
Microsoft has released one more free eBook, this time it is on SQL Server 2012. This is the second draft of this book. SQL Server MVP Ross Mistry and Stacia Misner has covered Administration and BI part, there are 10 chapters in total divided in two parts, they are:
The extension system is good for anything written in C. So, in theory, I could — probably shouldn’t — but I could write a thin wrapper for a Perl interpreter. At that point, I had no choice. The idea was so preposterous, I had to try it.
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.