Eitan Blumin is currently working as a Senior SQL Server Consultant, Solutions Architect, and DBA Team Leader at Madeira Data Solutions, the leading Microsoft Data Platform consulting company in Israel. Other than his day-to-day consultant work, he also co-hosts the popular “SQL Server Radio” podcast with Guy Glantser, writes professional materials for the SQL Server community, delivers professional presentations and courses, and serves as a pivotal source of expert knowledge for the Madeira team.
Imagine the following: You have a couple or more SQL Servers with some sort of High Availability solution between them (AlwaysOn Availability Groups, Database Mirroring,… Read More »Automatically Enable or Disable Jobs Based on HADR Role
Sometimes, when you have a table with an IDENTITY column, there could be scenarios in which weird “gaps” are created between different IDs.
There can… Read More »Re-align Identity Last Value to Actual Max Value
Not Trusted Foreign Key Constraints are such for which integrity of the underlying data is not guaranteed. This most commonly happens when you perform Bulk Insert into a table that has a FK constraint, or when you disable a FK constraint.
Having not trusted foreign keys can be dangerous for data integrity, because it’s possible to have invalid data in your table (despite the existence of the foreign key).
Read More »Find and fix untrusted Foreign Keys in all databases
When administrating a SQL Server instance with multiple CPU cores and heavy workload, it’s common to see SQL Server creating and using execution plans with parallelism. The instance configuration “cost threshold for parallelism” is what determines for SQL Server the minimum sub-tree cost before it starts considering to create a parallelism plan. The default “out-of-the-box” value of this configuration is 5.
However, in some cases, we would want to increase the default configuration of “cost threshold for parallelism” to something higher than the Microsoft default of 5, thus decreasing the frequency in which SQL Server creates parallelism plans.
Read More »Planning to Increase Cost Threshold for Parallelism – Like a Smart Person!
In my previous post, Advanced Service Broker Sample: Multi-Threading, I showed a rather advanced scenario where we can implement a multi-threading solution inside the SQL… Read More »Advanced Service Broker Sample: Asynchronous Triggers
I managed to encounter several times a scenario in which an application needed to execute several queries independent of each other, and then group them
… Read More »Advanced Service Broker Sample: Multi-Threading
“Orphaned Users” is a common issue in SQL Server where a Database User is no longer associated with its relevant Server Login.
This often happens when the Server Login is deleted (even if it’s recreated later), or when the database is moved or restored to a different SQL Server.
Read More »T-SQL Script to Fix Orphaned DB Users Easily
Performing a transaction log backup every 15 minutes has its advantages. But it also has disadvantages. Ever tried to restore hundreds of transaction log backups one by one in order to bring your database back from disaster? Not a bit of fun that is. Check out this useful script that I prepared to help sort this problem out.
Read More »T-SQL Script to Roll Forward Transaction Log Backups
Today I’ll talk about the main physical JOIN operator types in SQL Server (Nested Loops, Hash and Merge Joins), their differences, best practices, and complexity (which determines when the SQL Server optimizer would use them in execution plans).
Read More »The LOOP, HASH and MERGE Join Types
Dynamic Search Queries SQL Injection is a widely known issue with databases that work as back-ends for websites and applications. In… Read More »Dynamic Search Queries versus SQL Injection
