By Garth Jones April 12, 2016 marks the end-of-life for SQL Server 2005. What does this mean to a ConfigMgr administrator? You need to upgrade to at least SQL Server 2008 if you are still running Microsoft System Center Configuration Manager 2007, otherwise 2005 won’t be supported. If you are running System Center 2012 Configuration Manager or higher you don’t need to worry as the minimum SQL server version is 2008. By the way, the end date for the 2008 version of SQL is July 9, 2019. What does end-of-life for SQL Server 2005 mean for Enhansoft? It means that starting today we no longer support SQL 2005 with any of our products. More importantly, it allows us to start using all of SQL Server 2008’s features and functions! I’m truly excited about this move and can tell you that our team is ...
The System Center Operations Manager data warehouse contains a wealth of information that can be surfaced by running reports in the console. However, using reports isn’t the only way you can extract valuable information from SCOM; you can also write tiny snippets of SQL to return exactly what you need to see. Recently, we had a customer approach us with a specific dashboarding request. They were using the HTML5 dashboards that come with our Live Maps Unity solution to show information about service level agreements. While our product has a built in widget that shows whether you’re currently meeting your service level objectives or not, they also wanted to see how they had performed against their service level agreements in the past. This was a perfect opportunity to use the new SQL Query w...
We’re excited to announce that we’re investing in a number of enhancements to Reporting Services in SQL Server 2016, drawing largely from the wealth of valuable feedback you’ve taken the time to share with us. With SQL Server 2016 CTP 2.3, now available for download, you can take a sneak peek at some of our work in progress, while there’s more to come in upcoming monthly CTPs.
The SQL Server 2016 Community Technology Preview (CTP) 2.3 is now available for download! This release fully embraced the “Cloud First” tenet, as this release build was deployed to SQL Azure Database service first, running in production prior to the release build.
Recently, I had a need to list the SQL agent jobs, owner names and whether each job was enabled or not. Here is the result: SELECT j.name AS AgentTaskName, SUSER_SNAME(j.owner_sid) AS JobOwner, CASE WHEN (j.enabled = 1) THEN 'True' ELSE … Continue reading →
Topic today is monitoring. Catherine Wilhelmsen (b|t) is hosting this month’s T-SQL Tuesday blog party. The party was started by Adam Machanic (b|t) in December of 2009. I’ve been looking a lot of SQL Server installations over the past year. … Continue reading →
If you ever have a need to migrate SQL Server databases between servers; particularly a backup/restore scenario, you need to be aware that the database security login ids are not automatically migrated. Here are some notes on this task. Once … Continue reading →
SQL Health Checks Healthy SQL is an important topic… I’ve gotten involved in a number of SQL health checks and would like to share some of the key methodology, metrics investigated and tools/utilities used. There are at least two main … Continue reading →
As a follow-up to the post, how to install a service pack for a SQL Server cluster, it is important to have the ability to roll back an update. Fortunately, Microsoft has made this process fairly easy. The following process … Continue reading →
Quick tip… any drive that you use for SQL Server data or log files should be formatted as NTFS 64K size. SQL will give you better performance at the file level… I’m thinking of writing a post of best practices for SQL Server as it relates to ConfigMgr, would this be useful?Filed under: ConfigMgr, SQL, […]
Tuning your SQL server is important because it can impact overall server performance. Tuning expensive queries is imperative because your database server’s performance can be affected by a slow and unresponsive query. Monitoring the performance of each query in SQL server is key – for example, if a single query is taking time to respond, you’ll know CPU utilization is high. This causes a strain on other applications using the same SQL. Let’s look at a few reasons that cause a query to perform poorly. Server Load: If there’s a sudden spike in your server load then the queries will get slower – this is likely due to other applications like Antivirus scan or backup process running on the server. Indexing Issues: If the database isn’t indexed then it’s going to make your queries slower. Poorly...