SQL SERVER – Error 15559 – Error 912 – Script Level Upgrade for Database ‘master’ Failed. Let us fix the error in this blog.
SQL SERVER – Introduction to SQL Azure Database Throttling
In standalone versions of SQL Server, if your SQL Server receives more concurrent requests than it can service simultaneously, it will queue the requests for later processing (subject to certain limits—generally available memory on the box). For example, if you have the max worker thread configuration option set to 100 and there are already 100 queries submitted to the server than any new requests are simply queued until one of the worker threads completes and can pick up the request. Except in fatal circumstances where DBA intervention is required this will allow all of the requests to eventually complete (or potentially timeout, if the client specified this setting). Let us understand about SQL Azure Database Throttling.
SQL SERVER 2016 – STRING_SPLIT Function Performance Comparison – Notes from the Field #118
SQL Server 2016 is around the corner. We already have SQL Server 2016 RC0 released and many of us have started to test out various aspects of the same. For many years users have created temporary tables as well as used cross apply functions to split a large string and make it a table. I think every single time when I was assigned this task, I disliked it as the methods I used never made me happy. Well, the situation is now changed now with STRING_SPLIT function in SQL Server 2016.
In this episode of the Notes from the Field series database expert Kathi Kellenberger explains about easy and amazing functions of SQL Server. Kathi is an amazing instructor, she was the SQL author I have read in my early career. Today she brings a very new topic for database experts. Read the experience of Kathi in her own words.
SQL SERVER – Mirroring Error 1412 – The remote copy of database has not been rolled forward to a point in time that is encompassed in the local copy of the database log. (Microsoft SQL Server, Error:)
With mirroring gone as deprecated feature, I have tried to keep away from exploring into what has been happening in this space. But what can I do when customers still use them? The challenges for consulting is pushing the boundaries of my comfort zone here. This made me revisit some of my learnings again. As part of this exercise, I learnt a minute or two which I personally felt was worth a share as part of this blog post. Here is a story for Mirroring Error 1412.
SQL SERVER – The Need for Data Tier Elasticity in Cloud Computing
Many application workloads are characterized by resource use that varies over time. Usage peaks can vary depending on the time of the day, week, or month, and outside events. Even a big sport game or an online sale can bring usage spikes. With traditional, on-premises technologies, IT departments typically provisioned enough capacity to manage worst-case scenarios. This approach to scalability can leave a significant amount of underutilized resources in the data centers, most of the time—and inefficiency that can impact overall costs. Cloud computing promises answers to such inefficiencies. In the cloud, you can balance costs and performance by deploying new resources when needed and shrinking them during slack periods. This elastic approach matches demand and capacity.
SQL SERVER – Installing SQL Server Management Studio 2016 – Step by Step
New versions bring new learning. To keep myself up-to-date, I have downloaded RC0 (release candidate zero) for SQL Server 2016 and while installing SQL Server I was surprised to see the feature list. Installing these bits were something I was wanting to do as we are getting closer to the release date. But something got me by surprise though, check the screenshot shown below, there is no mention of SQL Server Management Studio 2016:
Interview Question of the Week #062 – How to Find Table Without Clustered Index (Heap)?
Question: How to Find Table Without Clustered Index (heap)?
Answer: In SQL Server, when we create a primary key it automatically creates clustered index on the table, unless we explicitly mentioned not to create one. Due to this reason, the most of the table where there is a primary key, there are good chances it is also a clustered index key.