Skip to main content

Bonehead of the Week: PB Furniture

My wife kicked into an organizing spree last week purchasing a companion shelving unit to house kid stuff matching one we already have. I took an hour or so putting this second unit together Saturday. I'm one screw away from finishing and...crap, this one isn't the same color. You've got to be kidding. Explicative. Explicative. Explicative.

Yep, the new one is "espresso" with the old being "honey". C'mon, get real people. I'm completely pissed at myself for not checking and/or noticing sooner. Taking this guy apart isn't tough but putting it back into the need-to-be-a-packaging-engineer packaging feels daunting. Well, I managed to get it close and re-pack it with some semblance...and off to Easton I go.

My wife called ahead and Pottery Barn Kids told us to just have our receipt and pull into a little, nearby driveway. Ok, fine. Well, they've changed the traffic patterns at Easton and it's a PITA to get around; but I finally plunk myself in the right spot.

I hop out of the T-Blazer and blam, Mr. PBK is wheeling my replacement shelves out. Is this guy psychic? We exchange boxes and he inquires, "You just called a few minutes ago, right?" [Nope...but I'm hijacking these "honey" shelves nonetheless, pal.] About then, a mini-van pulls up. Yep, you guessed it: two people pulled into this loading dock, both at Easton, both at exactly the same time--both retrieving the exact same thing. Doooo-dooo-dooo-dooo. Creepy, right?

Needless to say, I checked for the "honey" color prior to departing. Yep. "honey". Grumble. Grumble. Metrosexual. Grumble. Well now I'm an expert. I set up my "honey" shelves in about 25 minutes.

All is well (and organized) now! Unfortunately, due to my push to get this task checked off my list, a 45 minute task became a 4 hour task. Super.

Comments

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_…