还有另一种方法来“导入”目录 [英] Is there another way to "import" a catalog

查看:89
本文介绍了还有另一种方法来“导入”目录的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述


我的目录是4Gb(xml格式)。目录数据来自传统(大型机)系统。目录管理器中不直接对目录进行更新/更改。所有更改都在遗留系统中完成。


我在遗留系统中订阅目录更改时遇到问题,所以我唯一的选择是定期更换整个目录。使用Catalog Manager Import大约需要6个小时。这不好,因为我们不能让这个网站长久下来。 I
需要另一种方式。


一种解决方案可能是在另一台SQL Server中导入目录,完成时只需将数据库复制到生产环境。不幸的是,我不能这样做,因为我有服务器其他目录由客户更新(他们改变价格等)。


我还有另一种方法来替换整个4Gb目录吗? Commerce Server是FAST?


TR

解决方案

您的意思是说差异目录文件大小是4GB?如果您每次都导入整个日期,那么您的approch不正确。


您是否考虑过利用登台服务器的选项以及导入登台服务器时是否可以仅利用导入增量更改?


Hi,

I have a catalog that is 4Gb (in xml format). The catalog data comes from a legacy (Mainframe) system. No updates/changes to the catalog are done directly in Catalog Manager. All changes are done in the legacy system.

I have problems to subscribe to the catalog changes in the legacy system so my only otion is to replace the whole catalog at regular times. This takes about 6 hours using Catalog Manager Import. This not good since we cant have the site down this long. I need another way.

One solution could be to import the catalog in another SQL Server and when done just copy the database to production. Unfortunatly I can't do that either since I have server other catalogs that are updated by customers (they change prices etc).

Is there another way for me to replace a whole 4Gb catalog in Commerce Server that is FAST?


TR

解决方案

Do you mean to say that differential catalog file size is 4 GB? If you are importing entire date everytime then you approch is not correct.

Did you think of options of leveraging staging server and while import to staging server can you leverage importing incremental changes only?


这篇关于还有另一种方法来“导入”目录的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆