One way to find out why your database might be slow.
Finding out why a database is slow
One way to find out why your database might be slow.
One way to find out why your database might be slow.
This month's T-SQL Tuseday is about dipping into your cookie jar. Write about what keeps you going in tough times.
I love issues on old machines and editions... This one is about Error 3314 severity 17 state 3 combined with error 665.
This post is a response to this month’s T-SQL Tuesday #111prompt by Andy Leonard. T-SQL Tuesday is a way for the SQL Server community to share ideas about different database and professional topics every month. In this month’s topic Andy asks why do we do what we do? First and foremost, because i like it and because … Continue reading Why do i do this?
In my previous blog i shared my experience on my first day of work at a new client (https://wordpress.com/read/feeds/90430081/posts/2132980200). After this initial day, time to get to know the sql estate at hand. Accounts were already taken care of, and i got the admin level. I can check whatever i want and it shows a … Continue reading Analyzing an environment
I had to help a collegue out today. He had to delete about 12 million rows on a 13 billion row table. And his statement (delete from [table name] where spec_id = 1) never got anywhere. First thing i tried was to encapsulate the statement in a transaction. This transaction was put within a while … Continue reading Deletes on large table
My first T-SQL Tuesday post!
This year, i'm starting with my first real DBA consultancy job! 😀
Blog number 5 and already looking back? Sure, to appreciate the future, you have to know the past. Or something like that 😉 2018 has been a very, very interesting year. The first half started out quite normal, besides writing an advanced SQL training that lasts two days. I don't know how i got round … Continue reading 2018 review
My way of creating a SQL Server 2017 Failover Cluster on Windows Server 2016 Core edition.