edgoad

Search This Blog

Never Give Up

on July 03, 2008

Get link
Facebook
X
Pinterest
Email
Other Apps

Get link
Facebook
X
Pinterest
Email
Other Apps

Comments

Using SCOM to monitor SQL Error Logs

Our SQL DBA reported that occasionally he will see errors in the SQL Error Logs similar to: SQL Server has encountered 45 occurrence(s) of IO requests taking longer than 15 seconds to complete on file [T:MSSQLDatatempdev6_Data.NDF] in database [tempdb] (2). The OS file handle is 0x000005B4. The offset of the latest long IO is: 0x0000000c7b2000 Monitoring for this alert at first sounded simple, but as I dug into it I realized it could be much more difficult than I expected. First off, this error is reported in the SQL Error Logs and only in the SQL Error Logs, so we cant simply use the NT Event log to alert us. Secondly, depending on how you install SQL, these error logs could be anywhere on the system. And lastly, this is needed to be monitored on SQL 2000 and SQL 2005 systems, so xp_ReadErrorLog won’t work for us. So the breakdown seems fairly simple: find out where the logs are, use the text log monitor, and search for the string. 1. Find out where the SQL Error logs are store...

System Configuration and Management -- Build a simple RPM that packages a single file

This is an interesting objective – something that I have never had to do before. After looking around at various tutorials and such, the wording of the objective is even more confusing – RPM packages are designed to install programs, not just copy a file. For example, there is a great how-to for creating RPM packages at http://fedoraproject.org/wiki/PackageMaintainers/CreatingPackageHowTo . A few days looking and I actually came upon a need to create a package – I want to have a silent install of Linux in our datacenter that copies custom scripts to the systems. The best way to handle this would of course be to build an RPM package that included just the one script. A little Googling and bingo! http://lincgeek.org/blog/?p=303 has just the information I needed on how to package a single file and direct it to install into a specific location. STEP 1 : Install the necessary packages Each site you go to says something different, but it appears that the rpmdevtools contain...

Changing the PrintProcessor on a Windows 2000 Print Server

One of our customers has a W2k print server with several hundred (nearly 600) printers. Half are used for a program named CreateForm and therefore have a printprocessor named CfPrint, but the rest have a mixture of WinPrint and some other HP processors. They recently began having printer problems that we couldn’t diagnose, but the idea came up to limit the number of variables in play: drivers, configurations, processors, etc… So its up to me to make nearly 300 print queues use WinPrint as their processor. Under W2k3 this would be an easy item, simply write a WMI script to query the printers and then set the processor to WinPrint. W2k however sets these properties as read-only, so back to the drawing board. It looks possible to set the processor using printui.dll, but it requires a little knowledge to make it work. First off, it doesn’t seem to set the processor when run locally, instead I had to set it remotely from a W2k3 system. Secondly, it has a complex command line that...

Powered by Blogger

Never Give Up

Comments

Post a Comment