Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

Nebraska SQL from @DBA_ANDY

I'm a forty-something Microsoft SQL Server DBA of 12+ years, a devoted husband, and a father of two young boys (with another coming soon!). I have been a DBA at a university, at a major bank, at a healthcare system, and I now work as a consultant with customers across the United States.

Archives: March 2014

We Are Hiring!

My employer Ntirety (a division of HOSTING) is currently looking for multiple SQL Server DBA's.  As you have probably seen from me on Twitter (or on this blog) previously, I joined Ntirety last November as a 100% work-from-home Senior SQL Server DBA.

Ntirety is based out of Boston, but…

Read more

0 comments, 235 reads

Posted in Nebraska SQL from @DBA_ANDY on 31 March 2014

Backup Checksums and Trace Flag 3023

One of the items I always flag when performing a health check on a server is whether backups are being run with CHECKSUM enabled.  As Paul Randal (@PaulRandal/blog) writes in his post "Example 2000/2005 corrupt databases and some more info on backup, restore, page checksums…

Read more

4 comments, 1,301 reads

Posted in Nebraska SQL from @DBA_ANDY on 25 March 2014

Error 701 - Insufficient System Memory - Now what?

This story begins, as so many often do, with a few key elements:
1) A client who experienced a problem on Thursday and waited until Friday evening to report it, even though the problem was "critical" enough to ask us to work on it all weekend if we couldn't solve…

Read more

2 comments, 1,676 reads

Posted in Nebraska SQL from @DBA_ANDY on 20 March 2014

A New Day at #Ntirety

We - the rank-and-file employees at Ntirety - received word yesterday that we had been acquired by Hosting, a cloud and network services provider based out of Denver, CO.  Apparently Hosting did not have a database services division and decided it made more sense to buy one than to…

Read more

1 comments, 184 reads

Posted in Nebraska SQL from @DBA_ANDY on 18 March 2014

Why Did My Job Fail Anyway?

One of my biggest pet peeves when I check a new SQL Server for a client is the fact that by default there is no method of telling why a job has failed.

My philosophy is that all job steps should have output files, no matter how mundane or simple…

Read more

0 comments, 315 reads

Posted in Nebraska SQL from @DBA_ANDY on 12 March 2014