I’ve been working with SQL Server for 18 years and over that long span I’ve seen a lot of different techniques for tuning and development.
There are essentially two principles of development, Code First and Database First. Naturally, being a life long database professional I’d say that Database First is the only way to properly approach a project. You’d start with a business analyst gathering requirements, build out the database ERD, and then start coding.
I’ve been using Microsoft’s cloud database for some time now. I’ve had a few customers with various performance problems and thought I’d take a moment to highlight the interesting behavior you may run into as well.
With less than we week away, I can say that I’m really excited to reach more people in the community and share my knowledge. I’ve delivered webcasts for Microsoft Premier customers before but never one for the greater SQL community.
For those of us in the US, it’s our day of independence. A day that stands for FREEDOM and happiness. Fireworks will light up the sky tonight! For the rest of the world it’s another random day in July. But don’t worry everyone can celebrate “Free”dom with this new community tool.
I’ve spent the last couple years writing, improving, and using this tool at my customers. This health check now has more than 300 data points and even pulls out bad practice and concerns from your procs. As of today, I gift it to the community. #SQLFAMILY
Over the years I have come to see that every database has what I call data type drift. Simply put, data type drift is when you have columns with the same name but different data types or length. I’d say about 97% of databases I’ve reviewed have some form of drift. So why is that number so high?
I was recently doing some work on my Windows 10 desktop and placed a drive on one of the slower internal disks. It’s old. It’s 7200 RPM. It’s just plain slow. All that’s fine and good as I’m not doing any production workloads from this development machine.
I thought that until one query was taking exceptionally long to complete. I pulled up Resource Monitor to check CPU and storage pressure. Everything looked just fine. In fact, the D: drive wasn’t even listed as having any IO latency.Read More »
SQL TECH BLOG 