Randy Dyess

I have been working with SQL Server for over 5 years as both a development and production DBA. Before SQL Server I spent time as both a Visual Basic developer and Microsoft Access developer. Numerous projects upsizing Access to SQL Server lead me to become a full-time SQL Server DBA. Currently I have the privilege of working on one of the world's largest SQL Server "read-world" production installations at Verizon Communications for Verizon's billing project. We have 11 main databases totaling over 9 Terabytes of data with the largest single database over 2.2 Terabytes. My current position is as a development DBA, developing
new Transact-SQL code and enhancing existing code. Before working at Verizon, I worked at one of the largest advertising firms in America: Rapp Collins. There I supported up to 60 SQL Server web databases at a time, with some Oracle thrown in, doubling as both a development DBA and production DBA. Clients before Rapp Collins include: Auto One (a leading auto loan lender), Realpage, Inc. (leader in multi-housing management software) and BlueCross BlueShield of Texas (a large insurance company).

You can find out more about me and my works by visiting my website.

SQLServerCentral Article

Bookmark Lookups

Building high performance applications with SQL Server can be a challenge if you do not understand how the query processor works and how the server uses indexes. SQL Server expert Randy Dyess brings a look at how bookmark lookups are used when satisfying a query and how this can impact the performance of your query.

4.48 (31)

You rated this post out of 5. Change rating

2008-07-18 (first published: )

38,790 reads

SQLServerCentral Article

Obtaining Query Execution Plans Through SQL Profiler Traces

Did you know that you can obtain the execution plans for your SQL Server 2000 queries using Profiler? It is an interesting concept, especially when you need to troubleshoot the queries on a system that you did not develop and cannot obtain source code for. SQL Server guru andy Dyess brings us the technique you can use to find those queries and execution plans.

5 (1)

You rated this post out of 5. Change rating

2005-04-18

16,682 reads

SQLServerCentral Article

Optimizer Join Methods

Understanding the different types of joins used by the optimizer will help developers and DBAs understand how the optimizer is routing their queries. Developers often create queries without knowing that it would only take a few tweaks to produce an execution plan that utilizes one optimizer join method over another. These small tweaks can have dramatic effects on the optimization of the query and the ultimate satisfaction of the query by the end-users.

4 (1)

You rated this post out of 5. Change rating

2005-02-09

22,406 reads

Blogs

A New Word: Vicarous

By

vicarous – adj. curious to know what someone else would do if they were...

SQL Server Cross Platform Availability Groups and Kubernetes

By

Say we have a database that we want to migrate a copy of into...

Using Managed Identities with Azure SQL DB

By

We are trying to get apps and users off of using SQL accounts to...

Read the latest Blogs

Forums

We Stink!

By Grant Fritchey

Comments posted to this topic are about the item We Stink!

View works for me ...but doesn't return results for a user in SSMS but no errors

By krypto69

Hi I have this view to check if a job is running:   SELECT...

Dark mode, other color schemes

By mjdemaris

All, if you are like me and do not care for the built-in color...

Visit the forum

Question of the Day

Internal Checkpoints

Certain internal SQL Server actions cause internal checkpoints. Which of these actions does not cause an internal checkpoint?

See possible answers