I write and play around a lot with SQL object level permissions and I love working with them. Having said that, I also explore the ways people want to run code to achieve certain objectives. In the DBA’s world when the number of servers we are talking is not a single digit, they are looking for ways to automate and script out. Recently I was at a retail company backed team in India and they said they have close to 1500+ databases which are running at their various outlets and point of sale counters and the DBA team working to manage these were still less than 10. I was pleasantly surprised by this level of details. To achieve certain tasks, they have to allow non-sysadmin users to run xp_cmdshell. Here is the issue which was they wanted to solve.
SQL SERVER – Error Installing Microsoft Visual Studio 2010 Shell
There have been many situations where rather than performance tuning, I am contacted for an installation issue. Due to my knowledge by looking at logs and pin pointing at the error message, I am able to fix them as well. In this blog post we will learn how to fix Error Installing Microsoft Visual Studio 2010 Shell.
SQL SERVER – Could Not Load the DLL xpstar.dll, or One of the DLLs it References
Once upon a time a customer wanted to apply a patch on SQL Server instance, but it failed at the end to start SQL Server services. As usual, I asked to check ERRORLOG and found below information. Let us see errors related to the DLL.
SQL SERVER – Edition Upgrade – Invoke or BeginInvoke Cannot be Called on a Control Until the Window Handle has Been Created
One of a unique advantage of freelancing is learning more and more. I get a chance to hear some of the real word problem and it gives me immense pleasure to provide a feasible solution to them. This blog is interaction on the airport when I was coming back from a recent trip from Canada. After seeing me on airport, an old client of mine met and said hello. While having a discussion, he told an interesting issue of SQL upgrade and he wanted an idea. He showed me below error message related to edition upgrade.
SQL SERVER – SQL Audit Date Time Does Not Match Machine Date Time – Solution
Even though my consulting is mostly around performance tuning, I can see many customers who want to start using the new capabilities of SQL Server for their existing application as they plan to do an upgrade of their infrastructure. In one of engagement with a bank, they wanted to explore more about SQL Auditing capability. Since they were new I got engaged with them in implementing compliance, which they must follow. In the recent past, I have written below blogs on SQL Audit.
SQL SERVER – Event ID 1045 – No Matching Network Interface Found for Resource ‘Cluster IP Address’ IP address ‘10.10.10.10’ (Return Code was ‘5035’)
One of my clients implemented AlwaysOn Multi-subnet listener. This is one of the message which I have heard from few other AlwaysOn availability group customers who are having multi-subnet deployment. This client reported that they are not able to bring listener online on one node, which was added newly. When they attempted to fail over AG resource in the cluster, we could see below messages reported in event logs. Let us see how we can fix errors related to no matching network.
SQL SERVER – My Thoughts – Autogrow of File ‘SQLAuth_Log’ in Database ‘SQLAuth’ was Cancelled by User or Timed Out After 30020 Milliseconds
If you are seeing this error in the ERRORLOG on your production server then you must read this blog. I have collected some information about the message and its causes. Let us learn about Autogrow of file.