Nothing to say

So...it has been an impressively long time since I had anything to say here, and that is not likely super likely to change soon.  I am still working as a Database Administrator (though my role may be changing soonishly), and as such still running into interesting problems and finding ways to work around them, I just never think to post them here.  I will see if I can't keep that in mind, but I have every confidence that the internet will keep on truckin' just fine without my input.

In any event, I'll bug you later.

New Beginnings

It occurs to me that while my daily life is of interest to almost nobody, I might be able to write about the technical hurdles that I face on a daily basis and save other people time (or generate comments about better ways to accomplish things).

To that end, I am clearing out old posts and beginning anew.

Huzzah!

Cross Domain SQL Replication in a trusted environment

Howdy, this is quite a break from my usual posts, but addresses a problem I recently managed to "solve".

Scenario: You are working in an environment with 2 domains, and the domains trust eachother. You wish to get replication working from SQLA in DomainA to SQLB in DomainB, but SQL Server replication does not allow FQDNs. I am presenting SQLA as the publisher, and SQLB as the subscriber.

The first thing you need to do is ensure that the publisher is set to save the snapshot to a UNC. I still use the default path, but make it a share (C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\repldata becomes \\SQLA\repldata). With the share permissions set properly this will enable the subscriber to get to the snapshot.

The next thing you need to do is a hack. I say this without shame because it should not be necessary. In the hosts file on SQLB you need to add an entry for SQLA. If the FQDN for SQLA is sqla.domaina.com with an ip of 192.168.65.101 then the whole point is so that you only need to use "sqla", so your hosts file entry on SQLB should look like

192.168.65.101 SQLA

If SQLA needs to be able to communicate with SQLB, a similar hack may be needed there.


Once that is done you should be able to get replication working. Keep in mind that if you are changing the default location for any existing publications from the drive path to the UNC that the snapshot will need to be regenerated before that goes into effect.

Thanks, and please let me know if this was useful.

G4 Powerbook hinge problems

My roomate has a Powerbook G4, and as apparently happens, the casing around the left hinge has cracked so opening it allowed the hinge to exert force against the display back and force it to split. In looking for replacement parts I came to the conclusion that it is rather expensive to fix, and came up with my own solution (albeit an unaesthetic one). I took 2 alligator paper clips (Staples brand binder clips) which I measured as having a 5/16ths inch base. I cut the round parts (where the lever is inserted into the clip) off on one side, and clipped it to the offending part of the display case with the recently flattened edge on the inside of the display. See the pictures below, and feel free to email me any questions.

Please note that this is a first run. I intend to get my dremel and cut the clip closer to the base so the pressure is applied about halfway between the outer edge and the display itself, right now it is almost right at the display. My bottom clip also has a bit of metal I used to wedge it open. I did that clip first, and found that while it was more work, it looked better with that snapped off. Cutting the rounded parts off of the outside is prbly also advisable, though I was very careful to make sure there was no sharp edge making contact with the case. Any improvements I leave to you, though if you find something that works particularly well please let me know.