SQLintersection & DEVintersection Conference Descends On Las Vegas November 10-13
DevIntersection and SQLIntersection conference will bring together experts from Microsoft, SQLSkills, .NET Rocks, and 90 industry gurus.
DevIntersection and SQLIntersection conference will bring together experts from Microsoft, SQLSkills, .NET Rocks, and 90 industry gurus.
My “Success” story describes the import process when it works without a hitch, while my “Challenge” story highlights a common difficulty encountered when using the Microsoft Import and Export Wizard, and then offers a solution.
Most people prefer to work with the platforms that they are familiar with, but there is always pressure to try new, exciting technologies when others have success. Steve Jones explores the idea of switching platforms.
Besides the technical skills required to be a proficient SQL Server business intelligence developer, there are numerous "soft" skills that can contribute to your success.
It is widely acknowledged within the SQL Server community that baselines represent valuable information that DBAs should capture. Unfortunately, very few companies manage to log and report on this information, and DBAs are then forced to troubleshoot from the hip and scramble to find evidence to prove that the database is not the problem. This article will make a compelling argument for why DBAs must start capturing baseline information, and will create a roadmap for subsequent posts.
What's the most important thing about your application? The code? The accuracy of its calculations? The layout of the reports? Steve Jones has another opinion.
Aaron Bertrand supplies a script which generates two separate sets of commands: one to drop all foreign key constraints, and one to create them again. These scripts are stored in a table so that, if you drop the constraints and then disaster of some kind strikes during the create, you still have everything handy and can troubleshoot if needed.
This article shows a problem with P2P replication doesn't replicate DDL schema changes and something you might want to check.
Who checks on those who manage our systems? Is there auditing in place for those accidental DBAs?
When you're importing data into an RDBMS in bulk and an exception condition is raised because of a constraint violation, you generally need to fix the problem with the data and try again. The error won't tell you which rows are causing the violation. What if you've thousands of rows to search when it happens? There are solutions, writes William Sisson.
By Steve Jones
Here are the resources for my talk at Day of Data Boston. Slides –...
By Steve Jones
I’ve covered the values in a number of previous posts on the Book of...
By Arun Sirpal
When the evidence names the database, it says so. When it doesn’t, it stops....
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