Additional Articles

Clustering for Indexes

There is nothing spectacular about using indexes per say. However, on many occasions I have come across a variety of SQL coders that never consider validating that the index they think they are using is efficient or even being used at all. We can all put indexes on the columns that we think will be required to satisfy individual queries, but how do we know if they will ever be used. You see, if the underlying table data is constructed, contains, or is ordered in a particular way, our indexes may never be used. One of the factors around the use of an index is its clustering factor and this is what this article is about.


3,412 reads

Cursors with SQL 2000 Part 1

This series of articles will examine the purposes, uses, and optimization of cursors in SQL 2000. SQL languages are designed so groups of records, or sets, can be manipulated easily and quickly. The speed at which groups of data can be altered, updated and deleted, demonstrates why working with sets is the preferred method. However, there are places where cursors are a better choice.


2,572 reads

Optimizing Your SQL Code with SQL Server 2005

A common complaint of database administrators (DBAs) is that performance bottlenecks are not among those problems that one can fix "by just throwing hardware at it." Thus, database servers must provide tools and techniques to help administrators address this issue. On that aspect, SQL Server 2005 does not disappoint.


2,373 reads

Auto Fix Orphaned Users

Add this procedure to the master database, it can then be executed from any DB to fix orphaned users (very useful when moving back to development). Using sp_msforeachdb with the proc allows you to resolve orphaned users in all databases in a single command: SP_MSFOREACHDB "USE ?; EXEC SP_AUTOFIX_USERS;"

2004-12-15 (first published: )

2,715 reads

Easy Package Configuration

One of the age old problems in DTS is moving packages between your development, test and production environments. Typically a series of manual edits needs to be done to all the packages to make sure that all the connection objects are pointing to the correct physical servers. This is time consuming and gives rise to the possibility of human error, particularly if the solution incorporates many DTS packages. Many companies have provided their own custom solutions for managing this problem but these are still workarounds for a problem that is inherently DTS's.


1,761 reads


Approaches to running Databricks ETL code from Azure ADF


Databricks is fantastic, but there is a small issue with how people use it....

Creating a New Sequence–#SQLNewBlogger


I wrote about sequences in an editorial recently and decided to start using them....

An All Star Lineup for EightKB


An online conference is coming on June 17, 2020 that is full of high...

Read the latest Blogs


Authentication failed

By adisql

Hi , Added source and Target servers as Linked servers  in Intermittent Server(Third Server).And...

Minus Query

By khwabekhan

Comments posted to this topic are about the item Minus Query

Do You Think About CheckDB?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Do You Think About CheckDB?

Visit the forum


SQL Server Q&A from the SQLServerCentral community

Get answers

Question of the Day

Minus Query

See possible answers