Inner join xtra_itemmaster I on dbo.dataSKU(I.SKUlite) = Pcart.SKUlite
Inner join xtra_icecat_allproducts Pcart on R.prodID2 = Pcart.product_id Isnull(PO.dateForced, '') as nameApprovalDate Max(M.lastIceCatFetch) as latestProductSheetFetch, Max(M.lastUpdated) as mostRecentProductEdit, Max(M.dateCreated) as newestProductCreated, ISNULL(PO.forceName,Pprin.model_name) as approvedPrinterName,
RTRIM(ISNULL(ECAT.category,'NOCAT')) + '///' + RTRIM(ISNULL(SubCat.category, 'NOSUBCAT')) + '///' AS catPath, Or perhaps the script needs to be recoded using a different approach?Īny help greatly appreciated! select DISTINCTĭbo.deduceMFRfromSubCatName(subcat.category) as MFRdeduced, Would I be right in thinking that this can be tackled by adding indexes? If so how should I go about it? My knowledge of SQL Server is patchy, especially after several years of non-involvement. My hunch is that the query involves an exponential increase in CPU cycles as the table sizes increase, and that we've now hit a critical point in size.
#Icecat wont run windows code
Unfortunately the project was so long ago that I have very little idea about what is going on in the code even though I created it myself! The database tables involved are pretty large, but have only been very slowly increasing in size over the years and the code has always worked pretty quickly right up until recently. (BTW i'm aware of the single-core limitation of SQLEXPRESS, but that's what we are having to use) We have moved to a faster server with more RAM and the latest version of SQPEXPRESS (.0) but this has not fixed the problem. In the past it would have run fine in just a few seconds.ĭuring the query the CPU maxes out, but RAM usage stays reasonable. When I run the SP directly in SSMS it just doesn't terminate, I left it running for 90 minutes and it neither timed out nor completed. Many years ago I coded a stored procedure containing the following SQL (for a client's backend website) and it has always worked fine for them right up until a few days ago when it started to fail with a timeout message.
0 kommentar(er)
