I am looking for information and I am going to ask the community for assistance in this.
- The Garbage Collector in .NET. I have been asking this question on and off for about 3 years and I have never gotten a good answer. It seems that whenever I ask a question about how the GC works in a public forum, the only answer I get is that it is some magical mystical object and I don't need to worry about it. Well, that answer is not good enough for me. I have read posts from Paul Wilson and an article at The Server Side. I want to know more about what is going on behind the scenes, so if you know of any other articles about the GC that are beyond the statement of “it is called when a threshold is reached and it walks a tree of objects and removes the objects that can no longer be reached“ then please send them to me. Why am I interested in this? Well, I just want to know more about what is happening behind the scenes. Black boxes that do auto-magical things make me nervous so I want to know as much as I can about them.
- The CLR integration with Yukon. I know that the CLR integration with Yukon will make the database more stable because there will be less need (if any) to use extended stored procedures. I know that I can now use procedure logic in the database with sprocs, functions, and triggers as oppossed to TSQL's set based logic. I want to know more regarding this integration. What does Yukon's hosting of the CLR do regaring threading, memory management, and other features of the CLR? What are the limitations of hosting the CLR in Yukon?
Please post any type of links in the feedback for this post. Thanks.