SELECT

tab.col.value('@id','varchar(5000)') AS 'BookID',

...

Attributes on a node are identified by the "@" character.

Suggestion:

Don't use the double slash (//) (e.g. "//book") to locate the nodes as this implies that you are...

KEDIT http://www.kedit.com/

Can handle lots of data and is fast! Fully customizable interface (including line numbers) with built-in macro language KEXX (built on REXX http://en.wikipedia.org/wiki/Rexx)

Our environment is identical. I.e., everything is checked in to our source code control system (Perforce) as separate files.

The attached DOS script (BuildSchema.cmd) will do the job. Yes,...

Unlike Oracle, SQL Server does not support a UTF-8 collation (character set). Since UTF-8 is, in essence, a binary stream, it will have to be converted to the Unicode...

Re: A clustered index physically rearanges data on disk.

Technically, the use of the word "disk" is wrong. It rearranges data within the (SQL Server) pages and extents. Where...

Charles Kincaid (12/9/2009)

---

...

Here is the secret, at least to thinking about this. The CTE generates a very temporary table. It only lives for the length of the single...

Enabling Full-Text by itself doesn't impact performance. Note that all SQL Server 2005 database have full-text enabled by default.

If you don't have any columns that have a full-text index...

Lynn Pettis (11/17/2009)

---

I see that the question has been rewritten as it is now using variables that are set first and changes the word same to equivalent.

Now that the question...

It solves the time difference problem due to the 4 separate queries.

I...

It is a valid data model. I have designed and implemented it where the business case required it. I've also used it to prevent certain updates and/or deletions....

Maybe, but we are not...

Lynn Pettis (11/17/2009)

---

I actually answered true, and here is why, if you run this:

select getdate(), getutcdate()

you may get a result like this:

2009-11-17 06:16:57.527 2009-11-17 13:16:57.527

They appear different, but are actually...

First off, you should be using a Source Code Control system.

Then you need to create an "Upgrade Schema" script that can be run in batch mode against your QA databases...

Note that SQL Server 2005 Reporting Services has a bad defect related to linked reports. If the report is a linked report, the page size properties of the master...

Since this is SQL Server 2005, you should be using SQLCMD vs. OSQL. OSQL is obsolete