Are there XML Application file size limits?

[raking08]

I have created a custom application that is content rich with many linked tables from SAP . The XML application extract used to move the application to another instance is about 30MB, 17k application files when moved with limited data. Is this a reasonable size to move via XML extract for the application update?

The import is hanging up during commitment at what looks like 99% based on the progress bar, but there is no way to tell if its still "thinking" or just locked up. After several hours I gave up and had the instance zbooted to start from a clean slate.

Any comments on the size and advise on the locking up would be welcome

[coryseering]

Hi raking08,

Wow, that's a HUGE update set. During my time in Support, I would always advise customers to keep update sets below 1000 records. There is a lot of processing going on when update sets are imported- especially when there are so many things which rely on other things in the set.

Keep your Update Sets small to avoid issues like this. About 1000 records is the max I have ever felt comfortable with.

[raking08]

hello Cory,

Keep in mind this is an xml extract of a complete application with standard content, rather than a normal incremental update between instances. Breaking it up into small chunks to move to a fresh new instance would be difficult.

I am hoping to add this to the store shortly, but I need to sort out the commitment issue of course.

One idea is to move only the reference tables' data and the move the content tables data in a second step.

I will post if that works. Meanwhile I am still hoping to learn what defines "large" application.

richard

[raking08]

Quick update on this issue.

Creating the full application extract ( as SN suggests to move data between different instances and what is required for new application on the store) is now seemingly fine. I was able to increase the record sizes in SYS_Properties.

The update set minus any data is about 8800 files. It gets created in about 3 minutes and extracts to XML as a single update set in about 3.5 minutes.   It loads to the new box fine except for minor errors in missing reference records and such.

The desire is to load with all the data as this is a dictionary application so content is key. Loading tables individually is possible , just a pain.

The Application with most ( not all) of the needed content is about 14.5k files (93 tables) after trimming out all the import set tables etc. .

The update set gets created in about 4 minutes and looks fine, but the xml extract runs and I get the OK by the top second counter at about 4 minutes. BUT THEN the screen goes white and I never have a chance to download the XML file. The XML Pop-up never pops.

I have set the maximum XML export to 500,000 lines specific to the application so that's a bit more than I need I think. Could that still be the limiting factor and if so would that cause the XML File Save POP-up to never POP UP?

[coryseering]

Hi raking08,

It looks like you're running into a timeout issue. You can try to increase the transaction timeout for UI Transactions:

https://wiki.servicenow.com/index.php?title=Transaction_Quotas

The load balancer that sits between you and the node you're interacting with will automatically kill open HTTP connections which don't have activity for 5 minutes, so you may not be able to increase this enough to finish your export. It is worth a try though.

If that doesn't work, you could break up your Update Set into multiple smaller sets, export those individually, and reassemble them afterwards. Alternatively, contact the Support team to request assistance in exporting this set.