SQL Server Articles, Tips and Tricks
Have you noticed that storage is a major bottleneck in all cloud providers (Azure, AWS, Google Cloud)? Machine throughput (total MB/s) for storage is severely limited. Even on very expensive server VMs they give you not much more than about …
Introduction If you are in search for a good ORM, keep reading. Alan Hyneman, the author of SQLPlus.net was very kind to give an interview and answer tough questions that a developer might ask. Feel free to ask more in …
When multiple sessions insert into the same table, and something unique is there (uq index, uq constraint), a “duplicate key” error (2601, 2627) occurs from time to time, almost inevitable. If your app is affected with intermittent “duplicate key” surprises, …
Introduction EVERYBODY should read this! Whether you have a big database that needs speed, or other valuable data like documents or just personal pictures you do not want to lose when disk fails (disks DO fail without notice, just a …
Introduction There are thousands of indicators (Perfmon Counters, system views, …) one can track to monitor SQL Server, but not all of them are relevant. If I need to pick one, that would be “Processes Blocked”.
While ago I wrote SSMS Addin called SQL XDetails. It was not updated long time because GUI integration with new SSMS versions were different every time and too much for my poor csharp knowledge. I am a DB guy after …
In 2 days, 11th of May, I speak in Helsinki, Finland about SQL Server Magic. The country with the best education in the world, thinking out of the box, plus very nice nature and the best air quality. I am …
In less than two weeks I will speak at SQL Saturday conference in Stockholm, Sweden. I am very excited to meet people there and see at least a glimpse of their culture and way of thinking.
Your SQL Server may be slow for a peculiar reason: a run-away query that pushes-out all other queries from the plan cache, like a huge wave. So called “tsunami query”. Tsunami query wipes other plans from the cache and makes your SQL running slow. Creating tsunami query is easy and usually not intentional: a developer concatenates values in SQL command string. As it “works on my machine”, it easily slips to production (nobody tests for this, right?), and the monster is loose!
Introduction You might have lot of virtual machines (VM) for Dev and Test environments. And a storage with huge amount of space to fit all databases. What are the options? Probably the best for performance would be to connect to …
