In the install directory the is a file instmsdb.sql which defines sp_sqlagent_notify which calls xp_sqlagent_notify.

It uses a flag @error_flag which may help.

This looks definitely undocumented !!

Not sure if this is it but, your cursor should be declared STATIC since the underlying data is being modified during execution. STATIC ensures a buffered copy is used for...

This may help:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/SecNetHT05.asp

Sorry to be vague - no time to look it up again - but I found this was the issue when I had a similar problem.

You...

Only the in-house standards stop a user doing this (bypassing VSS and changing sprocs directly). We ask developers to check out of VSS to a local folder, edit and test...

Does Bruce Powell not realise that cursors are slow only when compared with set based SQL statements? They are probably quick compare with running the loop over a client recordset.

Also...

Tymberwyld has made good points. I too find sprocs excellent for the bread and butter stuff of loads and saves. (And the use of udfs on loads is a good...

One point that has not been mentioned (but is perhaps implied) is that the major performance gain of stored procedures is in Network I/O.

A well designed sproc may encapsulate 10...

As far as I know SQL server does not track table updates so you would need to use triggers to do that.

You can get table name info from sysobjects where...

I agree with all Patryks reasons for using a data access layer.

I also re-iterate rugha's comment - see the microsoft SqlHelper class which they publish separately as a freely downloadable...

I once had a similar problem and it was to do withthe scheduled job notification hanging - the job step itself completed but the agent process got hung on the...

You will need 2 SQL statements:

1. An UPDATE statement to cope with updating existing data - your statement in the first post in this thread looks OK I think.

2. An...

If you do

sp_help DT_Users

you will see a collation name such as SQL_Latin1_General_CP1_CI_AS

You can then use the syntax belowm, substituting the actual collation of your SQL Server data.

.....

WHERE sAMAccountName COLLATE SQL_Latin1_General_CP1_CS_AS...

You are right about the LDAP query. Somehow my cut and paste did not work.

An UPDATE statement cannot insert new rows into Sql Server.

You will need two statements: An UPDATE statement - you already have, and an INSERT statement.

The INSERT will use WHERE NOT...

I was looking for a way to do this when you dont have the source code for the application (i.e configuring a 3rd party application or a reporting tool).

Maybe I should...