Sitemap using URL_ALIASes gets too big for SQL?

TS 7.1001 w LiveSite on Windows

Hi I have a fairly large Sitemap in SitePublisher. I'm only using the Primary node, which has several subtrees, called e.g. "mainmenu", "footermenu", "helperaliases". I have a main menu component which only displays elements in the mainmenu tree, a footer navigation which only displays elements from the footermenu tree, and the helperaliases contains anything else that is needed.

I have successfully updated my mainmenu and footermenu subtrees to have one URL_ALIAS each, but occasionally submitting the changes (dev or prod) would break TeamSite completely, resulting in not being able to submit anything afterwards until the system is restarted. I traced the problem to a "binary data would be truncated" SQL error (MSSQL 2005). I am not able to add aliases to all my elements without getting this error. All my aliases are unique.

Anyone have an idea what is going wrong here? Is there a solution/workaround/bug to avoid? Somebody suggested that it is possible to edit the default.sitemap directly, after publishing, to add the required aliases but i don't like the sound of that and it defeats the point of managing it through the SiteMap tab.

Find more posts tagged with

Comments

miroperez

Where do you see this error? We don't deploy the sitemap to a db it gets sent over opendeploy during the submit as a file.

Crsb

What do you mean by "completely breaks TS"? can you post the error you see?

Content in the file doesn't impact the DB since only EAs gets deployment to the DB, and there is a known issue with 7.1 concerning MSSQL DB and EAs length (resolved in 7.2):

2. RTR-1438 Resolved the database EA table column length issue.
The database schema of EA table for MSSQL server is designed as varbinary(4096), which limits the EA length from 0 to 4096. LSCS code doesn't truncate any EA before storing it into database. To solve the problem, user needs to manually update the database schema for the length of varbinary for EA table (Note, for MSSQL server, the definable maximum length is 8000) by using Microsoft SQL Server Management Studio or other similar tool. If you expect a longer length than 8000, update schema as varbinary(max).

Binettoid

Thanks for your responses.
I see the error I mentioned about data being truncated.
Any subsequent submission of files stalls and nothing can be submitted until several services are restarted or we reboot the server.
CSRB your reference to RTR-1438 seems to have solved this issue for us.
No idea why the EA for this should grow so large but there ya go it works now.
Thank you!