maximum records bootstrap Excel Data?

maximum records bootstrap Excel Data?



Is there a maximum number of records that can be bootstrapped at once with Excel Data?

Thanks in advance,


There's no specific limit for the platform.
You can however hit a timeout, if it takes too long to process / upload; if file size exceed a certain threshold, IIS may block it on upload; and even excel may have its own limitations.

Hello Paulo,

Thanks for your quick response. I guess you are right, we found out the hard way...(see part of logfile below, created after trying to bootstrap Excel Data file with over 700.000 records).
Does this mean there is no rule of thumb for bootstrapping Excel Data, and it comes down to trial and error?

Timer BootstrapAfvalkalenders error (inside action 'BootstrapAfvalkalenders'). Timer duration = 100 secs:Fatal error encountered during command execution. [retry 1 of 3 scheduled] 
Environment Information eSpaceVer: 1 (Id=143, PubId=138, CompiledWith=
RequestUrl: (Method: POST)
AppDomain: /LM/W3SVC/1/ROOT/Afvalkalender-102-130722630201754355
FilePath: C:\...\PS\running\Afvalkalender\
Locale: en-US
DateFormat: dd-MM-yyyy
PID: 3628 ('w3wp', Started='13/03/15 11:37:36 AM', Priv=2000Mb, Virt=18324Mb)
TID: 87
Thread Name: 
.NET: 4.0.30319.34209 
MySql.Data.MySqlClient.MySqlException (0x80004005): Fatal error encountered during command execution. ---> System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   --- End of inner exception stack trace ---
   at MySql.Data.Common.MyNetworkStream.HandleOrRethrowException(Exception e)
   at MySql.Data.Common.MyNetworkStream.Write(Byte[] buffer, Int32 offset, Int32 count)
   at MySql.Data.MySqlClient.TimedStream.Write(Byte[] buffer, Int32 offset, Int32 count)
   at MySql.Data.MySqlClient.MySqlStream.SendPacket(MySqlPacket packet)
   at MySql.Data.MySqlClient.NativeDriver.ExecutePacket(MySqlPacket packetToExecute)
   at MySql.Data.MySqlClient.NativeDriver.SendQuery(MySqlPacket queryPacket)
   at MySql.Data.MySqlClient.Driver.SendQuery(MySqlPacket p)
   at MySql.Data.MySqlClient.Statement.ExecuteNext()
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteScalar()
   at OutSystems.HubEdition.Extensibility.Data.ExecutionService.BaseExecutionService.ExecuteScalar(IDbCommand cmd)
   at OutSystems.Internal.Db.Command.ExecuteScalar(String description, Boolean isApplication, Boolean skipLog, Boolean applyTransformationsToParameters)
   at ssAfvalkalender.ExtendedActions.CreateAfvalkalender(HeContext heContext, RCAfvalkalenderRecord inParamSource, Int32& outParamId)
   at ssAfvalkalender.Actions.ActionBootstrapAfvalkalenders(HeContext heContext)
   at ssAfvalkalender.TimerBootstrapAfvalkalenders.Execute(HeContext heContext, Int32 timeout) 
I'm not sure if it's the issue here, but for processing a large number of data, the recommended approach is having your timer to work for a certain period of time, stop and waking itself again (Wake<Timer> action). The timer should be able to continue (on the next iteraction) working on the next unprocessed element.

Note that timers have a timeout (that you can override in Service Center, in your eSpace details) - default is 20 minutes - so you can work your data in chunks of time below 20 minutes.