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

Tutorial: Changing the Visibility Objects in Reporting Services

In the last tutorial in this series of Reporting Services tutorials we added conditional formatting to the report. Now that we have created our first report and have added a bit of flare to it, we will go ahead and make it even cleaner. In this very quick demonstration, we will go ahead and change the visibility of rows or columns based on given conditions.

(1)

You rated this post out of 5. Change rating

2004-07-20

18,091 reads

SQLServerCentral Article

Don't Get Left Behind

Production DBAs may be a dying breed. At least according to some sources. While we're not sure that we agree with that, there is definitely a trend that should have you working on your career. The day of the DBA that only manages the operational data store is waning. Today's DBAs need to be flexible and have a number of other skills. Brian Knight looks at a few of the skills that you might to add to your arsenal to be prepared for the future of SQL Server.

(3)

You rated this post out of 5. Change rating

2004-05-21

10,948 reads

SQLServerCentral Article

SQL Server 2005 Feature Survey Results

A week ago, we solicited readers to let Microsoft know which of the SQL Server 2005 announced features mattered most to them. We had a great response, with 890 of you answering the survey in three days. The answers were pretty interesting. The full results can be seen at the bottom of this article.

You rated this post out of 5. Change rating

2004-03-22

11,229 reads

SQLServerCentral Article

Yukon Delayed Again and Named

Microsoft confirmed today that it has delayed Yukon yet again. It also announced that Yukon has an official name and will have another beta added to the development cycle. Get all the info here and share with Microsoft your thoughts about what features are important to you.

You rated this post out of 5. Change rating

2004-03-11

17,803 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