Steve Stedman Bio
I have been using SQL Server for over 34 years, and I have realized that out of all of the jobs that I have had, and the projects that I have worked on, the ones that I enjoy the most include SQL Server and good people.
I run Stedman Solutions, LLC a SQL Server consulting firm specializing in SQL Server Managed Services.
EMT at Sandy Point Fire Department
Current Projects
- Creating an online classroom curriculum for SQL Server professionals.
- Over 10 classes available.
Database Corruption Challenge.
Always doing SQL Server Performance Tuning.
The Database Health Reports: Database Health Reports program is a powerful performance monitoring and diagnostics solution that alerts administrators to health, performance or availability problems within their SQL Server environment, all from a central console. Download it now and enjoy.
Getting Help from Steve and the Team
Contact us for your Free 30 minute consultation ORschedule your appointment now.
Steve, I would like to see more same DMVs on SQL 2012 Availability groups and AlwaysOn both from an administrative/maintenance and health point of view.
Hi Steve
Just loaded down and install locally the beta 10 (January 2015) version of Database Health…..first let me say it a brilliant and wonderful product so please, please keep up the good work……
Now for the bad news…..when I launch the product I get a message indicating that I need to upgrade (which I just did) and absolutely nothing happens…..help….it is a great product and I really do not want to stop using it……
Bill,
Life has been a bit hectic, over the last 5 weeks I had planned to get the next version of Database Health out, but I ended up losing my job, and starting a SQL Server consulting business. http://StedmanSolutions.com.
I am working on the update to Database Health, and should have something out early next week. Sorry for the delay.
-Steve
The new version, Beta 10.1 is now available. Sorry for the delay.
http://databasehealth.com/download/
-Steve
Week 10 – Database Corruption Challenge. I was wondering you are going to posted the solutions for week 10.
Thanks for running this challenge it was a great learning experience and found it interesting on how people came up with the correct answers.
Thanks
Steve,
I need a mentor to teach me how to be a Ninja level data analyst with SQL. Would you be interested ?
Hi Vijay,
Just fill out the contact form at Stedman Solutions to get the conversation started.
https://stedmansolutions.com/services/free-30-minute-consultation/
-Steve Stedman
Hello Steve,
Hope you had good week so far. I am getting the below error whenever I am test the connection for the HistoricDB on only one of the servers but not others.
Also I can see that the Login DBHealthUser is not getting created after successfully configuring the Historic database.
Thanks,
Sai
Starting test…
1. Testing HistoricDB connection (MYDOMPRDSQL02).
HistoricDB connection is good.
2. Testing configuration for (MYDOMPRDSQL02).
ERROR: Database configured multiple times.
Hello Sai –
You will want to look at the table [dbo].[instanceMonitor] in the DBHealthHistory database.
SELECT *
FROM [DBHealthHistory].[dbo].[instanceMonitor]
Then look for multiple configurations for the same instance, and delete one of them.
That should clear up the multiple instance configuration issue.
-Steve Stedman
Very good