Just an FYI, the following query runs in as little as 0.04 seconds to as much as 0.16 seconds - always fast, and always sub-second, and that's a good thing.

DBCC...

Here's my exact source(attached), and I used SSMA to copy the data up to SQL Server 2005 Developer Edition 64-bit with SP2. SSMA is SQL Server Migration Assistant....

I'll check out that article, but I've already solved the problem. I also suspect that the SGML in the QFX files is not actually up to spec, because...

UPDATE #3:

My re-run of the distance categories update ran in 3:23:09.29. Wow, what a difference! Index creation now in progress.

Steve

(aka smunson)

:-):-):-)

ANOTHER UPDATE:

I hate when I do this kind of thing - I messed up my initial update to the distance category field. I forgot to change out a...

UPDATE:

I searched high and low for an "XML repair" tool, and I couldn't find any freebies, nor even any paid for products that actually tout such a feature. ...

UPDATE:

I've created my two indexes on the Zip Code fields, which didn't take all that long, and expanded the database from 16 GIG to roughly 50 GIG. Due...

Now I remember what I ran into before. Missing end-tags, because the true format of the file is just SGML, and not true XML. XQuery fails...

My objective is to be able to take the transaction data and import it to the correct table based on the specific account it's for. Mind you, I...

Well, at least I seem to be on the right track, but I'm not about to give my box a nap... it's a quad-core, for crying out loud - it's...

Whew.... it ran successfully last night !!! Thus I now have 890,061,336 records that occupy 20.6 GIG at the table level (still an awful lot of...

Anyone with ALTER TABLE permissions for the table with the trigger on it could have executed a DISABLE TRIGGER statement. See the following link within BOL:

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/e6529f06-e442-437e-a7bf-41790bc092c5.htm

I couldn't...

UPDATE:

I'd still like to know what was going on with such huge logging, and it was definitely the log file growth that was the problem. As this database...

I'd agree easily that indexes could certainly cause that kind of difference, but I didn't create any, nor did I even create a primary key, and that was all intentional...

Well folks, things have definitely gotten interesting... I know that SQL Server has some level of overhead in a table, but I'm completely lost as to how...