Random Thunks

I recently had to redeploy a DB on another server with a whole new master key. This meant that I had to destroy and recreate all the existing Certificates and Keys that I’d created based off the previous master key.

The biggest problem for me was locating all the pesky procedures that I’d signed previously that would need to be resigned with a new certificate; however locating this took a bit of time. Eventually I was able to come up with the following query:

Select    Schema_Name(O.schema_id) + '.' + Object_Name(Cp.major_id) As 'Module'
         ,cp.crypt_type_desc As 'Method'
         ,Coalesce(C.name, AK.name) As 'Signing Object'
From      sys.crypt_properties As Cp
    -- Get the schema
  Inner Join    sys.objects As O
        On O.object_id = Cp.major_id
    -- Asymmetric Key (if any)
  Left Join     sys.asymmetric_keys As Ak
        On Ak.thumbprint = Cp.thumbprint
    -- Ceritificate (if any)
  Left Join     sys.certificates As C
        On C.thumbprint = Cp.thumbprint

I was doing a round of mass service account password changes today on one of our development servers and came across this bit of strangeness; despite making several attempts to update the account and password in the Configuration manager the SSIS service refused not only to start up, but also failed to give any indication as to why (the application logs were horribly silent on anything from either SSIS or even the service manager).

So I went into the back door and fired up the Services applet and refreshed the password in there. One message informing me the account had been granted the ‘Logon as a service’ privilege and the service was up.

What beats me is why the configuration manager refused on multiple times to accept the change. Not saying we should all ignore the config manager from now on but I myself will bear this in mind for future weirdness.

Apparently JournalSpace.com has learned the lesson of an what happens when you don’t have an effective disaster recovery strategy the hard way.

Using OS X as a operating System – $1998, Employing a technician who knows a thing or two about backups, $65,000. Not using mirroring as a backup process – Priceless. Life needs tapes. For everything else there is unemployment.

Apparently JournalSpace.com has learned the lesson of an what happens when you don’t have an effective disaster recovery strategy the hard way.

Using OS X as a operating System – $1998, Employing a technician who knows a thing or two about backups, $65,000. Not using mirroring as a backup process – Priceless. Life needs tapes. For everything else there is unemployment.