-
Thursday, June 04, 2009
This is a follow up on a prior post I've made a few months back on XQuery, with the purpose of this post to just show a few more examples on how powerful XML and XQuery can be -- with no additional overhead costs. If implemented correctly, you can even get better performance gains; but I'll possibly discuss that in a future offering. For this segment, I wanted to document the common usages I've come across lately, and refer to it later on as a refresher. Example 1: So, you've got xml data, and the structure looks as such: key1 value1
-
Thursday, February 12, 2009
What's XQuery? It's a language backed by the W3C to standardize querying XML. Why XQuery? Microsoft started offering support for it in SQL Server 2000 and in SQL Server 2005, extended it with more support with the introduction of the XML data type column. It's fast, it's compact, and you don't need to add 10 million trivial columns. You just add one XML column and stick raw XML in there. It's that easy, a caveman can do it. Here's more information about Microsoft and XQuery. So what's the bad news? It's yet another language to learn and the syntax is
-
Sunday, November 09, 2008
Ever open up the SQL Server Configuration Manager and receive this message? I have; and an initial google search bring up a bevy of solutions. Unfortunately, the first several offerings did not solve my problem -- which prompted me to dig a little deeper. Apparently, I had corrupted my WMI repository somewhere along the line; and after some reading, the WMI can be corrupted after multiple restores of a database... which I'm definitely guilty of. So the solution? rebuild the WMI. Piece of cake, right? Luckily, I stumbled across this blog link which detail these instructions (which can be batched
