Hi Bonnie,

Agent is used to time out session state when it goes longer than the TimeOut setting.

>I've read the docs about how to store SessionState to SQL Server, and all seems to be working correctly, but I have one little question. Hopefully, one of you guys might either know the answer definitively or can point me to some links for more research.
>
>Here's the deal ...
>
>I ran the SQL Script that comes with .NET, called InstallPersistSqlState.sql. When I ran it, it said that it didn't complete successfully because SQL Agent needed to be running. OK, fine ... not knowing exactly what SQL Agent does (something to do with scheduling jobs, I think) ... I started it up anyway. Then ran the script again. Ran fine. Watching SQL Profiler while my Web app runs, I can see it store Session stuff to SQL Server, so all is right with the world. However, SQL Agent is constantly querying the database. So, since the docs themselves didn't say anything about having to have SQL Agent running, I thought I'd see what happens when I turn off the service. Sure enough, everything still seems to be working the same way ... from SQL Profiler, I can see a SP being run called TempUpdateStateItemLong (which I assume is updating my Session State). Does SQL Agent *have* to be running in order for this stuff to work? It sure doesn't seem like it, but I haven't tested it extensively
>enough to know if that's true or not.
>
>Anybody know for sure?
>
>Thanks,
>~~Bonnie