166 reputation
9
bio website glompix.com
location Lexington, KY
age 28
visits member for 4 years, 9 months
seen Dec 26 '13 at 1:41

I'm Stuart Branham, a professional software developer (and sometimes graduate student) in Lexington, KY.

I'm proficient in C# and a myriad of web technologies, including jQuery. I'm pretty good with ASP.NET MVC, WinForms and SQL Server. My goal is just to write the best software I can while also balancing an awesome life away from Visual Studio.

Even though I primarily work in the Microsoft world on a day-to-day basis, I feel just as "at home" in an emacs terminal on Linux.

I'm fond of cats and like prog rock. I've been playing piano since age 5, and pick up a guitar every once in a while. The game I'm playing in my gravatar is Beatmania IIDX. It's a lot of fun. I'm a total goon.


Apr
5
awarded  Popular Question
Feb
25
awarded  Popular Question
Dec
19
accepted Why am I getting warnings about missing DLLs when adding a node to a WSFC?
Dec
19
answered Why am I getting warnings about missing DLLs when adding a node to a WSFC?
Nov
29
comment Why am I getting warnings about missing DLLs when adding a node to a WSFC?
@floyd - I'm doing an AlwaysOn AG, I thought you used standalone installation for that, since you're not going to be sharing storage? That's what we did in our test lab when trying this and it seemed to work. We're not combining the technologies at all either, just a simple two-node AG.
Nov
28
asked Why am I getting warnings about missing DLLs when adding a node to a WSFC?
Sep
17
accepted Should I never put a transactional replication distributor on a subscriber server?
Sep
17
comment Should I never put a transactional replication distributor on a subscriber server?
Unfortunate, but makes sense at least for simple cases. You don't want the server that you're allowing to go down be a distributor.
Sep
14
comment Should I never put a transactional replication distributor on a subscriber server?
Thanks! Very helpful.
Sep
14
awarded  Commentator
Sep
14
revised Should I never put a transactional replication distributor on a subscriber server?
added 33 characters in body
Sep
14
comment Should I never put a transactional replication distributor on a subscriber server?
I should have been more precise with my words. This isn't a failover cluster instance, it's an AlwaysOn availability group. If the node hosting distribution goes down, replication stops. Wouldn't replication stop if the line between pub/dist goes down as well? That would be more of a concern to us than the log filling up, I think.
Sep
14
asked Should I never put a transactional replication distributor on a subscriber server?
Jul
6
accepted What's the cleanest way to reversibly break SQL Server replication?
Jul
6
comment What's the cleanest way to reversibly break SQL Server replication?
Effort. In our case it's fine to break replication in production for a minute or two, and far less of a cost than duplicating our environment. I sure wish we had replication in our test environment, though...
Jun
29
asked What's the cleanest way to reversibly break SQL Server replication?
May
17
comment What are the exact storage requirements for an AlwaysOn implementation?
Thanks for the answer! Now that we've been able to play with it, we understand how it works a bit better.
May
17
accepted What are the exact storage requirements for an AlwaysOn implementation?
Jan
30
comment What are the exact storage requirements for an AlwaysOn implementation?
Forgot that publisher responsibility failover is provided in AlwaysOn.
Jan
30
revised What are the exact storage requirements for an AlwaysOn implementation?
added 7 characters in body