Problem solved - but still not understood.

Changing all nvarchar to varchar, and responce time came down with a factor 10.000 - why?

Anyway, thanks for working on the problem.

Have tested the change to nvarchar, and are now back on 2 min.

ID is an Clustered, Primary Index

An SQL that gives the 2 min. wait was

UPDATE Persondata SET Fornavn='John Test" WHERE ID=370

I run the SQL from QA, but have also tried from...

Will look at your sugestions and return

The DDL looks:

CREATE TABLE [dbo].[Persondata] (

[ID] [int] IDENTITY (1, 1) NOT NULL ,

[Tid] [timestamp] NULL ,

[Fornavn] [nvarchar] (80) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,

....

) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]

GO

Using the Update:

UPDATE Persondata SET...

I am having the same problem, even when I am NOT using the Enterprise Manager.

But when I do, I get the "The entire resultset ..." messagage the first time.

When...