为什么SSM v18.11.1导入向导截断小数?
为什么SSMS V18.11.1截断为浮子的截短小数?
此屏幕截图显示从选项卡划界文本文件导入的值中有小数点。 在从选项卡划分的文本导入的值中的小数
此屏幕截图显示小数是在表中截断的 此屏幕截图表明,在SQL Server Import Process中将小数截断了
除了浮子以外,我还可以使用其他数据类型以防止小数被截断吗?
Why does SSMS v18.11.1 truncate decimals that are read in as a float?
This screenshot shows that there are decimals in the values imported from a tab delimited text file. decimals in the values imported from a tab delimited text
This screenshot shows that the decimals were truncated in the table
This screenshot shows that the decimals were truncated in the SQL Server Import process
Is there another datatype I can use besides float to keep the decimals from getting truncated?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
确保将数据类型设置为“选择数据源”对话框的“高级”选项卡中,并确保目标列是列映射窗口中的浮点(如果表格是新的)
Make sure the Data Type is set to float in the Advanced tab of the Choose a Data Source dialog box and also make sure the destination column is a Float in the Column Mappings window (if the table is new)
您是否尝试过数字数据类型值?这说它的精度为18,我认为过去我用它是在小数点之后的浮子上删除值。
Have you tried the numeric data type value? that says it has a precision of 18, I think I used that in the past as float was removing values after the decimal point.