This article has been archived. It is offered "as is" and will no longer be updated.
When you review the last_batch column by using Current Activity in SQL Enterprise Manager, or the master.sysprocesses.last_batch column when you use SQL Server Query Analyzer, you may see the Last Batch value as 1900-01-01 00:00:00.000 for a connection (system server process IDs [SPIDs]). The Last Batch value appears as 1900-01-01 00:00:00.000 because there is a connection (SPID) that has been made through a client that makes a connection without any remote stored procedure call (RPC) activity on the computer that is running SQL Server. The connection does not issue any Execute commands. Because the last_batch column is typed as datetime, and a value is absent, the value is stored as the default datetime value (which is 1900-01-01 00:00:00.000). The last_batch column is updated with the datetime of the last time a client process executed a remote stored procedure call or an Execute statement. Most client technology issues at least one RPC or Execute statement when the connection is made. If the client technology does not issue at least one RPC or Execute statement when the connection is made, then there is possibly no "last" RPC or Execute statement. If there is no "last" RPC or Execute statement, you will see a last_batch value of 1900-01-01 00:00:00.000.
To examine this behavior, you can use the Isql.exe program that is provided with Microsoft SQL Server 6.5 to make a client connection to the computer that is running SQL Server. Clear the Automatic Ansi to OEM and Use International Settings default options in the client configuration utility. Next, make a connection to the computer that is running SQL Server. Note that the last_batch value is 1900-01-01 00:00:00.000 until you use the connection to execute a statement.