Finally, it has happened…

Last month I blogged about my absence from the blogosphere.  If you want, you can read about it again – here.  Granted, it has been a month and I still have been slacking.  I am […]

August 2012 S3OLV Meeting

Well well well.  It has certainly been a long time between announcements on the blog about meetings for the Las Vegas SQL Server Users Group. We have had to cancel a couple of times in […]

A Trio of EachDB

When administering a larger database environment, sometimes one needs to perform repetitive tasks.  Performing repetitive tasks becomes more and more painful (maybe even demoralizing) with the larger the number of databases that might exist on […]

Maintenance Plan Owner

We all inherit things from time to time through our profession.  Sometimes we inherit some good things, sometimes we inherit some things that are not so good.  Other times we inherit some things that are just plan annoying.  Yet other times, we inherit things that may be annoying and we probably just haven’t discovered them yet.

Database In Recovery

What do we do? Have you ever run into a database that is in the “In Recovery” state? If that has happened, have the bosses and/or endusers come to you asking “What do we do?” […]

Are my Linked Servers Being Used?

This is a follow up to an article published on 3/1/2012.  That article showed how to find what linked servers were created on your instance of SQL Server.  You can read it here. This article […]

System Base Tables

On January 19th, I published a post about the Dedicated Administrator Connection.  I spoke very briefly of the system base tables in that article.  Today, I want to dive into these tables a little bit […]

Missing Indexes

SQL Server has means built into it to track possible missing indexes.  This used to be found through the use of the Index Tuning Wizard.  The process has improved over time (you can sort of […]

Public Role and Security

A good rule of thumb with the public role is to leave it be.  Do not add permissions to this role.  Add permissions on a per database  and per group of users basis.  Create roles within the database and grant permissions to that role – in each database.  And remember the rule of least privilege – don’t grant more permissions to a user/role than necessary to perform the job function.  Just the same as in an airport – everybody has their role and it is strictly defined.  If the user need not have access – then don’t grant the permissions.

A Trio of Tools

I have talked about tools for SQL server a few times in the past.  You can read some of what I wrote here and here. Since writing those last articles, I have come across more […]