Delayed stored procedure

We have a SQL Server 2000 database on my PC running WinXP Pro with a GUI
interface/application provided by a third party. We're recruiters and this i
s
the “Applicant Tracking System”/database we use to track our
candidates/resumes and clients.
This software was installed on my machine by others and I do not have the
technical expertise to diagnose problems when they occur.
There is a button within the application we click to search the (indexed)
resumes based on keywords.
Apparently this button runs a stored command thru SQL Server:
sp_help_fultext_columns 'consultants"
It used to be that when we clicked on the button a window (GUI) would open
instantly with fields where we enter our key words and then execute the
search.
However… for unknown reasons it now takes approximately 40 seconds after w
e
click for the search window to open. Our software provider does not know why
.
They logged on to my machine today and used Enterprise Manager and I think
Query Analyzer to run the query above. It also took 40 seconds to open and
they said this indicated we have a problem with SQL Server... not their
application... and sent us off to find our own solution.
We live in the country and there are no SQL Server experts within miles.
Does this sound like a problem that could be diagnosed/fixed by someone who
accesses my machine remotely?
Or better yet... does anyone have a clue how to fix the problem simply based
on my question above?Jeff,
If somebody can remote desktop in , they should be able to identify
the issue.
I don't want to sound presumptous but I somehow find it hard to believe that
just sp_help_fultext_columns 'consultants' is taking 40 seconds. This system
stored proc only brings back a list of columns that have full text index on
them in a particular table(or table-column),
If you can run trace and make sure that is the only thing running in the
backend when you click that button, that might help you narrow it down a
little more.
To run a trace just click sql profiler from the Sql server program menu and
click File-New Trace & Hit run. go back and click the Button on the
Application. and see the list of sql commands being executed as a result.
HTH,
RA
"Jeff Ingman" wrote:

> We have a SQL Server 2000 database on my PC running WinXP Pro with a GUI
> interface/application provided by a third party. We're recruiters and this
is
> the “Applicant Tracking System”/database we use to track our
> candidates/resumes and clients.
> This software was installed on my machine by others and I do not have the
> technical expertise to diagnose problems when they occur.
> There is a button within the application we click to search the (indexed)
> resumes based on keywords.
> Apparently this button runs a stored command thru SQL Server:
> sp_help_fultext_columns 'consultants"
> It used to be that when we clicked on the button a window (GUI) would open
> instantly with fields where we enter our key words and then execute the
> search.
> However… for unknown reasons it now takes approximately 40 seconds after
we
> click for the search window to open. Our software provider does not know w
hy.
> They logged on to my machine today and used Enterprise Manager and I think
> Query Analyzer to run the query above. It also took 40 seconds to open and
> they said this indicated we have a problem with SQL Server... not their
> application... and sent us off to find our own solution.
> We live in the country and there are no SQL Server experts within miles.
> Does this sound like a problem that could be diagnosed/fixed by someone wh
o
> accesses my machine remotely?
> Or better yet... does anyone have a clue how to fix the problem simply bas
ed
> on my question above?|||Rocky...
Thanks for your comments. But I'm not confident enough in my SQL expertise
to understand/follow thru on your recommendations.
(One small point... I mispelled the query in my original post... it should
be "fulltext" not "fultext").
I think I'll need to find a DBA who can logon to my machine remotely to
diagnose this.
I'd have done this by now except we only access this command a couple times
daily and I haven't wanted to hire an expensive consultant.
Would Microsoft paid incident support be a good route to go?
........................
"Rocky A" wrote:
[vbcol=seagreen]
> Jeff,
> If somebody can remote desktop in , they should be able to identify
> the issue.
> I don't want to sound presumptous but I somehow find it hard to believe th
at
> just sp_help_fultext_columns 'consultants' is taking 40 seconds. This syst
em
> stored proc only brings back a list of columns that have full text index o
n
> them in a particular table(or table-column),
> If you can run trace and make sure that is the only thing running in the
> backend when you click that button, that might help you narrow it down a
> little more.
> To run a trace just click sql profiler from the Sql server program menu an
d
> click File-New Trace & Hit run. go back and click the Button on the
> Application. and see the list of sql commands being executed as a result.
> HTH,
> RA
> "Jeff Ingman" wrote:
>|||Jeff,
I would suggest going through a consultant rather than a MS paid
incident, I am guessing this is not an issue with Sql server as a product, i
t
is more of a day-to-day technical issue, i would go the DBA route. I can
take a look at it if you are interested.
thanks,
RA
"Jeff Ingman" wrote:
[vbcol=seagreen]
> Rocky...
> Thanks for your comments. But I'm not confident enough in my SQL expertise
> to understand/follow thru on your recommendations.
> (One small point... I mispelled the query in my original post... it should
> be "fulltext" not "fultext").
> I think I'll need to find a DBA who can logon to my machine remotely to
> diagnose this.
> I'd have done this by now except we only access this command a couple time
s
> daily and I haven't wanted to hire an expensive consultant.
> Would Microsoft paid incident support be a good route to go?
> ........................
> "Rocky A" wrote:
>|||I would like help Rocky... how do we arrange? You can find my email address
at www.ingmancompany.com.
jeff
"Rocky A" wrote:
[vbcol=seagreen]
> Jeff,
> I would suggest going through a consultant rather than a MS paid
> incident, I am guessing this is not an issue with Sql server as a product,
it
> is more of a day-to-day technical issue, i would go the DBA route. I can
> take a look at it if you are interested.
> thanks,
> RA
> "Jeff Ingman" wrote:
>