(Grant Fritchey) So you’re keen to take the first steps to the continuous integration of your database. You have to start by getting your database into source control. You can then begin to automate your build processes in order to generate and test a database. By doing this regularly, you’ll be muc

(Bob Pearson) I ran into a perplexing problem on one of my SSRS servers. This server handled the reporting for internal users, and had a lot of reports that read from our source system, on iSeries DB2 (V6R1), and some reporting from our SQL Server data mart.

(Chris Shaw) Have you heard and understand why processing a ‘select * from any table’ can be negative on the performance impact?

(Bob Pusateri) Earlier this year I did a post on a new method I stumbled up on for copying and pasting file paths. I thought it was a huge timesaver, and I use it multiple times daily. Judging from the reactions I got, I’d say plenty of others have found it useful as well.

(Pinal Dave) Recently I was planning to give a demo about increasing tempdb files and its performance benefit. So while making the demo at home, I was doing multi-tasking. Talking to my daughter, having food and making demo. So, I ran the script and restarted SQL Server service but SQL Service didn’

(Kris Wenzel) All the examples for this article are based on Microsoft SQL Server Management Studio and the AdventureWorks2012 database. You can get started using these free tools using my Guide Getting Started Using SQL Server.

(Rob) Having a Change Log is a good thing. A quick and simple place to find out what has changed on a server and when. This can be invaluable when troubleshooting, matching a change to a symptom especially when assessed alongside your performance counter collection.

(Larry Leonard) Sometimes you’d like to find all occurrences of a piece of text in every stored procedure, trigger, etc., possibly to replace it with a new value. The script below will do just that; it returns the database name, the object name, and the object type.

(Dennes Torres) SQL Server keeps the most-used execution plans in cache, so it doesn’t need to recompile the same queries every time. How can we benefit from this to find potential performance problems in execution plans? Let’s see how to find some opportunities for optimization by using information

(dbafromthecold) A couple of weeks ago I was contacted by Webucator (an online training company) asking if they could use my blog post “Identifying Large Queries using Extended Events” for a video training session in their free series called SQL Server Solutions from the Web.