I know I have been fortunate to write back-to-back on topics around SQL Server. I get a number of you do take time in writing down to me over emails, comments and even sometimes over Skype pings. I see every such mail as an opportunity to learn something from you for sure. One of my friends from the networking team pinged me to check if I knew a query about the last bootup time he had:
SQL SERVER – Starting Up Database – Why Multiple Times in Errorlog?
Fixing error messages is something which keeps me energized because there is something challenging that is put in front of me. I know these can be frustrating times working on errors, but they also make you learn more about the product and make you better. My day life includes creating demo’s for sessions and learning new techniques that will enhance my knowledge. One of the days I started my machine and immediately connected to my SSMS environment to just see that it was taking unusually longer than expected time to get the instance up and ready. Let us see blog post about Starting Up Database.
My instinct was to scan through the ERRORLOG, I found the below series of messages.
SQL SERVER – Attaching and Restoring Database in Clustering Generates An Error – Notes from the Field #115
[Notes from Pinal]: In my career, I have seen many database experts who are great with what they do, but when they have to work with clustering or AlwaysOn solutions, they usually avoid it. The reason is that there are not many experts who know this subject well enough. One thing I always personally felt that the documentation is also not widely available when it is about clustering. If one receives some error, they are usually lost. This is when I reached out to Eduardo and asked him what can we do to if we face error while attaching or restoring database in clustering environment in SQL Server.
SQL SERVER – FIX Error 18456, Severity: 14, State: 6. Login failed for user
One of the blog which I wrote earlier was also on Login failed for user with state 58. Let us see how to FIX Error 18456.
After reading that blog, one of the blog reader contacted me and told that she is getting state 6. I thought this error are very common and is important to demystify some of the reasons for the same. I have asked completed error message to assist him. Here is the message she shared:
Error: 18456, Severity: 14, State: 6.
SQL SERVER – FIX Error 18456, Severity: 14, State: 58. Login failed for user
One of the most common and searched SQL Server failure is around “Logins”. Login failed for user has always been tricky and interesting to troubleshoot. I don’t think there is a silver bullet to easily troubleshoot the same. With every version of SQL Server, there are enhancements made in error reporting, which try to make life on DBA’s easy. In previous version of SQL, whenever there is a login failed, it would print message in the SQL ERRORLOG along with the state of login failed. It was difficult for a DBA to find the cause further and it all boiled down to doing a number of permutations and combinations of resolution over the internet. Let us see how to FIX Error 18456.
SQL SERVER – Huge Transaction Log (LDF) for Database in Availability Group
One of my blog readers posted on Facebook asked following question about Huge Transaction Log:
Hi Pinal,
We are using AlwaysOn availability group for our production database. The database is fairly large in size as its around 260 GB. The database transaction log file grows around 2.5gb every day. Over the weekend the DBA team noticed that the Log file for this database bloated up to around 230 GB and then seems to hold steady. While troubleshooting I noted an error that the rebuild Index failed due to “Availability_Replica”. Here is the error which we saw in ERRORLOG
SQL SERVER – JSON Support for Transmitting Data for SQL Server 2016 – Notes from the Field #114
[Note from Pinal]: In this episode of the Notes from the Field series database expert Kathi Kellenberger explains about JSON Support for Transmitting Data for SQL Server 2016. Kathi is an amazing instructor, she was the SQL author I have read in my early career. The reason, I love SQL Server because her writing has instigated love for this technology in me. Today she brings a relatively interesting topic for database experts. Read the experience of SQL SERVER – JSON from Kathi in her own words.