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 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 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 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?|||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:
> 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 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,
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:
> 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:
> > 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 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?|||I would like help Rocky... how do we arrange? You can find my email address
at www.ingmancompany.com.
jeff
"Rocky A" 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, 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:
> > 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:
> >
> > > 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 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?sql

Defining an event inside of an assembly => UNSAFE (no workarounds?)

Can someone verify that an assembly containing an interface with an event definition, such as...

public interface A {
event EventHandler Foo;
}

... can never be loaded under SAFE or EXTERNAL_ACCESS ?

It appears that the compiler-generated add_xxx and remove_xxx have the MethodImpl(MethodImplOptions.Synchronized) attribute defined by default, and "Explicit synchronization is not allowed". The same limitation also applies to classes by default, although technically one is able to define the implementation directly (clearly not ideal).

That's exactly correct. There is some possibility in the future that the CLR could change the way they implement EventHandler synchronization to allow it in non-unsafe assemblies, but for now that is the restricition.

Steven

Default Record IDs

There has to be somehow the SQL server uniquely identify each record in a db.

I am developing a web app to interface with an MsSQL Server. But in order to delete and update records I need to uniquely identify each record. I know you can do this with int IDENTITY columns, but not every DB table has a int IDENTITY column, so, what I am asking is, is there anyplace where I can query to find out an ID or something of the sort for a record in a db.

ThanksNo, records have no inherant or permanent ID in SQL server unless the database designer specifies one, either through a surrogate key or a natural unique key.

For example, a table with no primary key is called a "heap", and new SQL developers frequently make the mistake of assuming that the data in a heap is in a reliable, predicatable, and fixed order. It is not. While data is appended to a heap in the order it is inserted, the order can be shuffled over time by updates to the table, which cause rewrites to portions and thus change their location.

A well designed database will have a unique way of identifying each record. If the database you are working with does not have one, then you will need to add either an autoincrement field or a GUID field to each table. Autoincrements are integers and thus take up less space and sort/search very quickly. GUIDs have the advantage of being unique not just within a table, but across the entire database and even between databases.

blindman|||If your table has no primary key,unique constraint... then your entire table could have identical records. So unless your table was created with the proper constraints, you have no way of knowing. As already mentioned, if no unique identifier exists you can create one - but you still have to decide which data is valid and which you can delete - but in your case if you have identical information how are you distinguishing now ?