October 11, 2005 at 2:08 pm
Has anyone had issues with the SQL Turbo built in stored procedures having slow performance?
We are trying to page the top 2000 results. Here is the general query I am passing into the server:
declare @sql varchar(5000)
select @sql = '
SELECT top 2000 pl.id
FROM dbo.business (nolock)
JOIN dbo.listings l (nolock) on l.businessid = business.businessid
JOIN dbo.nearby n WITH (Nolock) on l.ZIPID = n.NearbyZIPID
WHERE {business_idx=$''STERILIZES''}
AND (n.zipid = 16814) '
exec tdbExecuteReturnPageL @sql, 3, 20
GO
The tables are business, listing (locations of a a business), and nearby (a list of local zipcodes). We have horrible response times when the number of users increases. Also, the results per page vary - sometimes we get all 20 for the page, other times, only 5 records are returned!
Is there any issue with the statement or how we are going about this?
Thanks,
Nick
October 12, 2005 at 2:15 pm
Yes, there are indexes on both.
The strange text is SQL Turbo related code - what they say to use - to find anything in the index that is like "sterilizes". I could have anything in the search word - right now I've hardcoded it.
tdbExecuteReturnPageL is the SQL Turbo provided stored procedure for returning paged results.
October 12, 2005 at 5:57 pm
Quest Software SQL Turbo is for full text searches. From Quest's website "SQL Turbo is a revolutionary new software tool which dramatically increases the speed of SQL Server's free text retrieval."
I would be nearly impossible for us to determine what is going on inside their stored procedures. You should contact the vendor for help.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply