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,776 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,676 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,383 reads

Blogs

Query deadlock info in Azure SQL DB

By

A couple of weeks ago, a developer came to me and wanted to know...

MSSQL Database Property LastGoodCheckDbTime to Get the Last Successful DBCC CHECKDB on a Database

By

Database Property LastGoodCheckDbTime to Get the Last Successful DBCC CHECKDB on a Database As one...

Dynamic Warehouse & Lakehouse Connections in Microsoft Fabric Data Pipelines

By

When you develop data pipelines in Microsoft Fabric (the Azure Data Factory equivalent in...

Read the latest Blogs

Forums

Baseball Everywhere

By Ryan Booz

Comments posted to this topic are about the item Baseball Everywhere

How to run custom python module on SQL Server?

By yyang5823

I am working on a small test script on SQL server 2022 using python...

Upgrade to SQL2019 from 2012 Query is taking time, Need Query Optimization steps

By ralahari

Upgrade to SQL2019 from 2012 Query is taking time, Need Query Optimization steps and...

Visit the forum

Question of the Day

Sensitivity Ranks

I want to use the ADD SENSITIVITY CLASSIFICATION DDL to mark some columns in my SQL Server 2022 database as PII. Can I use this code?

ADD SENSITIVITY CLASSIFICATION TO dbo.sales.price,
    dbo.sales.discount
WITH (
    LABEL = 'Highly Confidential',
    INFORMATION_TYPE = 'Financial',
    RANK = 'INTERNAL ONLY'
);

See possible answers