Lock Request - SQL Timeouts
Hi,
We have done a number of SF projects for clients and are testing out the e-commerce functionality for a new client. In testing I have loaded about 100k products in the db using the API with another 200K more to go.
I am receiving lock timeouts though when trying to pull up products in the backend, under e-commerce. Is module capable of handling such (relatively) large product lists?
Hi,
We have uploaded 100k products using our API and have not encountered any SQL timeouts in the backend.
SQL timeouts could be attributed to your SQL configuration, location of your SQL server or your systems configuration.
Also if you encounter anymore issues, can you open a support ticket so we can better identify the problem you are encountering? Please let us know how many products, number of customers, number of orders and images per product you are trying to upload.
Kind regards,
Grace Hallwachs
the Telerik team
Are there any "known" limitations as far as numbers of products, images, customers or orders that we should be aware of?
Hi Victor
There are no limitations of any kind in Sitefinity Ecommerce that we know of. As Grace stated we are using around 100k to 130k products for testing and will soon be testing up to 500k. However, when you start to get into these high numbers, you need to make sure your servers (hardware) can handle the job. SQL Express is not a desired DB for these large numbers of products etc....as SQL Express only uses a single core from the processor and is considered a single threaded application. Thus SQL Server Standard or above is ideal for this volume of products, orders, pages etc... You may find performance issues if you are using SQL Express. For example if you are importing products into Sitefinity, and at the same time you are logged into the Sitefinity back-end and trying to view products. This example could cause a SQL time out issue, but again only if you are using SQL Express.
Hope this helps.
Kind regards,
Thank you. A few things I've learned that might of help. Always set the server.timeout to something high while doing big batches of inserts. If for any reason the process does time out, it possible to SQL Server to hold transaction open. This will pretty much lock up the entire database and not allow access to SF at all.