Watch Brighton win the battle bot competition!

December 16th, 2016

I am so very proud of him!

Pointless, Work

Synth Radio Russia, INSOC

April 1st, 2016

Synth Radio Russia!  I enjoy almost every track they pump out.
Go here and get a Camouflage tribute album from them:

Information society NEW ALBUM!  Fun covers.  Listen to the live one: Then, select the “10:30” link under “Information Society”.  Starts at about 2:15 in.


Tea options change in Tucson

November 9th, 2015

The Chantilly Tea room closed!  Sad day. They were the best.

Could try Seven Cups traditional Chinese tea service.

Kalina’s restaurant does Russian Tea on Saturdays. (closed)

The Tudor Rose is British Tea all the way. Closed down.

Missed a boba shop: Chatime (visited, sad really)


Toying with ideas

September 17th, 2015

hokusai tiresclick for larger.


Synthpop’s Alive.

January 11th, 2015

Somehow I missed this one, love the track.

Synthpop Music

This guy knows from parenting.

January 11th, 2015

SQL cannot take the action auto_fix due to duplicate SID

November 3rd, 2014

I ran into an unusual Error in SQL “Msg 15331, Level 11, State 1″ “cannot take the action auto_fix due to duplicate SID”. I had restored a database from another server and decided to update the database owner name to one that had a mismatched SID.

Here is how to find it:

SELECT, u.sid,, sp.sid
FROM sys.sysusers u
LEFT JOIN sys.server_principals sp
ON =
WHERE u.sid != sp.sid

So at first I tried to fix it myself by updating that SID and found:
Msg 259, Level 16, State 1, Line 1
Ad hoc updates to system catalogs are not allowed.

The SID for the owner would not repair until I changed the owner of the database to “sa” or myself. (go to db properties, select files, change owner value.) Once this was updated the autofix statement will repair the user: EXEC sp_change_users_login ‘Auto_Fix’, ‘username’

At that point I could set the db owner back to the desired name.


This day be pirate!

August 8th, 2014



Pirate weekend starts today in Bisbee. I had to upgrade the van to a landship. (While I wait for the funds to build a real landship.) Does adding a mast and some paint count? The text in the back says “Seek Ye First.” I know the font is small but I had a stencil made and it’s not ready in time. The graphic is how I reconcile Godliness with Pirate theme. Go straight to the cross!


It’s a Keyboard Keyboard.

July 30th, 2014

Where else should you put your keys than a keyboard keyboard? Of course it should light up, connect to USB and be Starcraft 2 branded. I put an outlet in the wall with USB connectors as well as standard plugs. The keys clip onto stainless steel drawer handles. Only one of the electrical paths was damaged by drilling the holes for bolts. I tested it each time I drilled one out. The lower left corner of the key backlights no longer have an LED. Everything else works! Now the family fights: Is it a keyboard keyboard©, or is it a key keyboard©?

A keyboard keyboard


Finding an SQL Job that shows an error in logs

May 27th, 2014

I was perusing the MSSQL Agent logs and came across a job that kept printing errors every 20 seconds. It has an id with a long number. How can you find what job this is by name?
Here is what the error looks like: “Request to run job 0x17DF82795C5C224CBF7DC88E8E3C4E12 (from Alert 2618) refused because the job is not currently enabled.”
To find the job I must assume that this mess of numbers is a GUID, and therefore it relates to a name?
use msdb
select * from dbo.sysjobs

I find a job_id that relates to the problem above by just grabbing the last part of the guid without dashes. Here is the real job_id:

I can also look for when this job might fire again:
select top 100 * from sysjobschedules where job_id like ‘%C88E8E3C4E12%’

The job is disabled and there are no schedules for it. So why is it erroring every 20 seconds? It is an alert:

select * from dbo.sysalerts where id = 2618

Someone created a check for blocking transaction job, and fired it upon Blocking Alert. Then they found out that they didn’t want the thousands of emails so they disabled the job. The alert is enabled, calling a disabled job. Error logs get filled now instead of inboxes. The solution was to disable the alert.

Computers, Work