使用 DBGhost 处理大型静态数据表
我们正在考虑使用 DBGhost 重组我们的数据库开发和部署流程，我们希望摆脱中央开发数据库并将数据库引入源代码控制。
我们遇到的问题之一是一个包含静态数据（包含翻译的语言字符串）的大表，它有接近 200K 行。
我知道我们最好的解决方案是将这些内容移至资源文件中，但在我们实现这一点之前，DbGhost 是否能够在短时间内维护所有这些静态数据并生成我们的开发和部署数据库？如果没有，是否有一个好的替代方案可以在我们需要时填写此表？
We are thinking of restructuring our database development and deployment processes by using DBGhost, we want to move away from the central development database and bring the database to the source control.
One of the problems we have is a big table with static data (containing translated language strings), it has close to 200K rows.
I know that our best solution is to move these stings into resource files, but until we implement that, will DbGhost be able to maintain all this static data and generate our development and deployment databases in a short time? And if not is there a good alternative to filling up this table whenever we need to?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
这是一个较旧的问题，有一个公认的答案，但我对此有一些不同的意见。
我们使用DBGhost，我们有大量的静态表数据，尽管最大的只有大约20K行，而不是200K行。
DBGhost 具有编写数据脚本的功能（作为一系列插入语句）。我们用它来将静态数据导出到脚本中，并将这些脚本置于版本控制之下。我们调整了这些脚本以在将数据添加回之前清除数据，因此我们可以使用单个脚本来“重置”表的静态数据。此添加是为了满足我们的特定需求，并不是使用 DBGhost 处理静态数据的唯一方法。
“从脚本构建”和“同步”进程都支持在进程之前和之后运行临时脚本。我们将静态数据脚本添加为临时脚本，以便在构建/同步后运行。
DBGhost在同步过程中还支持数据同步。同步过程可以配置为对选定的表进行数据同步。使用这种技术，您可以让构建过程通过脚本添加数据，然后同步过程可以自动同步这些表的数据。使用这种技术，您不需要像我们一样更改脚本。
This is an older question with an accepted answer, but I have some different input into this.
We use DBGhost and we have lots of static table data, although the largest is only about 20K rows, rather than 200K rows.
DBGhost has a feature to script data (as a series of insert statements). We used that to export our static data into scripts and put those scripts under version control. We tweaked those scripts to clear the data before adding the data back in, so we can use a single script to "reset" the static data for a table. This addition was for our specific needs, and is not the only way that you could handle static data with DBGhost.
The "build from scripts" and "sync" processes both support runnning ad-hoc scripts before and after the process. We added the static data scripts as ad-hoc scripts to run after the build/sync.
DBGhost also supports data synchronization in the synchronization process. The sync process can be configured to do a data synchronization on selected tables. Using this technique, you can have your build process add the data via the scripts, then the sync process can automatically sync the data for those tables. Using this technique, you would not need to change the scripts like we did.
您能看一下 SQL 源代码管理吗？我们刚刚添加了静态数据支持，并正在完整发布之前寻求反馈。
http://www.red-gate.com/MessageBoard/viewtopic.php ?t=12298
您能解释一下为什么要放弃中央数据库开发模型吗？
Would you be able to take a look at SQL Source Control? We've just added static data support and are looking for feedback prior to the full release.
http://www.red-gate.com/MessageBoard/viewtopic.php?t=12298
Would you be able to explain why you're moving away from a central database development model?
这是来自 Innovartis 的一封电子邮件，涉及与您相同的问题。不过你现在可能已经发现了这一点！
That's from an email received from Innovartis regarding the same question as yours. You've probably found this out by now though!
也许当你问这个问题时他们没有做出评估，尽管我不确定这是真的。您知道的唯一方法就是测试它并看看它是如何工作的。
http://www.innovartis.co.uk/evaluation.aspx
Maybe when you asked this they didn't have an evaluation though I'm not sure that is true. The only way you will know is to test it and see how it works.
http://www.innovartis.co.uk/evaluation.aspx