Sometimes it helps to go back to the basics and indexing is always a great topic. SQL Server has a wide variety of indexes; but, today we’re going classic and talking about Non-clustered indexes.
Simple post today: How to compare two plans in SSMS.
This task is a task that is often done by a DBA or developer who is wanting to compare changes of an index or perhaps even comparing queries between DEV and PROD.
It seems like SSMS has seen better days. Many developers I have worked with recently complain about Out of Memory issues and other bugs and I personally miss the days of Query Analyzer.
Designing a rock solid application and database can be difficult. New features and overlapping features mean that you’re able to accomplish a single task in many ways. For instance the numeric and decimal data types. Which should you use?Read More »
If you’ve read my blog, I’m sure by now you know that I have no love for GUI tools. I will say they are improving every day and maybe, just maybe, we will see the day when you can click happily away and do everything you want. Sadly, this is not the day.
A while back, SSMS added the “Missing Index” data to the graphical query plan. They even made it really easy to add.
People always ask me what tools I use. Mostly this question comes from the topic of monitoring. I can honestly say that I don’t love any tools and you shouldn’t either.
My time at Microsoft placed me at nearly 300 different clients. As a Microsoft employee I never liked saying, “Go grab this tool so we can look at your problem because SSMS isn’t good enough.”
Foreign keys are an interesting feature of relational databases. They help enforce data integrity, sometimes help improve performance by eliminating joins, and sometimes slow down DML operations (inserts, updates, and deletes).
I was building out a blog post about cardinality today and noticed that sys.dm_exec_query_stats was getting cleared my my Surface Pro 3 dev instance about every 30 to 60 seconds.
I opened object explorer to check if any jobs were running in SQL Agent that may be running DBCC FREEPROCCACHE