[Notes from Pinal]: First of all, last week SQL Server 2016 released. If you have not downloaded the developer version for free. You can download from here. SQL server 2016 has many different features which are related to performance and stability. One of the feature which attracted me very much is stretch database. I am sure of the name, you might have understood that it is about extending the current features of the SQL Server. Well, the feature is very interesting, and to understand how it works, you will have to read this entire blog post.
SQL SERVER – Event ID 107- Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
Generally, I like to pick and choose the way various services are installed when working with SQL Server. I am careful not to have unnecessary services like “Reporting Services”, “Agent” etc running. I install them and keep them in a switched off state because I don’t like to keep eating away the resources on my PC during startup. But this is more of a best practice in general, I see not many doing.
SQL SERVER – Identifying Application vs Network Performance Issues
But what do you do? Let us learn in this blog about How to Identify Application vs Network Performance Issues and their solution.
SQL SERVER – Configuration Manager – MMC could not create the snap-in. The snap-in might not have been installed correctly
I have always felt the social media has a bigger impact on the current generation. It can easily spoil their time on one side or it can be awesomely productive if utilized the right way. As there are two sides to the coin, social media also have a similar effect on people. I have personally wanted to see the bright side because it gets access to people easier now. The space for being private has decreased and we can easily be web searchable. Whenever I get time, I try to help on public forums and even on my Facebook page of SQLAuthority. Recently, one of the friendliest contacted me with below error while opening configuration manager over Facebook.
SQL SERVER – FIX: Error 1807 Could not obtain exclusive lock on database ‘model’. Retry the operation later – Part 2
I have always mentioned in the blogs that the most sought out blogs would be around troubleshooting or around specific error messages. These blogs are the biggest source of page views from various search engines. I love getting these error messages and an opportunity for me to learn something new. Here is my first blog written in the year 2010 and I still get questions around the blog via emails. FIX: Error: 1807 Could not obtain exclusive lock on database ‘model’. Retry the operation later. Let us learn to fix error 1807 in this blog post.
PowerShell – Querying SQL Server From Command Line
PowerShell is quite an interesting capability that is added as part of Windows. I wonder how many of us really appreciate the power of this tool being out of the box. The more I see it being used in customer locations, the more I get intrigued by what it can do. Let us learn about Querying SQL Server From Command Line via powershell.
SQL SERVER 2016 – Management Studio Highlighting Current Line Option
With every new release, there is changes that are being made to the tools that support it. It is tough sometimes to keep up with the pace. I am always an old school guy and I try not to change the style that involves changes to the way things function. When I installed SQL Server 2016 Management Studio, there was something fresh about the IDE, but I was trying to get to terms to why I was feeling little weird. Let us learn about Highlighting Current Line Option in SSMS 2016.