SQL Server 2005 has changed many of the ways in which we will use SQL Server in the future with a dizzying array of new features and enhancements. Sureshkumar Ramakrishnan brings us the second part in a series looking at what these changes do and how to use them.
2007-11-28 (first published: 2006-12-06)
20,477 reads
SQL Server 2005 has changed many of the ways in which we will use SQL Server in the future with a dizzying array of new features and enhancements. Sureshkumar Ramakrishnan brings us the first part in a series looking at what these changes do and how to use them.
2007-11-27 (first published: 2006-11-29)
27,985 reads
Data cleansing is something that constantly occurs in all RDBMSes, not just SQL Server. However it's easier on some platforms than others. New Author Sureshkumar Ramakrishnan has written a script that shows how you can easily remove duplicate rows in SQL Server. Read about his technique and see if it might come in handy in your environment..
2006-03-10 (first published: 2004-12-20)
47,457 reads
SQL Server 2000 has a great scheduler in SQL Agent, but it isn't integrated with anything else. And with lots of servers, having a centralized environment is essential to keeping yourself from being overworked. Author Sureshkumar Ramakrishnan brings us his technique for running SQL Server jobs from an external scheduler.
2005-08-24
14,537 reads
By Steve Jones
I caught this interesting item over on Pinal Dave’s blog: Eleven Interview Questions that...
By Hemantgiri
I use color-coded connections in SSMS to distinguish Production, Pre-Production, UAT, and Development. But...
Comments posted to this topic are about the item Split Large Queries in Athena...
Comments posted to this topic are about the item 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 SallyI 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