Server’s free disk space:

xp_fixeddrives  

Determine logspace: 

dbcc sqlperf (logspace)  

TempDB size:

 sp_tempdbspace  

select 
   current_timestamp as Time,
   user as Benutzer,
   system_user as System_Benutzer,
   current_user as Current_Benutzer,
   session_user as Session_Benutzer   

sp_who2 


Useful stored procedures: 

sp_helpdb -- Displays information about all databases on the server
sp_helpdb databasename -- Displays information about a particular database
sp_help objectname -- Displays information about a table
sp_spaceused -- Displays information about the space used in the current database
sp_tables -- Lists the tables in a database
sp_helptext name -- Displays the code used in a particular stored procedure
sp_dboption -- Sets or returns information about database options    

Oracle

Get all tables including the system ones:
SELECT table_name FROM all_tables;

That will give you only the tables owned by the user that you are connecting as:
SELECT table_name FROM user_tables;

Query table columns:
SELECT * FROM all_tab_cols WHERE table_name = 'whatever table name you are looking for'

Looking for comments on the tables:
SELECT * FROM all_tab_comments WHERE table_name = 'whatever table name you are looking for'

SQL-Server

That will give you all tables:
SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_TYPE = 'BASE TABLE'

You can save your data during a HttpRequest by passing it to System.Web.HttpContext.Current.Items[itemKey].
Objects stored in this Collection will be available during the whole lifecycle of the HttpRequest.

Example of usage:

System.Web.HttpContext.Current.Items["reloadCount"] = 5;

int reloadCount = (int) System.Web.HttpContext.Current.Items["reloadCount"];

Be carefull when installing it on a productive server, use a test environment first. Seems like there are a lot of problems upgrading systems. Also be aware that WSS and MOSS service packs cannot be uninstalled!

Downloads:
WSS 3.0 SP1
MOSS 2007 SP1

HttpApplication Events:

Application_AcquireRequestState
Occurs when ASP.NET acquires the current state (for example, session state) that is associated with the current request. 

Application_AuthenticateRequest
Occurs when a security module has established the identity of the user. 

Application_AuthorizeRequest
Occurs when a security module has verified user authorization. 

Application_BeginRequest
Occurs as the first event in the HTTP pipeline chain of execution when ASP.NET responds to a request. 

Application_Disposed
Adds an event handler to listen to the Disposed event on the application. 

Application_EndRequest
Occurs as the last event in the HTTP pipeline chain of execution when ASP.NET responds to a request. 

Application_Error
Occurs when an unhandled exception is thrown. 

Application_PostAcquireRequestState
Occurs when the request state (for example, session state) that is associated with the current request has been obtained. 

Application_PostAuthenticateRequest
Occurs when a security module has established the identity of the user. 

Application_PostAuthorizeRequest
Occurs when the user for the current request has been authorized. 

Application_PostMapRequestHandler
Occurs when ASP.NET has mapped the current request to the appropriate event handler. 

Application_PostReleaseRequestState
Occurs when ASP.NET has completed executing all request event handlers and the request state data has been stored. 

Application_PostRequestHandlerExecute
Occurs when the ASP.NET event handler (for example, a page or an XML Web service) finishes execution. 

Application_PostResolveRequestCache
Occurs when ASP.NET bypasses execution of the current event handler and allows a caching module to serve a request from the cache. 

Application_PostUpdateRequestCache
Occurs when ASP.NET completes updating caching modules and storing responses that are used to serve subsequent requests from the cache. 

Application_PreRequestHandlerExecute
Occurs just before ASP.NET begins executing an event handler (for example, a page or an XML Web service). 

Application_PreSendRequestContent
Occurs just before ASP.NET sends content to the client. 

Application_PreSendRequestHeaders
Occurs just before ASP.NET sends HTTP headers to the client. 

Application_ReleaseRequestState
Occurs after ASP.NET finishes executing all request event handlers. This event causes state modules to save the current state data. 

Application_ResolveRequestCache
Occurs when ASP.NET completes an authorization event to let the caching modules serve requests from the cache, bypassing execution of the event handler (for example, a page or an XML Web service). 

Application_UpdateRequestCache
Occurs when ASP.NET finishes executing an event handler in order to let caching modules store responses that will be used to serve subsequent requests from the cache. 

Application_Init
This method occurs after _start and is used for initializing code.

Application_Start
As with traditional ASP, used to set up an application environment and only called when the application first starts.

Application_End
Again, like classic ASP, used to clean up variables and memory when an application ends.

Session Events:

Session_Start
As with classic ASP, this event is triggered when any new user accesses the web site.

Session_End
As with classic ASP, this event is triggered when a user's session times out or ends. Note this can be 20 mins (the default session timeout value) after the user actually leaves the site.

Profile Events:

Profile_MigrateAnonymous
Occurs when the anonymous user for a profile logs in.

Passport Events:

PassportAuthentication_OnAuthenticate
Raised during authentication. This is a Global.asax event that must be named PassportAuthentication_OnAuthenticate.
 

Possibly more events defined in other HttpModules like:

System.Web.Caching.OutputCacheModule
System.Web.SessionState.SessionStateModule
System.Web.Security.WindowsAuthentication
System.Web.Security.FormsAuthenticationModule
System.Web.Security.PassportAuthenticationModule
System.Web.Security.UrlAuthorizationModule
System.Web.Security.FileAuthorizationModule
System.Web.Profile.ProfileModule

Gerät: iRobot Roomba 560

Funktionsweise: Roboterstaubsauger

Testurteil: sehr gut 

Kurzer Testbericht:

Was will man viel sagen, der Roomba macht einfach, was er soll. Nachmittags, wenn niemand zu Hause ist, erwacht er zum Leben und saugt mal eben schnell (ok, er braucht ca. 70min) die Wohnung. Wenn er damit fertig ist, fährt er zurück zu seiner Ladestation und hält ein Nickerchen bis am nächsten Tag. Selbst die langen Haare meiner Freundin sind für ihn kein Problem, allerdings sollte man so alle zwei bis drei Tage den Staubbehälter leeren und die Bürsten reinigen. Der Aufwand dafür beträgt ca. 5 min.

Die Bedienung ist kinderleicht, Roomba erklärt sich über das eingebaute Sprachmodul inklusive Demonstration seiner Fähigkeiten selbst.

Insgesamt macht der Roomba einen sehr ausgereiften Eindruck und ist sein Geld allemal wert, vor allem wenn man bedenkt, was eine Haushaltshilfe für eine vergleichbare Arbeit verlangen würde.

Die Goodies:

Der Roomba ist programmierbar! Unter http://www.sparkfun.com/commerce/categories.php?cPath=2_104 gibt es alles was man benötigt, um den Roomba an den PC anzuschliessen. Das Coolste ist, dass der Roomba mit dem Microsoft Robotics Studio (kostenloser Download) kompatibel ist, d.h. er kann ganz einfach mit .NET programmiert werden.

Weitere Links für Entwickler:

http://www.devx.com/dotnet/Article/32729/0/page/3
http://www.sparkfun.com/commerce/categories.php?cPath=2_104
http://www.roombadevtools.com/
http://msdn2.microsoft.com/en-us/robotics/default.aspx
http://msdn2.microsoft.com/en-us/library/bb483025.aspx