Hi Paul, merging at project creation does what it is supposed to do I think but it doesn't seem to help address the performance issues we are having with groupshare which relates to numbers of files that can be published at anyone time. As mentioned this is something we are working with the SDL support team so my question is essentially in the context of a short/medium term workaround.

Anyway as an example if we try to publish 200 xml files into 20 languages the groupshare publish fails and the processing takes much longer, if I use the merging option at project creation the same issue remains but if I combine all the xml files together into a couple of larger xmls before loading the project the processing happens much more quickly and it loads on to groupshare with out any problems.

The issue I have is when I combine the xmls the reverse separation process isn't 100% reliable hence I wondered if there were any tools/apps that could combine a set of source sdlxliffs or something along those lines and then I might load these? Hence perhaps the reason the inbuilt merge option doesn't seem to help is potentially because it might be more of a virtual merge and perhaps the source files are not actually combined when the project is loaded? When I actually combine the xmls prior to creating the project they process fine and I can publish much larger projects to groupshare.

Any ideas much appreciated, processing files in small source/language sets has been proposed but is not a great solution for us hence I was looking at some alternatives.

Many thanks

Hi Kevin,

I spoke to the product team in the meantime and this is a known issue that is highly dependent on server performance and the type of files.  So we have examples where 5000 files works fine, and then we have seen some where only a few hundred could cause a problem.  There is a KB article on this problem.

So the current resolution may be one or more of the following:

1. the one I gave you by merging the files and recreating the project with the merged files.
2. reducing the number of files added at a time, so multiple projects
3. increase the SQL Server performance

Hope something helps here until we have a more permanent solution for this (no timelines yet...)

Regards

Paul