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,755 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,668 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,374 reads

Blogs

Unlock the Power of Your Data: From Basic to Advanced Data Analysis

By

Data isn't just about numbers and spreadsheets. It holds stories, patterns, and the answers...

Attacking the Weakest Link

By

When I look at a system and think about its security model, the first...

Webinar – Microsoft Fabric for Dummies

By

On Wednesday May 15th 2024 I will give a free webinar on MSSQLTips.com about...

Read the latest Blogs

Forums

The "ORDER BY" clause behavior

By Alessandro Mortola

Comments posted to this topic are about the item The "ORDER BY" clause behavior

Are IT Certifications Still Relevant?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Are IT Certifications Still Relevant?

SQL-CTE reqursive query

By jjjohn

I have table TicketNumbers i     TicketNumber  UID 2    10                        09901a22c7c3acc6786847c775f1d113 6    5                          00dad28bef21f916240d6e8c1c1bd67d 12 ...

Visit the forum

Question of the Day

The "ORDER BY" clause behavior

Let’s consider the following script that can be executed without any error on both SQL Sever and PostgreSQL. We define the table t1 in which we insert three records:

create table t1 (id int primary key, city varchar(50));

insert into t1 values (1, 'Rome'), (2, 'New York'), (3, NULL);
If we execute the following query, how will the records be sorted in both environments?
select city

from t1

order by city;

See possible answers