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,108 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,965 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,240 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,811 reads

Blogs

Goodbye, Microsoft

By

A few years ago I took a new job at Microsoft, working as a...

The SUM of Nothing: #SQLNewBlogger

By

I caught this interesting item over on Pinal Dave’s blog: Eleven Interview Questions that...

How to Move the SSMS Status Bar to the Top and Color-Code SQL Server Connections

By

I use color-coded connections in SSMS to distinguish Production, Pre-Production, UAT, and Development. But...

Read the latest Blogs

Forums

Today's AI

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Today's AI

Split Large Queries in Athena with a Simple Modulo Trick

By Rahul Gupta

Comments posted to this topic are about the item Split Large Queries in Athena...

Finding Trailing Spaces

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Finding Trailing Spaces

Visit the forum

Question of the Day

Finding Trailing Spaces

I have some data in a SQL Server 2025 database. It looks like this for the dbo.Customer table:

CustomerID CustomerName PreferredName
1          Steve        Steve               
2          Andy         Andy               
3          Brian        Brian               
4          Allan        Allan               
5          Devin        Devin               
6          Steve        Steve               
7          Sally        Sally
I want to detect which names have a single trailing space. The CustomerName is a varchar() and the PreferredName is a CHAR(). Does this query detect the problem rows?
SELECT 
       CustomerID,
       CustomerName,
       PreferredName
FROM Customer
WHERE CustomerName <> RTRIM(CustomerName)
OR PreferredName <> RTRIM(PreferredName);

See possible answers