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

The Basics of Sizing a SQL Server Database

Sizing a database can be one of the most arduous tasks a DBA, analyst or developer must attend to. It?s time consuming and more hours go into analyzing the database than actually sizing it. This article focuses on how to monitor the database?s growth after its deployed and contains some tips on how to size it before deployment. We will also dive a little into how to benchmark your database against a robust data load.

(21)

You rated this post out of 5. Change rating

2008-08-01 (first published: )

43,891 reads

SQLServerCentral Article

Upgrading SQL Server 2000 DTS Packages to SSIS

If you're like Brian Knight, you probably have dozens if not hundreds of DTS packages running around that you're terrified to touch. SQL Server 2005 has some interesting methods to upgrade your packages to SSIS with minimal effort. This article shows you a few ways that you can use to upgrade and some of the drawbacks.

(14)

You rated this post out of 5. Change rating

2008-05-23 (first published: )

66,121 reads

SQLServerCentral Article

Step-by-Step Guide to Clustering Windows 2000 and SQL Server 2000

In this next article of the SQL Server in the Enterprise Series, we'll explore how to cluster Windows 2000 and SQL Server 2000 in a step-by-step manner. After this article, you should be able to cluster a SQL Server 2000 machine for failover availability in an Active/Active cluster.

(8)

You rated this post out of 5. Change rating

2008-01-18 (first published: )

155,280 reads

Technical Article

Change Data Capture with SSIS

In this presentation, Brian Knight shows you how to use canned SSIS components to detect data changes in a source table and only load new or conditionally update changed records. He shows you two methods: one using the OLE DB command and another using a set based operation and demostrates you the performance differences between the two.

You rated this post out of 5. Change rating

2007-01-12

2,108 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