Skip to main content

Sinus Relief: My Approach

Quick off-topic post about allergy relief...

I've been plagued by allergies since childhood: trees, cats, dogs, ragweed, you name it. I've been on every drug on the list. I can remember being sick every Easter and every birthday (end of September) for...well ever. A few years ago, I consulted an allergist who ran me through a series of tests, determined my exact allergies, and gave me some solid guidance.

Following my allergist's advice, I've not been 100% allergy/cold-free but I've noticed a significant improvement. His recommendations:
  1. Exam from an Ear, Nose, and Throat (ENT) doctor. I have a slightly deviated septum and some nasal dollops but otherwise, nothing horrid. He checked my jaw, my hearing...all kinds of stuff. Fortunately, nothing major is/was wrong. He did recommend I wear a mouth guard at night to prevent teeth grinding (which may cause eustachian tube clogging).
  2. Take a daily Loratadine (generic Claritin).
  3. Daily Fluticasone steroid nasal spray (generic Flonase).
  4. NeilMed Sinus Rinse in the morning and before bed.
  5. (I think I came up with this one but...) Wear a particulate mask (just one of the cheap ones) when mowing the lawn. I'm sure the neighbors think I look like a weirdo but [without scientific evidence] it helps keep the dust and particles from getting into my sinuses...and causing infections.
The NeilMed Sinus Rinse is the big one for me. I'd done the other drugs for a while with limited success. The sinus rinse is similar to a neti pot...if you've heard of that. Essentially, it's a saline rinse for your sinuses. It's awkward at first but the benefits are tremendous--significantly fewer sinus infections!

I hope you find relief from your allergies. Looks like this spring will be rough.

Comments

Anonymous said…
The doc gave my wife a NeilMed kit after she had her deviated septum fixed. She still uses it on occaision and says it works great!

Popular posts from this blog

Get Your Team Foundation Server Hate On!

[Google ranking skyrockets... ;-)]

I'm a big fan of TFS/VSTS. However, there are a good pocket of folks who take issue with the way TFS handles or implements a certain feature. Well this is your chance to vent!

I'm planning a presentation around the "Top 10 TFS/VSTS Hates and How to Alleviate Them"...or something along those lines. But I need your help. Post a comment below detailing your dislike. If it's legitimate, I'll highlight it in the presentation and [hopefully] provide an alternative, resolution, or work-around.

Thanks in advance!

Update 7/19/2008: Version Control and Microsoft

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario...
I'm workin…

Shrinking WSS (Sharepoint) SQL Server Log Files

Yesterday, while migrating a source repository from StarTeam to TFS, I received the following error:
"TF30042: The database is full. Contact your Team Foundation Server administrator."Excuse you? Sure enough, my 100+ GB drive was full on the server. But I'd only migrated around 1000 items. Surely SQL wasn't consuming 100MB per file.

Turns out (yes, there was a lot of crud on the drive but...) the majority of the space, almost 40GB was being consumed by the Windows Sharepoint Services WSS Content data and log SQL Server files. Huh? I still need to investigate and understand why this portal, which is 100% unused, grew so large. Regardless, here's what I did to resolve:

Since this is not yet a production database, I flipped the SQL recovery option from Full to Simple for WSS Content and several other databases. Detail here and here.
Executed the maintenance plan for all the databases to get backups and clear out some of these files. That didn't help much. The Auto_…