SQL RNNR

A database can be offline at the time that you take over responsibility of the database. You will be asked when it was taken offline. This script will help you get a reasonable deduction for that offline event in the absence of better data.

Database recovery (crash recovery) is a nerve wrenching situation under the wrong conditions. It can be as bad as a root canal and just as necessary to endure that pain at times. When the business is waiting on you waiting on the server to finish crash recovery, you feel nervous at best. If you can be of some use and provide some information back to the business, that anxiety dissipates and the business becomes more calm as well. While the previous script can help you get that information easily enough, I want to introduce the easiest method to capture that information currently available.

If you can use a database to create automation routines to help sustain your work life, you can certainly do the same to sustain your personal life. Databases are an essential piece of both my personal and professional life.

One of the more gut-wrenching experiences of a DBA is to have a database get stuck in recovery. This typically happens when the server was rebooted unexpectedly and typically coincides with a rather large transaction.

An indexed view is a view where the result set from the query (the view definition) becomes materialized in lieu of the virtual table result set of a standard (non-indexed) view. Many times we see that an indexed view would be created to help improve performance. Far too often, an indexed view is created without consideration for the costs of the indexed view.

The first critical task any data professional should ever learn how to do is how to connect to SQL Server. Without a connection to SQL Server, there is barely anything one could do to be productive in the data professional world (for SQL Server).

There seems to be a myth out there that when deadlocks come a-knocking, then just throw this little directive (ROWLOCK) at it and all will be well. This is total fiction and we will explore that in this article.

A powerful little expression in SQL Server is the CASE statement. The CASE statement has the ability to “transform” data per business rules to help better understand the data in a given query. In the simplest form, the CASE statement is a statement that evaluates a list of conditions (in order) and returns the first matching result expressions.

One of the frequently required job functions of the database administrator is to track disk space consumption. Whether this requirement comes from management or from a learning opportunity after a production outage, the need exists.

One of my biggest reasons why I do what I do, boils down to the challenges that I frequently get to encounter. There is a wild satisfaction to working on a very difficult and challenging task, product, tool, profession, skill, etc. This satisfaction often involves reward and a sense of accomplishment.

Jason, great post and work in explaining the XE. I was hoping if you can create an article or one…

A bigger problem I've seen than connecting through a dialog box like Management Studio does, is when developers or testers…

Actually that is more of an "it depends" rather than the rule. Read these debunked myths which I am sure…

90% is not a good idea if the tables primary key is an identity as data then is always going…

I remember being asked a different type of trick question in an interview. The interviewer went thru a list of…

Yes it is a good idea. A fillfactor of 100 is great if the data in the table is always…

When the ad account disappears, then you could see various abnormalities that could be intermittent.

That is fine.

I like to use that one as well.

In your outstanding script called "Script to auto generate a security report for your SQL Server instance" where can I…