dribbling memory?

guopan has asked for the wisdom of the Perl Monks concerning the following question:

I am tasked with using
Text-Metaphone,
Text-Levenshtein,
String-KeyboardDistance, and
String-Similarity
to work with data in SQL-Server. (sniffle)

I've set up one active x package for each of the functions. All 3 packages use ADO to get data from the source table, perform the necessary functions, then write the results to the same table. Works fine except . . .

the packages runs slower and slower until I get an 'internal error' on the last one (similarity). If I close out of the DTS package and SQL server manager, then re-open and run the last (failing step), it works fine. By this behavior I am guessing that some memory leak (or stuff up?) is occurring.

Any thoughts on this would be very much appreciated.

Pamela

Comment on dribbling memory?

Replies are listed 'Best First'.
Re: dribbling memory? by dws (Chancellor) on Aug 27, 2002 at 16:54 UTC
Any thoughts on this would be very much appreciated. If what you mean by "active x package" is a Perl module that uses OLE/ADO to talk to SQL server (reading data, applying an algorithm, and writing data), then you can divide the problem up into pieces, and examine each for performance issues. Think isolation. Run one of the packages repetitively, examining for slowdowns. Then move on to the next. When you can provide a better characterization of the problem, post details and a small code sample that demonstrates the problem.	[reply]

Replies are listed 'Best First'.

Re: dribbling memory?
by dws (Chancellor) on Aug 27, 2002 at 16:54 UTC

Any thoughts on this would be very much appreciated.

If what you mean by "active x package" is a Perl module that uses OLE/ADO to talk to SQL server (reading data, applying an algorithm, and writing data), then you can divide the problem up into pieces, and examine each for performance issues. Think isolation. Run one of the packages repetitively, examining for slowdowns. Then move on to the next. When you can provide a better characterization of the problem, post details and a small code sample that demonstrates the problem.

[reply]