Posts Categorized: Technical Blog
Good morning and happy Friday to all. Happy Thanksgiving to all of our friends, family, acquaintances, and well-wishers in the US. Enjoy the turkey and the football. As always, there’s not shortage of news stories, though the week seemed a bit slow because of the holiday. Here are some things we thought were interesting this week.
One of our clients has a public web page and they needed to ensure that it is always up and accessible. Pythian already has a monitoring stack that includes website and pages monitoring. I wondered if this could be done from SQL Server using built-in Windows modules to access external web resources. There are various the methods we can use.
I had an opportunity over the past few days to attempt to use Microsoft’s Server Management Objects (SMO) with Perl to manage a SQL Server 2005 DB. To make a long story into a short post, I blundered into the Win32::CLR module on CPAN, a little gem from Toshiyuki Yamato. Here is all you need to get started.
Is it Friday already? Where has the week gone? Whatever, we’ve got lots of good news tidbits for you this week, including several follow-ups to previous stories. Enough jaw-jacking, let’s get to the news.
This is the 170th edition of Log Buffer, the weekly review of database blogs. Welcome. Let’s kick off this week with a double-helping of . . .
I recently nominated my colleague and good friend Christo Kutrovsky for the Oracle ACE program. Today, I’m excited to share that he has been accepted and is now part of the community of 200+ Oracle ACEs and Oracle ACE Directors.
Like good day and welcome to issue 6 eh. This is another light one as it’s been another busy week. I have not had any time of my own to crawl through the news, but luckily my cohort Bill has flagged some good stuff for this week. Let’s get to it.
Here is a must-read whitepaper describing SQL Server Scheduling and how to interpret and diagnose Errors 17883, 17884, 17887, and 17888; please look here How To Diagnose and Correct Errors 17883, 17884, 17887, and 17888. We had a client having same issue. The client runs a busy online business with thousands of connected users; databases sometimes include more than half a million tables. We had a healthy counters and server didn’t seem to suffer from memory or I/O bottlenecks. We did suspect, that it is something to do with SQL Server internals, as we also received fatal exceptions pertaining to SPIDs <50 (system processes). If you face similar issues, you should install the latest service pack and cumulative update, and check if you have any resource bottlenecks. You can try trace T2330 as well, and if you still get errors or dumps, then you had better open a case with Microsoft Support to analyze the dumps and provide a resolution.
This is a little tip for those who develop or debug SSIS packages. In SQL Server Integration services, User namespace variables are assigned values that are used across the package. When developing, testing or debugging packages, we assign multiple values to those variables to test different scenarios. This is done using the variables window. However, SSIS Script tasks can allow us to key in values for selected variables in run time. This looks more fun and keeps us from taking chances when we forget assigning variables’ values.
For the past two months, I have been running tests on TokuDB in my free time. TokuDB is a storage engine put out by Tokutek. TokuDB uses fractal tree indexes instead of B-tree indexes to improve performance, which is dramatically noticeable when dealing with large tables (over 100 million rows). For those that like the information “above the fold”, here is a table with results from a test comparing InnoDB and TokuDB. All the steps are explained in the post below, if you want more details.