Brian Knight

Brian Knight, MCSE, MCDBA, is on the Board of Directors for the Professional Association for SQL Server (PASS) and runs the local SQL Server users group in Jacksonville. Brian is a contributing columnist for SQL Magazine and also maintains a weekly column for the database website SQLServerCentral.com. He is the author of Admin911: SQL Server (Osborne/McGraw-Hill Publishing) and co-author of Professional SQL Server DTS (Wrox Press). Brian is a Senior SQL Server Database Consultant at Alltel in Jacksonville and spends most of his time deep in DTS and SQL Server.

SQLServerCentral Article

Gathering Random Data

Brian Knight recently had the basic need to retrieve a record from the database at random. What seemed to be an easy task quickly became a complex one. This case showed an interesting quirk with T-SQL that was resolved in an equally quirky way. This quick article shows you a method to retrieve random data or randomize the display of data.

(1)

You rated this post out of 5. Change rating

2003-03-26

9,430 reads

SQLServerCentral Article

Who's to Blame for the SQL Slammer Virus?

Last week the SQL Sapphire (or SQL Slammer) virus hit corporate networks throughout the Internet. Although damage has not been estimated yet, it is sure to be in the tens of millions of dollars. So who is to blame when a virus like this manhandles a corporate environment?

You rated this post out of 5. Change rating

2003-02-03

5,881 reads

SQLServerCentral Article

A Sneak Peek at Entegra

Recently, the SQLServerCentral.com labs had the chance to get a sneak peak at Lumigents latest creation, Entegra, which is scheduled to ship in the second week in December. Entegra monitors database activity and provides a complete record of access to the data and changes to database structure and permissions.

You rated this post out of 5. Change rating

2002-11-13

3,313 reads

SQLServerCentral Article

Creating your own sp_MSforeach stored procedure

This article shows you one of the most time saving stored procedure built into SQL Server and then shows you how you can modify it to affect additional objects like triggers. For example, after this article and the code in the article, you'll be able to disable every trigger in your system in one line of code.

(1)

You rated this post out of 5. Change rating

2002-06-17

16,557 reads

SQLServerCentral Article

SQLsnake Worm Hits SQL Servers and Networks Hard

If you haven't changed the SA password on your SQL Server, you may be soon paying the price. Beginning last week, an old worm has come back in full force, infecting about 100 SQL Servers an hour. Reports of heavy port 1433 scanning began in early may but by the 22nd, the virus really began to take its hold on systems with no SA password.

You rated this post out of 5. Change rating

2002-05-28

4,818 reads

Blogs

When Your Microsoft Fabric Capacity Runs Out: Optimize, Scale Up, Scale Out, or Isolate?

By

Microsoft Fabric makes it wonderfully easy to put many analytics workloads on one platform....

Accessing the Data API Builder MCP Server from VS Code

By

I recently started playing with the MCP Server for SQL Server, which is a...

From DBA or Data Engineer to AI Engineer: A Realistic Path

By

If you spend your days tuning queries, managing pipelines, or keeping a production database...

Read the latest Blogs

Forums

STRING_AGG DISTINCT

By Phil Parkin

Has anyone written a wrapper function (or similar) around STRING_AGG() to allow the retrieval...

In-place OS upgrade or migration to new OS?

By jasona.work

Putting this here as we're currently on SQL Server 2019 installed on Windows Server...

Never is Not the Policy

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Never is Not the Policy

Visit the forum

Question of the Day

Rebuilding All Indexes

I have added a few indexes to one of my tables in SQL Server 2025:

ALTER TABLE dbo.CustomerContact
ADD CONSTRAINT PK_CustomerContact
    PRIMARY KEY (CustomerID);

-- Create index on CustomerEmail
CREATE INDEX IX_CustomerContact_CustomerEmail
ON dbo.CustomerContact (CustomerEmail);
CREATE INDEX IX_CustomerContact_CustomerPhone
ON dbo.CustomerContact (phone);
I then do this to disable one index:
alter index IX_CustomerContact_CustomerPhone on dbo.CustomerContact disable
I see this when I check the index status:Index status for CustomerContactI decide to rebuild all indexes with this command:
ALTER INDEX ALL ON dbo.CustomerContact rebuild
After I do this, what will I see for the index status?

See possible answers