使用列级 WHERE 子句更新多个列中的所有 SQL NULL 值?
我们有一个包含大量宽表(每个表 40-80 列)的数据库,并且刚刚发现一个错误,该错误将 NULL 值引入到大约 500 条记录中。 NULL 值可以出现在任何列中(所有列都是整数列,请参见下图),但这些 NULL 值会导致我们的报告系统之一出现无法轻松更改的问题。我们需要将 NULL 值替换为特定的静态值(在本例中为 99),但由于必须针对超过 250 个不同的列逐列进行此更改,因此我宁愿不编写单独的 TSQL 脚本来更新每一列一个。
我的大脑现在太混乱了,无法想出一个聪明的解决方案,所以我的问题是如何使用简单且可读的 SQL 查询对表(或者更好的是多个表)上的所有列执行此任务。我可以使用一系列 WHERE (Answer_1 IS NULL) OR (Answer_2 IS NULL) OR ...
甚至每个表的 AdministrationID 编号来轻松隔离记录,但这个技巧不起作用更新时,where 子句是每行而不是每列。有什么建议吗?
下面是一个示例查询,显示了 4 个不同表中的一些记录:
We have a database with a bunch of wide tables (40-80 columns each) and just found a bug that introduced NULL values into about 500 of the records. The NULL values can appear in any of the columns (all are integer columns, see image below) but these NULL values are causing issues with one of our reporting systems that cannot be changed easily. We need to replace the NULL values with a specific static value (in this case 99), but since this change has to be made on a per-column basis for over 250 different columns I would rather not write individual TSQL scripts updating each column one by one.
My brain is too fried right now to think up a clever solution, so my question is how can I perform this task on all columns on a table (or better yet multiple tables) using a simple and readable SQL query. I can isolate the records easy enough using a chain of WHERE (Answer_1 IS NULL) OR (Answer_2 IS NULL) OR ...
or even by AdministrationID numbers for each table, but this trick won't work when updating as where clause is per row not per column. Any advice?
Here is a sample query showing a few of the records from 4 different tables:
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(4)
对此没有任何约定 - 如果您只想处理相应列为 NULL 的记录,则需要使用:
但您可以在 UPDATE 语句中使用它:
逻辑是该值将仅更新为 99如果列值为 NULL,则由于 COALESCE 的工作原理 - 返回第一个非 NULL 值(处理从左到右提供的列表)。
There isn't any convention to this -- if you want to only process records where respective columns are NULL, you need to use:
But you could use this in the UPDATE statement:
The logic is that the value will be updated to 99 only if the column value is NULL, because of how COALESCE works--returning the first non-NULL value (processing the list provided from left to right).
只需轮询每个表的 sys.columns 表并创建一些动态 sql...这是蛮力,但它使您不必写出所有 t-sql。
例如:
Just poll the sys.columns table for each table and create some dynamic sql... It's brute force but it saves you from having to write all the t-sql out.
For example:
由于您必须在各处执行此操作,因此我编写了一些 javascript 来帮助您构建 sql。将其剪切并粘贴到浏览器地址栏中以获取 sql。
Since you have to do this all over the place i wrote some javascript to help you build the sql. cut and paste this into your browsers address bar to get your sql.
我不喜欢为了报告的目的而操纵数据本身的想法。如果您将 NULL 值更改为 99 只是为了使报告更容易,那么我认为该数据已损坏。如果除了报告之外还有其他消费者需要真实数据怎么办?
我宁愿为报告编写一个智能查询。例如,如果使用 ISNULL(columnname, 99),则只要列值为 NULL,它就会返回 99。
I don't like the idea to manipulate the data itself for the purpose of reporting. If you change the NULL values to 99 to just to make your reporting easier then the I consider that data as corrupted. What if there are other consumer apart from reporting which need genuine data?
I would rather write an intelligent query for the report. For example, if you use ISNULL(columnname, 99), it would return 99 whenever the column value is NULL.