See how to log Web application errors for better health monitoring, what to read if you're thinking about LINQ, and which blog Scott recommends reading this month.
MSDN Magazine April 2008
View Complete Post
This month Toolbox provides help with error logging, finds an app that helps you write LINQ queries, and explores the non-technical side of development.
MSDN Magazine September 2008
This month we bring you products that let you synchronize data, correct runtime errors, and more.
MSDN Magazine August 2006
SSIS 2008 R2
I’m a relative newbie to SSIS but a long time developer / dba.
I have developed several packages that I execute from stored procedures, via the cmdshell,
and I want to capture any error messages that come from the actual execution.
Ideally I would check a sql table for any error results.
I found SSIS > Logging on the Menu bar and created a Sql Server log (in the same database as I am executing the sp from).
In the Configure SSIS Logs, I created the appropriate entry on the Providers and Logs tab and on the details tab I selected only the OnError check box.
All well and good. After an execution I find the sysssislog table in the system tables.
What I did not expect to see was the Begin Execution / End Execution rows for the package just executed.
I only want errors to show up however I have not yet tested an error situation.
Entity Framework and SQLCE - Repeated Logging of data (quickly) causes failed to open errors Hi all
I am using C# Visual Studio 2010 with EF 4.1. I am receiving some SCADA data that I would like to log to the database, all is well, until the data comes in quickly (not really that quickly)
I parse and massage the data, and then call a "logMessageToDB" function.
now if I call the function again before the last message has been logged, I get an error in my error handler
logging the message caused the following error -> The underlying provider failed on Open.
How can I log the data more quickly? why does it take so long to add a new record.
My function is below, please excuse the uglyness of it (I have just started with C#, there is a bit of a learning curve)