Making extra money as a programmer on the side

Ok, I've been programming for years, so not much shocks me anymore. But, every once in a while I wonder how I can make more money without having to work more hours. At some points, it seems as though, as a developer, I may spend the rest of my life in "crisis mode" for clients.

Anyway, lately, I've been investigating some strategies. I've found that if I were to choose the ultimate job, it would consist of the following... unlimited number of clients, make money when I'm not working, create residual money, no extreme deadlines.

From what I've seen so far, it looks like affiliate marketing is the way to go. I've been working with it for a short time now. No big successes yet. But, considering this economy, companies are scrambling for these marketers.

If you want to continue on that journey with me, or learn more, please visit http://www.awealthyaffiliatemember.com for more information. On a side note, the group within this "university" also needs developers as they have their own job board.

How can I tell if a stored procedure is taking too long to run

A lot of times, we are called in a panic if something crashes. A lot of times, it could be because something crashed, in some cases, a stored procedure. Here is a good article with a solution: http://www.databasejournal.com/features/mssql/article.php/3500276/Identifying-Long-Running-SQL-Server-Agent-Jobs.htm

A severe error occurred on the current command. The results, if any, should be discarded.

Error message:
A severe error occurred on the current command. The results, if any, should be discarded.
A severe error occurred on the current command. The results, if any, should be discarded.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Exception: A severe error occurred on the current command. The results, if any, should be discarded.
A severe error occurred on the current command. The results, if any, should be discarded.

Error Message in DB:
The connection has been dropped because the principal that opened it subsequently assumed a new security context, and then tried to reset the connection under its impersonated security context. This scenario is not supported. See "Impersonation Overview" in Books Online

Solution:
Implement coding workaround, non-dba issue.
Issue: Web.config setting for connection strings "Connection Reset" does not work for newer versions of .NET2.0. This issue starts once .NET 2.0 SP1 or greater is installed on the application server machine. You'll have to change your code where you are impersonating someone.

Immediate solution:
In your web.config database connection string turn off pooling, Pooling=false;