Dealing with large databases?

Has anyone else had Inventory crash on them? We attempted to use it for a couple months, but usually half-way through a requisition it would crash, thus forcing us to (a) unlock the requisition from an admin SW21 account, then delete it, then (b) restart the requisition.

Of course it only crashed with LARGE requisitions. :)

We found it easier just to print off the req from SW21, fulfill it, then return to sw21 and type in what was done.

Have you guys made any improvements to the way this is handled, within the past couple years?

Also, the ability to bypass going through your server would be sweet. We have a huge database and wifi everywhere. If we could connect straight to our server without going through yours, the connections would stay in-house and be much faster, or so I think.

▶ Reply to This

Replies to This Discussion

Permalink Reply by Jeffrey Hensel on April 11, 2011 at 1:26pm

Nathan,

I will pass this along and see if anyone here has any idea why it's crashing. I am unsure if the 2nd thing is possible due to SW21 restrictions but will mention it. Thank you!

▶ Reply

Permalink Reply by Nathan Sutherland on April 11, 2011 at 1:42pm

Thanks for passing this along Jeff.

Here's some additional info if it helps:

Our inventory database currently has over 2500 inventory unique parts, over 300 inventory tools (tools we charge out per time), and over 2,400 non-stock parts.

Our main warehouseh as over 3,400 bins, and we have 4 vehicles with over 1,100 bins each, as well as several styles of templates with 1100 bins each.

▶ Reply

Permalink Reply by Ryan McNamee on April 11, 2011 at 1:56pm

Hi Nate,

Make sure in your Mobile Inventory settings scree, that your Timeout is set to "-1". This tells the application do not stop making a web service request, no matter how long it may take. Large updates to SW21 make require some time to send across. Roughly how many items are you adding to the requisitions?

▶ Reply

Permalink Reply by Nathan Sutherland on April 11, 2011 at 2:31pm

On large jobs, about 400 (these freeze). A few are around 100 (also freeze), but most are around 20 (don't freeze).

▶ Reply

Permalink Reply by Steve Kiernan II on July 12, 2011 at 12:07pm

Hi Nate,

Did adjusting the timeout as Ryan suggested help?

▶ Reply

Permalink Reply by Nathan Sutherland on July 12, 2011 at 12:43pm

Thanks for the follow up. I haven't had the chance to test it yet (huge bids flying around), but I'll give it a shot soon.