In continuing this look into the new XML Data Type in SQL Server 2005:

• XML Data Type XQuery XML Indexes XML Schema Collection and Http Endpoints in SQL Server 2005
• SQL Server 2005 XML DML ( XML Data Manipulation Language ) and the XML Data Type
• XML Data Type in SQL Server 2005 - Part I

eventually you will want to load this XML into an XmlDocument ( as an example ) using ADO.NET.

Continuing with this idea of a library of books as used in the first two examples above, we can load the index of each book into an XmlDocument using the following ADO.NET

Per another question I received, the last thing I wanted to mention on the subject of Excel is that you can use SqlBulkCopy to transfer Excel Spreadsheet data at high speeds to a SQL Server Database Table. I talked about SqlBulkCopy in a previous ADO.NET Tutorial:

• SqlBulkCopy - Copy Table Data Between SQL Servers at High Speeds - ADO.NET 2.0 New Feature

You can view my other posts on Excel for more information about using ADO.NET to read and write to Excel Workbooks and Worksheets:

• Reading Excel Worksheet and Column Schema Information Using ADO.NET 2.0 and GetSchema
• Reading and Writing Excel Spreadsheets / Worksheets Using ADO.NET C# DbProviderFactory
  

One of the problems that we recently faced was the need to post a message to MSMQ when the data in a SQL table was changed. An extensive search of the various resources that we have led us to this solution. And, although it seems to be complicated, it appears to be the only way, at the moment, to accomplish our goal.

First, we created a Visual Basic ActiveX DLL project that will actually talk to the Message Queue. We chose to expose a single method called Send. The code appears below

As I'm sure you're aware, it's extremely difficult to build a dynamic Website without a way to access and manipulate your content dynamically. Back in 1995 when the majority of Websites were still serving static content (i.e. plain HTML files), database driven sites were nowhere near as popular as they are today. Why do you think this is? Are databases easier to setup today? Is Web server software more usable? Or was it just a natural progression that we as Web developers went through to "evolve" from the way we developed "back then"?

I like to think it's all of these things. Today we have databases such as MySQL and SQL Server that can be set up on a development machine with very little expertise: you simply activate the setup program, change a couple of options and you're up and running in 20 minutes or so. It also seems that databases are "the way to go" these days, which makes sense when you think about it: they're readily available (some such as MySQL are free), some are supported cross-platform, and others are supported with native providers or pure source code libraries.