Did you know #4 You can make a connection using SQL Server Windows authemtication using non-Windows authenticated accounts.
On the server running the SQL Server instance;
Create a local (not domain) user.
In SQL Server - create a Windows authenticated user.
Make sure the username is prefixed with the server name.
For example, if your server name is SVR01 and the username you created was JBloggs
then the username you need to create in SQL Server is SVR01\JBloggs
On the client PC;
Create a local user with the identical name and password to the one created on the server.
This is important, the username and password must be identical on both machines.
Log on to the client PC as that local user
you will be able to connect to SQL Server using Windows authentication.
This might be useful where the client is in a DMZ with no domain access and the SQL Server is other side of the DMZ firewall.
Rework
If you haven't read Rework then do.
It's an insight into the way 37signals work which we would all do well to consider.
Did you know #3
The db2 command line suggests using QUIT to leave the command line processor.
What it does not tell you is that QUIT does not break the back end process or database connection,
CONNECT RESET breaks a database connection but does not terminate the back end process,
TERMINATE does both of those things.
Using QUIT can cause subsequent db2 commands to fail, for example:
db2 => quit DB20000I The QUIT command completed successfully. db0008:db2xd1 28> db2stop 02/02/2011 10:53:56 0 0 SQL1025N The database manager was not stopped because databases are still active. SQL1025N The database manager was not stopped because databases are still active.
So, if you want to carry on running db2 commands, use QUIT.
If you want to leave db2 and have the back end process stop then use TERMINATE.
See QUIT command reference