2023-05-01
134 reads
2023-05-01
134 reads
Once you've done a number of SQL code-reviews, you'll be able to identify signs in the code that indicate all might not be well. These 'code smells' are coding styles that, while not bugs, suggest design problems with the code. In this PDF, Phil Factor's put together 119 of those code smells so you can see what to avoid and why.
2014-09-25
12,476 reads
By DataOnWheels
Ramblings of a retired data architect Let me start by saying that I have...
By Steve Jones
A customer was testing Redgate Data Modeler and complained that it auto-generated PK names....
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
Hi everyone, Below is a consolidated summary of what we validated Architecture & data...
Hi all, I recently moved to a new employer who have their HA setup...
Comments posted to this topic are about the item Semantic Search in SQL Server...
I have this data in a SQL Server 2025 table:
CREATE TABLE Response ( ResponseID INT NOT NULL CONSTRAINT ResponsePK PRIMARY KEY , ResponseVal VARBINARY(5000) ) GOIf I want to get a value from this table that I can add to a URL in a browser, which of these code items produces a result I can use? See possible answers