Thought on Microsoft client XQuery
I've known for a couple of weeks now that XQuery and the new XML-SQL client mapping have been dropped from System.Xml in .NET 2.0. The
I've known for a couple of weeks now that XQuery and the new XML-SQL client mapping have been dropped from System.Xml in .NET 2.0. The
Got back from Win-Dev last night…and immediately crashed. It was a great show, a little exhausting because some of the folks that I’d lined up
One more thing about getting an error 6522 wrapper from SQLCLR procedures. the workaround I spoke about last week (dummy catch block) works to propagate
Made it to this conference, came a day early just in case (see I’m at SQLPass…not). No hurricanes at this one, but fairly nasty cold
There's a new Community Technology Preview of SQL Server 2005 available on MSDN for universal subscribers. I'm sure you've all heard of it by now,
A few weeks ago, I was surprised by an error message when attempting to create an HTTP endpoint with CREATE ENDPOINT. The error was "You
About a month ago, I'd written about unhandled errors in .NET procedural code always causing error 6522 to be returned to the (T-SQL) caller (see
The new SNAC (SQL Native Client) OLE DB provider handles naming of parameters a tad differently than SQLOLEDB. Let's say that I have the parameterized query
After having been immersed in .NET since the alpha version, I'd lost touch with how many products use OLE DB and ODBC. After all, when
I heard that when SQL Server 2005 ships, SQLCLR (the ability to execute .NET code in SQL Server) will be disabled by default. This is
Just finished watching Ichiro break the single season hit record on TV. I’m a Seattle Mariner fan from way back when, and a big Ichiro
With training and consulting from SQLskills, you’ll be able to solve big problems, elevate your team’s capacity, and take control of your data career.