什么数据大小适合在 SQL Server 中存储 RFID 列？
我对整个 RFID 领域还是个新手。
我需要在数据库中存储 RFID 公关资产。 目前还没有决定哪个系统将满足该特定领域（或多个领域？），所以我现在只想留出一些空间。
Oracle 有整个“Identity”包，可以处理不同版本和类型的 RFID，但我还没有看到 SQL Server 的任何东西。
也许我把事情过于复杂化了，但我进行了广泛的搜索，但没有找到关于这样一个标签有多大的参考，或者即使它适合存储在一个字段中，或者是否需要多个字段。
那么，我应该有哪些列，它们的大小应该是多少？ nvarchar(10) 就足够了吗？ nvarchar(20)？
I'm new to the whole RFID arena.
I need to store an RFID pr asset in the database. No decision has yet been made on what system will feed that particular field (or fields?) so I just want to set aside some space right now.
Oracle has this whole "Identity" package that handles, amongst other things, the different versions and types of RFID, but I havn't seen anything for SQL server.
Perhaps I'm overcomplicating things, but I've searched wide but found no reference to how big such a tag is, or even if it is suitable for being stored in one field, or if you need multiple.
So, what columns should I have, and what should their sizes be?
Would nvarchar(10) suffice? nvarchar(20)?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
RFID 标签没有固定的数据大小。 事实上，它们可以存储几个字节到几千字节。 它们甚至可以通过在其中存储代码来侵入未受保护的系统。 因此，您应该像从其他地方收到的数据一样对待从他们那里收到的任何数据。
至于唯一的标识符，如果您在其不大于 UUID 的基础上进行分配，那么您应该没问题。
There is no fixed data size for RFID tags. In fact they can store from a few bytes to a few kilobytes. They can even be used to hack into an unprotected system by storing code within them. Thus you should treat any data that you receive from them with the same suspicion that you would do from elsewhere.
As for an identifier that is uniques then if you allocate on the basis of it being no larger than a UUID then you should be OK.
据了解，第一代RFID标签一般为128位，其中96位是唯一ID，其余的是校验和。 但我强烈怀疑新一代至少有 256 位，而且还会继续增长。 我绝不是专家，所以您可能想等待另一个答案:)
所以我会选择足够大小的 char 或 varchar，这应该很容易在以后扩展。
AFAIK the generation 1 RFID tags are generally 128 bits, where 96 bits are the unique ID and the rest is checksum. But I strongly suspect that newer generations are at least 256 bits and it will continue to grow. I'm by no means an expert, so you may want to wait for another answer:)
So I'd go with a char or varchar of sufficient size, which should be easy to scale later.
不幸的是，目前 RFID 世界的标准规定了各种有用的东西，但没有规定标签尺寸（这些标准往往是针对特定行业的，跟踪奶牛的能力可能无法很好地符合您的计划）。
我的建议是分配一些东西来容纳足够的测试数据（
nvarchar(10)应该没问题），然后在选择实际实现时适当调整其大小，此时供应商将能够给你这些信息。Unfortunately, the standards in the RFID world at the moment specify all sorts of useful things, but not the tag size (these standards tend to be industry-specific and the ability to track cows may not map that well to what you have planned).
My advice would be to allocate something to hold enough for test data (
nvarchar(10)should be fine) and then size it properly when you choose an actual implementation, at which point the vendor will be able to give you that information.RFID 标签没有固定的大小，但我相信目前（2011 年 1 月）2KB 是 HF 规范中的最大大小，这包括标签 ID、用户数据和制造商设置的标签运行所需的数据。
在 UHF 规范中，您拥有的不是唯一 ID，而是 EPC，如果标签解锁，则该 EPC 可以由阅读器编辑，这与 HF 中由制造商设置和锁定的唯一 ID 不同。
最后，您需要读取您使用的标签内存的数据布局。 制造商将提供您所需的技术文档，解释可用的内存地址，以及您所需的最大大小。
There is no set size for RFID tags, but I believe as it currently stands (Jan 2011) 2KB is the maximum size in HF specification, this includes the tag ID, user data and data set by the manufacturer required for the tag to function.
In the UHF specification, instead of unique IDs you have an EPC which is editable by a reader if the tag is unlocked, unlike unique IDs in HF which are set and locked by the manufacturer.
End of the day, you need to read the data layout for the memory of the tag your using. Manufactures will provide the technical document you need that explains the memory addresses available, and thus the max size you need.