Why not using SQL Server job scheduling? That is the only method built into
SQL Server for doing such a thing. SQL Server is built around the paradigm
of having a client send a request to the server and waiting for results.
Why do you want to be able to close the window? You could write an
object/program that runs on the server to handle these request, but then you
are simply replacing a tool that is already there, namely the agent which
you don't want to use.

--
----------------------------------------------------------------------------
Louis Davidson - drsql@hotmail.com
SQL Server MVP

Compass Technology Management - www.compass.net
Pro SQL Server 2000 Database Design -
http://www.apress.com/book/bookDisplay.html?bID=266
Note: Please reply to the newsgroups only unless you are interested in
consulting services. All other replies may be ignored :)

[quoted text, click to view]

Hi there:

Does anyone know how tu run a transact sql statement (or a SP) as a
background task without using SQL server job scheduling?. For example run
it from the command line using isql / osql but being able to close the
window. I am interested in leaving a long job running an not being canceled
because someone closes the window.

Also, is there a way from a SP to run other SPs asynchronously ?

Thank you,

Pedro.