The data archive views make use of the SqlServerRegexFunctions assembly to replace some text. This requires installing the assembly in the database which has to be done separately from the EF migration/deployment process. It would be nice if there was only one deployment process, if only because the database is constantly rebuilt when debugging locally.
Because of this, it's worth considering whether the text replacement functionality should be performed in the C# code rather than in the SQL code.
Pros of leaving the regex replace in SQL
The problem is already solved (no extra work)
Pros of moving the regex replace to C#
Simplifies local debugging
SQL version ties the code to a specific DB implementation
SQL assembly may hinder moving the application to a serverless deployment strategy
In either case, performance should be compared and taken into account.
The data archive views make use of the SqlServerRegexFunctions assembly to replace some text. This requires installing the assembly in the database which has to be done separately from the EF migration/deployment process. It would be nice if there was only one deployment process, if only because the database is constantly rebuilt when debugging locally.
Because of this, it's worth considering whether the text replacement functionality should be performed in the C# code rather than in the SQL code.
Pros of leaving the regex replace in SQL
Pros of moving the regex replace to C#
In either case, performance should be compared and taken into account.