About Me
Hi, I'm Lince Sebastian — a SQL Server Database Administrator based in India. I spend most of my working life inside SQL Server: keeping production instances up, untangling slow queries, and figuring out why a job that ran fine at 2 AM decided not to run today.
What I Do
- Database Administration — installing, configuring, patching and maintaining SQL Server instances; managing log shipping, availability groups, backup strategies and recovery planning.
- Performance Troubleshooting — reading execution plans, fixing blocking and deadlocks, tuning indexes and queries, and hunting down the one procedure that quietly consumes 40% of server CPU.
- High Availability & DR — keeping things up when things break, and having a tested answer for when they break anyway.
- Automation — because nobody should be doing the same maintenance task by hand for the rest of their career.
Why I Started This Blog
Most DBA problems are not new. The same handful of issues show up again and again, and usually the fix is something small — a missing index, a stale statistics refresh, a log file that wasn't sized for the workload. But finding that answer usually means hours of reading forum threads and blog posts written years ago.
DBA Scrolls is my attempt to write those things down. Every post here is meant to be a working answer: a real problem I ran into, the script or fix that resolved it, and enough explanation that you understand why it worked so you can adapt it. My goal is a practical library of scripts and troubleshooting steps — not theory, and not marketing.
About This Site
DBA Scrolls is a personal, non-commercial project. Posts may contain links to vendor documentation or third-party tools. I do not accept paid posts, and I do not write about products I haven't actually worked with. Scripts are provided as-is; always test them in a non-production environment first.
Get In Touch
Found something wrong, or have a problem you'd like me to look at? Comments are open on most posts, and you can reach me via the contact page. Corrections are genuinely welcome — I'd rather have an accurate post than a fast one.