Skip to main content


Showing posts from April, 2006

sms: reporting is single-threaded

a fellow mvp, brian rogers , started drilling me about sms reporting the other day (probably because all the smart people are hanging out in san diego drinking margaritas and eating fish tacos in Old Town pretending like they're at a conference). the questions started around how to best setup sms reporting for load. hashing back and forth the basics, it was assumed that sms reporting probably taxed sql server the most ... since the only bottleneck was page faults. brian alluded to a possible problem where the sms reporting function executes one request at a time. we started looking into this and discovered this to be the case. reviewing logs, he discovered that this was indeed the case. i did the same test myself and found that to be happening. the reporting point is, in fact, single-threaded. even though the database can handle multiple queries, the reporting point only sends one at a time. if the browser is closed after a query is sent, the query request does not end.

mom: new mom resource goes live...

if you haven't seen it yet, go check out . pete and justin, who are becoming legendary mom experts, are doing an excellent job of consolidating content directly related to the successful administration of mom. all of their previous blog material and how-to guides appear to be on that site. their downloads section contains some scripting answers to problems you may be trying to solve today. right now... this very moment... :) they've also removed the frustration of finding some of the not-so-easy to locate materials. just wanted to raise some awareness to a rapidly growing resource that i know i'll be frequenting.

mom: update to upgrading sql 2005

we upgraded our mom warehouse infrastructure to utilize sql 2005 before the official article was released using the three separate articles i had posted earlier. so far, successful. all dts packages execute post-upgrade! big benefit for me? i can use vs2005 to write the reports now. time to move on to upgrading the production databases. anyway... since that time, microsoft has released an official knowledgebase article on the issues/hotfixes regarding upgrading to sql 2005.

mom: execute a command or batch file...

i was fiddling around with using this to issue a stop/start sequence on a service under a given condition. the stop/start stuff was pretty easy, but the response execution was a little baffling. i found that mysterious "use windows command interpreter (not recommended)" dialog is required (i didn't put the parenthesis around not recommended . that was microsoft's doing). anyway, that's the first part. i'll get to that in a minute. so how do you execute commands in a sequence? the answer is, i don't know. i don't know if it's possible. i don't know if it happens if you order it right. if you notice, the dialog doesn't supply an "up/down" button to move the commands around to sequence them. you'd have to create them in order. even then, does it execute this way? dunno. the easy way around this is to use a double ampersand. so in order to stop and start the dhcp service, for example, you'd issue this command: net s

mom: all http errors rules

pete has added some great stuff as a follow on to my post regarding http error rules. once again, he illustrates with a magnifying glass on getting to the core of where the problems lie. check out excellent blog entry .

ds: a few of my favorite repadmin commands...

if you're dirt poor and can't afford a monitoring product to watch over replication status in your environment, you can still get "at-a-glance" capability using repadmin. these are some of the commands i use to see what's going on in my environment. mom, you say? well... errr... yes... i... errr. the story is, we have some domain controllers that do not have the mom agent loaded on them. these are domain controllers in an entirely different domain. however, we still replicate with them as a part of our forest so i have to stay vigilant to their health. (in other words, no mom agents on those...) repadmin /replsum * /bysrc /bydest /sort:delta displays the source and destination domain controllers, along with their delta. repadmin /showrepl /csv displays the source and destination pairs in comma-delimited format which is much easier to read than standard output repadmin /showutvdec /latency displays the domain controller, usn value, and sorted by time

my first korean visitor! (about damn time)

i've been anxiously viewing my clustrmap (it's the picture under the google ads) to finally show me that i had a reader visit from my homeland! i've been tracking it since february... and it took until now to finally see that i have had one visitor. (korea is the bunny shaped country attached at the southeast corner of china and west of the islands of japan.) so what does this have to do with technology? hmmm... nothing, actually. i was just so excited about it, i had to post it. :)

misc: enabling terminal services remotely...

this may be old stuff, but i've been too busy lately to post anything. i felt obligated to post something, anything. :) anyway, with wmic you can enable terminal services remotely in case you had forgotten to do it during a build. from a command prompt, issue this command: wmic /node:"servername" /user:"domain\username" rdtoggle where servername = "servername" call setallowtsconnections 1 from inside wmic, issue this command: /node:"servername" /user:"domain\username" rdtoggle where servername = "servername" call setallowtsconnections 1 /node: indicates the remote server name /user: indicates who to grant access to setallowtsconnections: indicates to enable terminal services. 1 enables it. 0 disables it.

john hann is back...

sort of. he's blogging again, which is good. he's a valuable mom resource and a good friend. apparently, very passionate about technology, mom in particular. he alluded in a previous post that he reached high levels of frustration trying to get product improvements to occur. click here to read an email he sent to steve ballmer last year.

mom: application log provider (snafu) throws error 25222

david (henson) and i were kicking this around a bit, if you happened to have been watching on the msmom mailing list only to come to a ridiculous fix. anyway, this may come to bite you in the ass at some point or cause unnecessary pain so i had to blog it (not to mention i may forget about it as i slip quietly into senility). i think david may have lost some hair from this one. i encouraged him to call pss. when you're setting up an application log provider, you have to specify the below properties. provider name: provider log type: generic single-line log file directory: x:\test\logs format: generic file pattern: crud.log none of it is out of the ordinary or difficult to interpret. however, you want to pay careful attention to the way you terminate your directory path. if the directory ends with a trailing backslack, mom may generate event 25222. in the above example, a bad directory path would be " x:\test\logs\ ". since it's not documented anywhere, i&

mom: monitoring exc script processes

i recently deployed an exc connector (excellent company, by the way, and very pleasant to work with) to help with trap forwarding with the intent of doing two-resolution state at some point in the future. one of the problems i noticed with the connector was that the script processes running on the exc connector terminated without any warning that i could detect (and subsequently alert on). my goal in this case was to get a little more familiar with wmi notification queries. after some fiddling around, i finally got it to work. alright, so how to do this? here goes: create a wmi event provider. name: exc_script_processes (i named mine this because i'm just clever like that. name yours whatever you want.) namespace: root\cimv2 query: select * from __instancedeletionevent within 89 where targetinstance isa 'win32_process' and targetinstance.commandline like '%cscript%mom%' property list: create an event rule. provider name: exc_script_processes (or the equall