Something I have mused over for a long time is whether or not I should pursue certifications in SQL Server. I don’t talk about it at home for fear of a frying pan over the noggin from my wife…She’ll just tell me to do it and stop thinking about it all the time.
Do you often run a few variations of index queries against your SQL Server instance and look at multiple resultsets? Once upon a time, I did too. Now I rely on the query in this post. It’s not a finished product and I’ll no doubt revisit and add a few more columns and/or logic over time. However, it’s great for pulling back index keys, include columns, fragmentation, scans/seeks and so forth.
IT moves at an incredible pace. We seem to be constantly talking about a new technology or something which is around the corner. If you sit still in IT and stagnate, you’ll quickly be falling behind the crowd. Blink and you’ll miss it!
I was playing about this weekend and trying to use the DBCC PAGE command and stumbled across a function which was certainly new to me which could tell me on which page my data is stored.
sys.fn_PhysLocFormatter (%%physloc%%) as PhysicalRID,
ISNULL(MiddleName,'') as MiddleName,
order by LastName, FirstName, MiddleName
I was recently looking over a bunch of scripts which I had saved within a single .sql file and thought it would probably be a little more concise if I pull the data all together rather than run individually.
One of my developers asked me today why one database was in single user mode on his development server. This is part of their restore process which puts the database into single user mode prior to dropping the database for a restore. I’ve been meaning to fix their code, but it does normally work so is low on my priority list.
We’ve all used DBCC SHRINKFILE or DBCC SHRINKDATABASE, right? It’s a really usefull tool. However, I stumbled across a blog by Paul Randall and learnt something new. The shrink process can fragment your indexes!
While SQL Litespeed offers significant savings in space, that does not mean you won’t necessarily have space issues if you don’t clean up your backups.
Back in the day when I had Litespeed at my disposal, I started off using the maintenance plans which look very similar to the maintenance plan designer that you will be used to in SQL Server 2005. It was a very basic plan consisting only of a full backup of all databases and then delete any backups over 3 days old.
Welcome to my blog! My name is Clive Strong and I am a DBA/Database Architect from Egham, Surrey, UK.