Hi NG

Im writing a web-interface that enables the user to update a DB. The
(non)queries takes heaps of time, and since my page "waits" for the query to
finish, wich is a pain. So basically I was wondering if there is kinda a
"update mytable set myrow=... LATER" kinda keyword or something, to make the
query execute whenever the sqlserver feels like it, but return "ok" right
away.

- Kasper

Show quote Hide quote As far as I know, there is no direct way of doing this.

One thing comes to mind...   Have a simple table where you can drop the
information quickly.   A SQL Server job can come along and check the table
every few minutes and then perform the work.

There are some caveats however.  What if the data is bad, or SQL Server has
an error attempting to process the data.  You have already told the web-user
that everything is ok, but in reality it is not.   How do you notify the
user that there were problems.

You may need to do some architecturual work to get this to work the way you
want it to.


Rick Sawtell
MCT, MCSD, MCDBA

Implement the sql update as a stored procedure. If you are using an ADO /
ADO.NET connection, then look executing the SP asynchronously. The SP can
send an email notification back to the user when it completes.

Show quoteHide quote

Service Broker queue(s) come to mind.  Need 2005 however or come up with
your own queue table.

Show quoteHide quote

Audit trigger with dynamic SQL and Cursor - Am I close?
Is Cursor Best Way To Go?
Mirrored Records?
Question concerning decimal datatype
UPDATE table FROM same table
Problem with WHERE clause
Backing up tr.log on another server
SELECT DATETIME PROBLEM???
sql qusetion 3
testking question