Finally! A full year of traffic. I aimed to blog at least once every few days but fell short. I plan on blogging a lot more in 2017, especially with the release of SQL Server 2016 and all the cool new features it has.
As you can see, 2016 was a 10x increase of visitors compared to 2015.
There was a +350% growth this year in page views compared to the prior year.
62% of the visitors are from the U.S., 7% from India, and the rest of the top 10 include UK, Canada, Brazil, Germany Australia, Netherlands, Singapore and Russia.
On to a great 2017!
How to View and Read SQL Server Setup Log Files
Usually when something goes awry in a SQL Server, the first place that comes to mind to check is the SQL Server error log, or Windows event log. But what if the error was during SQL Server installation? What if you’re installing SQL Server and suddenly the GUI disappears? Poof! Gone! There were no pop-up errors or anything to give you a hint of where to start troubleshooting.
What do you do?
When you first kick off a SQL Server install, there are a couple directories and files that are created. The directories are time stamped and the files within the directories record a detail “process-by-process” snapshot in a plain text file for troubleshooting and record keeping.
Check out this MSDN link to all the setup files SQL Server creates during initial installation. It’s definitely a great place to start when troubleshooting install problems. Add it to your bookmarks!