I have been working on email stuff on and off for the last… forever.
One of the very handy and easy to use tools to have in one’s pocket for testing email functionality with a particular SMTP server is the ability to quickly send email through a selected server from the command line. Just like using telnet to test ports makes day-to-day IT life easier vs. having to grab and install some extra tool, so also does the ability to shoot emails off from a CLI.
I have been fiddling about with setting up a SQL Server 2012 Failover cluster using an Equallogic SAN. After a whole lot of digging about I found two different posts on two different sites which got me about 90% of the way there. However there were some key “gotcha’s” and other information that was missing in both cases and I wanted to document those here in addition to referencing the articles I followed for my setup.
BTW – Just my 2-cents, but setting up clustering is complicated… especially when you throw SQL in the mix. It isn’t bad once you have done it a few times (I tested again, and again, and again in a virtual environment) but there are honestly like 50+ considerations to take into account to ensure everything goes correctly.
I am assuming if you are here you already have a general understanding of failover clustering, know what you are wanting to do and why. This article also doesn’t really cover all aspects of high-availability. I don’t discuss how your SAN(s) should be networked for example. I do touch on a few items though that fall in this area. This isn’t meant to be comprehensive and a lot of it is just for personal reference.
So here are some tips if this is your first go around. These are in NO particular order or grouping (this is very “stream of thought”) so I would suggest reading this from start to finish at least once rather than referencing it as you are going through your setup.
Currently I am working on integrating some 10Gbe switches into an existing 1Gbe network. Being completely new to 10 Gbe I wasn’t prepared for the volley of new terms, acronyms, and gotcha’s that were thrown my way.
Initially I had a very hard time finding answers to some basic questions. So I figured I would write a quick post for everyone else having the same struggles… Excuse my laymen explanations and gross oversimplifications which are to follow… To some I may sound the dunce, so be it. I hope this is helpful to all the other dunces :).
One of most difficult things to find (imho) is information about API and Service URL’s for just about any and all applications. Microsoft is better than some (Dell, I am looking at you…) but it can still require some metaphorical google search back flips to get to the right information.
That said… I wanted to quickly document the right mix of URL’s that must be allowed in order for Windows OS license activation to work: (more…)
SQL instances running a lot of databases can get a bit confusing as to what is kept where. Especially if said instance was setup by someone else in times prior. To that end, there is a very handy query you can run in SSMS to quickly return the on-disk file locations of all SQL data files. You can use this query exactly as-is with no modification:
SELECT name, physical_name AS current_file_location
This will output a nicely formatted table including filename and folder path, including the Master database and Temp Database files.