I inherited the SCOM project when one of our Admin people left the company. This person had done a ton of work setting things up but ran into some problems. One of the problems was identified as databases missing from particular instances. I investigated further and found that the database list was "distinct" across instances. Meaning, if two instances shared the same database name, only one of the databases was listed. After getting an email from PSS, I did more investigation today. Now it's getting weirder. Some servers aren't showing up in Explorer, some aren't in both Explorer and the console. Not good. I've documented it all and shipped it off to the PSS guys to see what they think.
I was asked if I would look at a new tool from a company I hadn't heard of. It's SQL Inspect from Yohz Software. Nominally this isÂ a SQL query editor. However, strictly as a query editor, especially when compared to what's available in SQL 2008 or what tools like Red Gate's SQLPrompt or SQLRefactor can do for you, it's not so hot. Luckily, that's not where its strengths lie. Instead, it's all about performance tuning your queries and it does this very well indeed. It takes a query and returns a tree structured execution plan, looking a bit like the old text plans, but much more sophisticated with roll-ups, etc. It shows you all the details of the operations, just like an execution plan, but immediately accessible on the screen,…
I'm working through implementing SCOM, specifically the SQL Server Management Packs. I've been tweaking and tuning and for the most part I'm really impressed with how MS configured the defaults. Until today. Since I've hit all the really big and important monitors & rules (at least the ones that have caused problems) I'm starting to drill down a bit. I just hit the Duration monitor for SQL Agent Jobs. The run time for a warning state is 1 minute and an error state in 2 minutes. OK. So any backup on a database over about 2gb in size is going to go into a warning state? I don't think so. What the heck were these guys thinking of?
Last week I presented at the Southern New England SQL Server User Group (SNESSUG) where I'm the Program Director. I presented from the book, Dissecting Execution Plans, that is supposed to be published any day now. I kept it basic and it flowed very well. The audience seemed receptive and there were a few questions. Mostly around figuring out what to do when you saw certain problems within the execution plans. Since that was the goal of the presentation, I was ready for most of the questions. I got stumped once on a Constant Scan operation. I finally looked it up this morning and feel silly. Here's the query: INSERT INTO [AdventureWorks].[Person].[Address] Â Â Â Â ([AddressLine1] Â Â Â Â ,[AddressLine2] Â Â Â Â ,[City] Â Â Â Â ,[StateProvinceId] Â Â Â Â ,[PostalCode] Â Â Â Â ,[rowguid] Â Â Â Â ,[ModifiedDate] VALUES ('1313 Mockingbird Lane'…
Steve Jones, in his daily email from SQL Server Central,Â supplied a link to a terrific article in the MSDN magazine. Apply Test-Driven Development to your Database Projects. It was written by Jamie Laflen who is a Tech Lead on the DBPro team.Â I've written a couple of articles on database unit testing, but none of them touch this. It's the new gold standard for introducing the topic to beginners (and lending a helping hand to experienced users). It's worth a read, or even two. I'm going to go back and review it a couple of times with Visual Studio open and a project running. No word yet on new virtuals. I'm going to work on another set of tests that I have to run. More on that later.
My fault, my fault, my most grevious fault... I installed the November CTP to my virtual machine without making a backup of the virtual first. Now I can't get the November CTP to uninstall and the February CTP won't install on top of it. ARRRGGGGH! Anyway, I'll be getting back to 2008 tomorrow, hopefully, after the admin guys get me a new virtual.
I'm going to try, again, to blog about SQL Server. We'll see how it goes.