July and August are big months for me. July is when my MVP Award comes up for renewal (and as I posted here, I was renewed for the sixth time this year, for a total of seven Microsoft Cluster MVP awards). August is important in other ways. It was in August of 2007 that went I took the leap, went independent, and formed Megahirtz, LLC after leaving Avanade – no safety net. So this month starts year eight of being my own boss. When I started, I said to myself, “Well, get through year one and we’ll see about year two.” All these years later, I can’t imagine going back and working in a typical 9-to-5 (is there even such a thing?), go in the office every day type of job. I would if I had to, but I’m not seeing that need. SQLHA is going strong so that is not even an option.
I’ve certainly had my share of ups and downs in the world of independent consulting. I sometimes submit my “So You Want to Be a Consultant?” talk to SQL Saturdays. It has been picked on occasion, and I enjoy delivering it. If you are thinking of going independent, the best piece of advice I can give to anyone wanting to strike out on their own is this: have both a good accountant and a good lawyer. So many people underestimate the business side of consulting. It consumes a lot of time. If you are not prepared to run a business and everything that it entails, don’t leave the hug of corporate life. Why an accountant and lawyer? You need people who understand things like taxes (they’re not the same as your personal stuff), VAT, understanding the legalese of contracts, and so on. What you don’t know will hurt you. Your skills alone will not make you a success. You also need a plan to market your business and your skills, but that to me is much easier than ensuring everything is kosher with the business. Screw that up, there will be no independence.
This Friday, August 28, marks the four year anniversary of the death of my friend, Mike Kenwood. Lasrt year, I wrote a pretty long blog post about it on the third anniversary., so I’m not going to rehash everything there but I encourage you to read it. I get very moody and contemplative around the end of August. It is what it is. I still miss him and think about him quite often, even at times reaching for the phone. I don’t think that feeling will ever go away. Many of us tend to focus on the small things in there here and now and on what I like to call “first world problems”. It is nice (if that is even the right term) to take a step back and assess things and be thankful for what you do have and can do, not what sucks and you cannot do.
I’m not saying I’m always Mr. Warm and Fuzzy every minute of every day, but in the years since Mike has passed away, I have gained a whole new perspective on things. Our time on this planet is short, so enjoy it and try not to sweat the small stuff (says the guy heads down writing a book and under stress to get it done lol). I’m no less competitive and driven today than I was when I started Megahirtz, but I do take time to smell the proverbial roses. You should, too.
As humans we tend to use money as a measuring stick of success. No amount of money would bring Mike back to be a father to his daughter or a husband to his wife. I joke sometimes you can’t take it with you when you go and money does not buy health or happiness. I truly believe that. Whether I make $1.98 or way more than that, it’s the company you choose – friends, family, colleagues – that contributes to the quality of life you enjoy. I would rather have a small number of good friends that I trust over a gaggle of backstabbing acquaintances. Quality over quantity.
Unfortunately. there are a lot of fake, petty, manipulative, self-centered people in this world who focus on the negative and try to bring others down or wish them harm in one way or another. Tearing someone else down to build yourself up is no way to be. Reality check: the world does not revolve around you. There is always someone smarter or better than you out there. It’s one reason I am always learning and growing professionally and personally. Get complacent due to arrogance, and you will fall behind. I have seen it happen. We should strive to help others and mentor if we can. I try to in my own way.
Anyway, I am thrilled to be starting year eight on my journey of independence. I love what I do, whether it’s the more traditional consulting arm and helping customers in that way, speaking at events, or training people. Mike loved to be outdoors and be adventurous, and I try to now have a bit of that in me as well. No, you won’t find me hiking or biking – not my thing. Ironcially, Mike always tolde me that he lived a bit vicariously through me in my world travels since he did not get to do it. It wasn’t a regret – he enjoyed his life at home with his family. He was happy for me, and I for him. So I carry his spirit for life wherever I go. Mike was interested in Australia and asked me to bring him back a boomerang on my first trip (which I did). I will definitely be thinking of him when I go back in a few months to teach in Brisbane and Canberra. I think he would have loved it there.
Yesterday I blogged about one of the most important features in Windows Server 2016 Technical Preview 3 and how it affects SQL Server – domainless WSFCs. I am genuinely stoked for that feature because it will open up some scenarios we have never been able to do with clusters. There are other cluster-related enhancements I will be writing about, but today is not that day.
A few months ago, I wrote a blog post entitled Need a User Interface for Windows Server Technical Preview 2? It’s Not On By Default. The title is self explanatory. With TP2, you had two installation options: Server Core and Min Shell. Since then, Microsoft listened to many of us and put a GUI option into Setup for TP3. Unfortunately, it was a course correction too much to the left. When you are installing Windows Server 2016 TP3, you get two options as shown in Figure 1: Windows Server 2016 Technical Preview 3, which is Server Core, and an option that is Server with Desktop Experience.
Hold the phone – Desktop Experience? Is my Server now a client OS? No!
Prior to Windows Server 2016, when you got a GUI for Windows Server, it was not Desktop Experience. Desktop Experience brings with it things like the cool Tron-like Windows background. Along for the ride are other things – like Media Foundation and Ink and Handwriting. Lord knows I need to use my N-trig pen on a server (NOT)!
Of course, you can simply run Remove-WindowsFeature Desktop-Experience and get rid of it, but why should we have to do extra work? A server OS – or any OS for that matter – should just work the way it should out of the box. The problem is, removing Desktop Experience does not remove things like Ink and Handwriting in TP3. In fact, you can’t remove them at all via the GUI as shown in Figure 2.
PowerShell to the Rescue! If you run the following command:
it turns out you can remove them. So if you want to get rid of everything at once, just add Desktop-Experience and another comma. Reboot and you’re all set. Figure 3 reflects the feature removal in the GUI post-reboot.
You can also switch to MinShell or Server Core if you’d like via PowerShell as well.
I really do like a lot of what Windows Server 2016 is bringing to the table, but as I have always stated, Setup is your first introduction to any product. Make it a miserable experience, and people will not be starting off on a good foot. While I’m excited to use Windows Server 2016 and get my customers on it because of some of the benefits, this is putting a damper on the overall experience. But, it has to be said, at least Microsoft is listening. They put a GUI option back in … just the wrong one. Ideally Microsoft should give us three installation options for Windows Server:
- Server Core
- Full UI (but not Desktop Experience, Ink and Handwriting Services, and Media Foundation)
That way admins can pick the OOB experience they want without any additional work.
At least Microsoft is listening to us and they made a well intentioned, but IMO misguided, change to the TP3 Setup experience. We will see what the next release brings …read more
You may have noticed that Windows Server 2016 Technical Preview 3 was released today. For the full announcement from Microsoft on the Server & Cloud blog, click here. There is one important line that all SQL Server folks should pay attention to:
Increase flexibility by removing domain-specific constraints for SQL Server clusters
Yes, kids. That means you can create a Windows Server Failover Cluster (WSFC) with NO – I repeat NO – domain required. This will not work for clustered instances (FCIs) since they still require domain-based service accounts, but it will work and be supported with SQL Server 2016 for AlwaysOn Availability Groups (AGs). I would not expect Microsoft to go back and certify this configuration with SQL Server 2014 (or 2012 for that matter), but you never know. If you try and want to use 2012 or 2014 in this configuration, as of the posting of this blog post, it would be considered unsupported – don’t do that as it is the antithesis of mission critical.
This is huge and for many, will simplify AG configurations. No more CNOs and VCOs (although this was possible in Windows Server 2012 R2, you still needed the nodes to be domain joined). I have been testing this configuration with SQL Server 2016 CTP 2.2 and the builds of Windows Server 2016, but due to NDA, have not been able to talk about it until today because it had not been publicly announced. For everyone who has been complaining how DBM was better, you got your wish – this allows you to have an AG configuration which is the same as the one that you had using database mirroring (DBM) with certificates.
The demo configuration I will show below is multi-subnet to simulate two different data centers. Node One (SYLVESTER) is in subnet one and Node Two (TWEETY) is in subnet two. These are not joined to any domain as shown in Figures 1 and 2.
So far, so good. My WSFC’s name is PUDDYTAT. The entire configuration can be seen in Figure 3.
I have an AG named AG1 with a Listener named GRANNY. Its info is in Figure 4.
While you can see that the AG is up and running in Figure 4, Figure 5 shows it working in SSMS. Viola!
If you don’t believe me yet, to further drive the point home, I left the accounts running the SQL Server instances as local accounts (NT Service\MSSQLSERVER and NT Service\SQLSERVERAGENT). This can be seen in Figure 6. Figure 6 also shows the properties of SQL Server where the ability to use AGs is enabled. This is very real and works as advertised. I’m excited about this.
As always, there are some caveats to this configuration that you should be aware of:
- At least in TP3, you cannot create or administer the WSFC via Failover Cluster Manager. Everything must be done in PowerShell. This may not change between now and RTM of Windows Server 2016, so if you are uncomfortable administering clusters via PowerShell, this is not a configuration you should be using. If you try to use Failover Cluster Manager, you will see the message in Figure 7.
- This will make using the AG Wizard to do your backups a bit trickier since shared directories usually use domain-based accounts. You may have to manually deal with them if you are not using domains or do not have trusted domains.
- There are some flags that get tripped during Cluster Validation (namely, no domain) that should be fixed by RTM. This is a known issue in TP3.
- With no domain requirement, this also means no Kerberos however, if each node is in a different domain (i.e. one in Site, another domain in Site B) but crosses boundaries, you should be able to have Kerberos. I have not tested this configuration yet (it is on my list). This should even enable cross-domain migrations – again a scenario I have yet to test. There are more, but hey, first blog post and all of that.
- You will need to add the DNS suffix manually otherwise the WSFC will not come online
- Networking is clearly crucial here, and things like DNS replication will be important.
- File Share Witness is not supported, so you will need to use asymmetric disk (which defeats the purpose of AGs with no shared storage) or Cloud Witness.
The good news is now that this is public, this bit will most likely make it into the book. I wanted to do a quick blog on it, and if I get time, I will show how I created this in a blog post soon. Also, with this now public, I may make this one of the labs for my PASS Summit 2015 preconference session Advanced SQL Server Availability Architectures and Deployments. Sign up now!
UPDATE: I just saw that Subhasish of the Cluster team on Windows just blogged a bit more about the Windows side of this.
Also, due to the fact that the AG configuration is standalone with no storage and there was an error during validation (TP3 known issue I mention above) due to the fact these are not domain joined, I used the -Force and -NoStorage options of New-Cluster.read more
Where in the world will Allan be this fall?read more
How to create HA/DR designs based entirely on your needs.read more
Is the book done yet, Allan?read more
If you’re used to a graphical interface in Windows Server, wait until you install Windows Server Technical Preview 2.read more
2015 is shaping up to be a busy year for training, and […]read more