Duplicate Indexing Woes
Why would you ever create duplicate indexes? Does that even make sense? Steve Jones isn't sure, and that's for another day, but it sure caused him some problems. Follow along and find a solution for tracking these down.
Why would you ever create duplicate indexes? Does that even make sense? Steve Jones isn't sure, and that's for another day, but it sure caused him some problems. Follow along and find a solution for tracking these down.
Full text indexing is interesting, but not always easy for the user to apply well. Chris has some ideas about to make that
Red Earth Technologies announces the release of version 1.3 of Superior SQL Builder, its SQL tool that allows users to visually build complete SQL scripts without typing any code.
Superior SQL Builder introduces new SQL scripting technology, allowing users to quickly and easily transform their database data. In version 1.3 this scripting technology has been extended and enhanced so that complex SQL scripts can be built in less time and with greater ease.
Frank gives us his take on Codd's Rules. If you're new to databases, this is the core theory that resulted in the development of RDBMS. If you're more experienced with databases, maybe now is a good time to return to the rules to see how you're doing!
Ever wanted to use the SQL Trace system stored procedures instead of Profiler, but got intimidated by the cryptic system stored procedure calls? Then this article is just for you. It will show you how to use SQL Trace system stored procedures and provide you with wrapper stored procedures, that can be used to quickly get server side traces up and running.
Steve Jones takes a first look at the next version of SQL Server. It's been sitting for some time, but with the NDA lifted, here's some first impressions of the tools.
Andy started writing about worst practices a long time ago and returns this week with one that is short and sweet - why defining rows that exceed 8060 characters is a very bad idea and how you can avoid it.
This service pack contains bug fixed, plus enhancements including test email button, sorting, and drill down.
Needing to number rows with a sequential id is a pretty common request. Sometimes it's because the user hasn't made the transition to 'set based' thinking, sometimes it really is a valid request (more or less!). Greg provides several different techniques to help you achieve sequential numbering.
This article proposes a system where extra data is stored in a simple row based table and retrieved using the 'store key'. It's not a new concept of course, but the author explains how and why he chose to implement. Feedback should be interesting!
By James Serra
Once again there were a number of Microsoft Build announcements related to data and...
A good week ago I hosted the monthly T-SQL Tuesday blog party. I invited...
By Steve Jones
I was messing around with SQLCMD and I realized something I hadn’t known. I’ve...
I have an issue where I have a Bill of Material list of items...
Comments posted to this topic are about the item Follow Your Hunch
Comments posted to this topic are about the item What Happens When You Ask...
I have a SQL Server 2022 English default installation on a server. I want to detect if there are any upper case characters in rows and I have this code:
SELECT CustomerNameID,
CustomerName
FROM dbo.CustomerName
WHERE CustomerName = LOWER(CustomerName)
Here is the sample data I am testing with:
CustomerNameID CustomerName 1 John Smith 2 Sarah Johnson 3 MICHAEL WILLIAMS 4 JENNIFER BROWN 5 david jones 6 emily davis 7 Robert Miller 8 LISA WILSON 9 christopher moore 10 Amanda TaylorHow many rows are returned? See possible answers