January 3, 2013 in Uncategorized
Today I was working on a server and wanted to confirm the SQL alias settings were correct. There are two ways to do this and I wanted to compare both techniques.
1 – CLICONFG (Bad Way)
The old stand-by. Trusty EXE file names that just work. Win + R + CLICONFG.EXE is a favorite for keyboard shortcut key gurus.
To see 32-bit settings run “%SystemDrive%\Windows\sysWOW64\cliconfg.exe” Yes, not as easy to type.
But wait a minute. Both windows look exactly the same! Whaaaaat?? That’s no good. In a world of 32-bit only this worked fine, but things change and our tools should too.
2 – SSMS (Good Way)
I install SQL Server Management Studio (SSMS) on all of my SharePoint web front ends (WFE) for support and troubleshooting. It’s a great way to confirm the WFE can “see” SQL and connect successfully. If your organization has a separate DBA team which manages SQL, this is even more helpful because you can look at the databases and run queries even without RDP access to the SQL machines. Checking storage used, last backup time, and permissions are all helpful read-only tasks we can safely do with SSMS.
With SSMS installed, you get a Start Menu icon for “SQL Server Configuration Manager.” Launch that and you’ll be able to view aliases for both 32-bit and 64-bit drivers.
Both are in one place! Clearly labeled and easy to read! Now that’s much better in a modern 32/64 world.
So there you have it. Two different ways to look at your SQL alias settings.
As much as I used CLICONFG.EXE over the years, today I use the GUI because it’s a helpful reminder to look at both 32 and 64-bit settings all at once. Consistency = fewer issues = happy admins.