Wednesday, February 23, 2005 - Posts
Check this image out. Yes, since this might be construted as NSFW, I'm just linking to it.
When I first saw it, what immediately came to mind? Eric Cartman asking his Mom, "Mom if you were in a German Scheisse video..."
Probably not the context that the FrontPage Folks were aiming at, but yet there it is...
Seriously, folks, WTF? I'm glad I wasn't showing that site to clients or managers.
Michael Rys posts links to three key white papers on XML storage, XQuery and XML indexing internals.
What are you waiting for...? :)
Euan Garden that is. More Here.
One of the more interesting Q&As...
What parser is used when manipulating XML inside SQL Server Engine?
XMLRW, which is the new small stream based parser for native code.
Michael Rys has also recently clarified that there will not be an option to have untyped XML instances constrained to just being well formed documents declaratively [e.g. declare @x xml(document)] for SQL Server 2005 but this may appear in future versions. While I'm okay with that, if you have feedback on it, please feel free to post that here and I'll make sure it the team gets it. Of course, you can do it with a check constraint on a column as Darshan posted. Maybe we can talk him into putting that example up on ttp://www.yukonxml.com. Nothing like peer presure, right?
Can't go into the specifics here, but I'd like to give a big public thanks to Kathleen Anderson and Chuck Letourneau for making me look good today. I asked a pretty open-ended a question and within moments, Kathleen pointed me at Chuck and Chuck gave me exactly what I needed.
Throw me a frick'n bone (or blog or book) here.
What I want, so I can starting learning how to use this magic brick, is a step by step walkthrough of building it into an ASP.NET solution. I'm only interested into doing the minimum required to get the Data Access, Exception, Caching and Logging blocks in my solution since I think I can follow the various quick starts well enough to figure out how to build my code around them.
I'll be the first to admit that while I have looked a the documentation, I'm just not seeing the entry points to this specific procedure.
I'll also be the first to buy the "dead tree" version of the documentation when its ready.