简体   繁体   English

在SQL Server中快速,大量输入数据

[英]Fast, high volume data input in SQL Server

I'm currently in the preparatory phase for a project which will involve (amongst other things) writing lots of data to a database, very fast (ie images (and associated meta-data) from 6 cameras, recording 40+ times a second). 我目前正处于一个项目的准备阶段,该项目将涉及(除其他事项外)非常快速地将大量数据写入数据库(即,来自6台摄像机的图像(和相关的元数据),每秒记录40多次) 。

Searching around the web, it seems that 'Big Data' more often applies to a higher rate, but smaller 'bits' (ie market data). 在网上搜索时,似乎“大数据”通常适用于更高的费率,但适用于“位”较小的数据(即市场数据)。

So.. 所以..

  • Is there a more scientific way to proceed than "try it and see what happens"? 是否有比“尝试一下然后看会发生什么”更科学的方法?
  • Is "just throw hardware at it" the best approach? “随便扔硬件”是最好的方法吗?
  • Is there some technology/white papers/search term that I ought to check out? 我应该检查一些技术/白皮书/搜索词吗?
  • Is there a compelling reason to consider some other database (or just saving to disk)? 是否有充分的理由考虑使用其他数据库(或仅保存到磁盘)?

Sorry, this is a fairly open-ended question (maybe better for Programmers?) 抱歉,这是一个开放式的问题(对于程序员来说可能更好吗?)

Is there a more scientific way to proceed than "try it and see what happens"? 是否有比“尝试一下然后看会发生什么”更科学的方法?

No, given your requirements are very unusual. 不,因为您的要求非常不寻常。

Is "just throw hardware at it" the best approach? “随便扔硬件”是最好的方法吗?

No, but at some point it is the only approach. 不可以,但是在某些时候这是唯一的方法。 You wont get a 400 horse power racing engine just by tuning a fiat panda. 仅通过调整菲亚特熊猫,您将不会获得400马力的赛车引擎。 You wont get high throughput at any database without appropriate hardware. 没有适当的硬件,您将无法在任何数据库上获得高吞吐量。

Is there some technology/white papers/search term that I ought to check out? 我应该检查一些技术/白皮书/搜索词吗?

Not a valid question in the context of the question - you ask specifically for sql server. 在问题的上下文中不是有效的问题-您专门针对sql server。

Is there a compelling reason to consider some other database (or just saving to disk)? 是否有充分的理由考虑使用其他数据库(或仅保存到磁盘)?

No. As long as you stick relational database the same rules apply pretty much - another may be faster, but not by a wide margin. 不会。只要您坚持使用关系数据库,相同的规则就会应用很多-另一个规则可能会更快,但幅度不会很大。

Your main problem will be disc IO and network bandwidth, depending on size of the images. 您的主要问题将是光盘IO和网络带宽,具体取决于映像的大小。 Properly size the equipment and you should be fine. 适当调整设备的大小,您应该没事。 At the end this seems less than 300 images per second. 最终,这似乎少于每秒300张图像。 Sure you want the images themselves in the database? 确定要在数据库中存储图像吗? I normally like that, but this is like storing a movie in pictures and that may be stretching it. 我通常喜欢这样,但这就像将电影存储在图片中,并且可能会拉伸它。

Whatever you do, that is a lot of disc IO and size, so - hardware is the only way to go if you need IOPS etc. 无论您做什么,都会有大量的磁盘IO和大小,因此-如果需要IOPS等,硬件是唯一的选择。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM