Win 2k, w/ access and a dot matrix printer.

Omg not the way I'd like to go out.

Glad its U, not me.

Cursor in a 700 line trigger.

OMG, that is not the way I'd like to go out!

In a stateless application (Using IE etc) You cannot implictly lock rows, it will hold rows locked until you release them, which is all good except what if the admin...

Well Without specifically telling you whats wrong with your trigger, you need to understand that triggers should be written to handle record sets.

select  @ControlID = i.ControlId,

 @EntityID = x.entityID,

 @TimePeriodID = x.TimePeriodID,

 @Response...

hth

Even with recompile you can suffer the same result from parameter sniffing.

in your procedure reassign in parameters to a new parameter, and use the new parameter in the query.

also dbcc...

Sql stores date times as 2 different numbers, but it is the responsibility of the presentation layer to display the date/time formatted. I don't know why, but enterprise manager doesn't...

You have it mixed up.

SELECT [Name], value

FROM OPENXML (@idoc, N'/policy/DesktopProperties/AgentParameters',1)

 WITH ([Name] varchar(20),

       [Value] varchar(50))

<AgentParameters Name="pamver" Value="7.0.14"/>

your xml consists of an element of AgentParameters,

with attributes Name, and Value.

query up...

It is probably a permissions issue.

In the sql server agent, who is the job set to run as?

if its sa, then you'll have issues because sa does not have rights...

How are you looking at this data?

if your using enterprise manager, I'm not surprised.

use query analyzer instead.

I think thats the only way you can do it.

Developer edition is functionally equivelent to Enterprise edition.

while Standard edition has some functionality disabled, such as replication, and log shipping.

The install...

100 ms is a very low requirement, I'm not sure you can get that low unless you go thru some very expensive hardware level database mirroring.

or some 2 phase commit...

There's something funk about your xml string.

When I remove the bolded section it works fine. (the xmlns Attribute)

Oh by the way, don't forget the   exec sp_xml_removedocument @idoc

DECLARE @RetVal int, @Doc varchar(8000), @iDoc...

Your destination table has a primary key.

Your trying to insert either duplicate rows into the table, or the primary key of one of the rows your trying to insert already...

Thread along the same lines.

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=61&messageid=970

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=61&messageid=6371

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=23&messageid=110059

there's a ton of articles and posts about this. Try the search.