Scanning Every Server with Dynamic Reports
I am really big on using a couple of methods to scan every server in my environment with a huge array of queries. Why? because There’s the classic purposes to doing this. How do I do it? I have two core methods, but multiple flavors of those methods. Via either a PowerShell script I wrote
Standard SQL Server Machine
When you build a plain old Vanilla Windows Machine supporting a SQL Server instance, what does your run book look like? My run book is an excel spreadsheet with lots of formulas that update or make visible items based on selections in the first ten rows or so. it has maybe one hundred rows in
ttry
simple try catch
Lonely Secondary Log Shipping
Have you ever had that rare situation where you need log shipping to another server, but have zero access to the primary server? I encountered that issue recently and my solution was two parts. A Secondary Log Shipping Target without a Primary. Pretty Cool. I had the need to consume transaction logs into a StandBy(ReadOnly)
Performance Tuning
Code Performance improvements are a layered approach. I think of it as multiple passes and focii to Statistics. slightly out of date stats on huge tables can greatly affect performance. Index Optimization: Review missing indexes, remove unused indexes. Data Management Views: find what is slow on the whole server, and start digging in. Not just
Who is this Lowell guy anyway?
Hi I am Lowell Izaguirre, and I’ve am a cutting edge Senior Database Administrator for SQL Server. I’ve got the paper pedigree for those who care, two MCSA’s and an MCSE as well, but the key is my experience, deep scripting capabilities, and the tools I use to make myself the fastest, most efficient DBA
sp_getddla and sp_getddl
If you have ever worked with SQL Server, and wanted to script a table, you know it is a GUI process, that behind the scenes, is calling SQL Management Objects(SMO) to create the script for you, which you can then copy and paste. But what if you want to script the table and put it
Massive tempdb usage implies a missing index opportunity
Tripped over a great example yesterday, where an application was recently upgraded, and ran out of temp db space for the tables, and not the log. The TLDR was that an inefficient query was sticking 500MB of data into a tempdb table to satisfy a query, and the query was called hundreds of times, with