The Wild Developers of SQL Server like Wildcards
Phil Factor explains the enduring attachment of database developers to wildcards, despite their current deficiencies.
2025-03-17 (first published: 2018-12-17)
489 reads
Phil Factor
- Interests: Motorbikes, Beer, gardening, conservation, Local history.
On Looking and Acting the Part
Phil Factor's offers tips for longevity in the world of IT consultancy: listen well, humiliate no-one and convince others that it was their expertise that solved the problem.
2024-12-27 (first published: 2020-01-18)
430 reads
Idempotent DDL Scripts That Always Achieve The Same Result - Making Changes Only Once: Stairway to Exploring Database Metadata Level 6
Idempotence is the property of certain operations in mathematics and computer science, that can be applied multiple times without changing the result beyond the first time they are run. When you are making changes to a database to deploy a new version, you need to be sure that certain changes aren’t made twice, or in the wrong order.
2023-10-04 (first published: 2016-12-21)
19,675 reads
Potholes in the Road of Progress
Phil Factor looks at some technologists more famous for thwarting progress than for their own creations.
2022-09-02 (first published: 2017-07-17)
315 reads
Reading and Writing your Database's Documentation using JSON
One of the problems to which I keep returning is finding the best way to read and apply documentation for databases. As part of a series of articles I'm doing for Redgate's Product Learning, I've been demonstrating how to maintain a single source of database documentation, in JSON, and then add and update the object […]
2021-06-28 (first published: 2021-05-28)
3,611 reads
Malleable Source Control
Git has proved to be a better fit to the needs and workflow of a database development team than anything that came before. Git is valuable because it encourages branching and merging, giving more choice in the way that your team can work. Due to the ease with which you can adapt Git, there is […]
2021-04-03
154 reads
Exploring Facts About SQL Server Tables: Stairway to Exploring Database Metadata Level 5
Now that we've explored, in preceding levels, some of the information that is available about indexes, triggers, keys and distribution statistics, we can concentrate on the tables themselves and their columns.
2021-01-13 (first published: 2016-12-07)
6,257 reads
Spoofing Data Convincingly: Text Data
Learn how to generate some convincing data for your development databases.
2021-01-05
2,909 reads
2020-12-12
323 reads
Presenting the Facts about Data Breaches
If you're faced by an investigation team, after a data breach, it is no use putting on your 'Mr. Sincerity' face and making vague statements. They want documented facts.
2020-11-14
158 reads
Blogs
Flyway Tips: AI Deployment Script Descriptions
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
A New Word: Fawtle
By Steve Jones
fawtle – n. a weird little flaw built into your partner that somehow only...
Post-quantum key exchange – Insurance policy for your packets
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
Forums
Where Your Value Separates You from Others
Comments posted to this topic are about the item Where Your Value Separates You...
Fixing the Error
Comments posted to this topic are about the item Fixing the Error
T-SQL in SQL Server 2025: Encoding Functions
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
Question of the Day
Fixing the Error
On SQL Server 2025, I have a database that has this collation: SQL_Latin1_General_CP1_CI_AS. I decide I want to run this code:
SELECT UNISTR('*3041*308A*304C*3068 and good night', '*') AS 'A Classic';
I get this error:Msg 9844, Level 16, State 4, Line 24 The char/varchar input type uses an unsupported collation. Only a UTF8 collation is supported with char/varchar input type in UNISTR function.What is the easiest way to fix this error? See possible answers