Yes, there is a "secret"... simply think about what you want to do to columns instead of what you want to do to rows. That and having a little...

Now, thats a "hint" if I ever saw one... 😉

Heh... another compliment. Thanks, Jason, but...

Shoot... once I learned it, I was just aching for a place to use it! ...

Heh... Troy, you must have a death wish... testing deletes...

That's quite a compliment, Jason. Thanks. Glad to see someone take it to the next level by actually getting a better job from what they're learned by looking...

Unless the "spaces" between the columns are something besides spaces, then you can't use BCP to import this file because the country names may also have spaces.

The best answer for SQL Server 2000 is, in fact, the Temp Table solution. It's nasty fast, especially if you use a SELECT/INTO.

The solution that Absinthe showed ...

select (select...

The seed should probably the value returned from the NextID proc...

Other problem is, you have to increment the NextID in the NextIDtable by the number of rows you have in...

Think of it as a "going away present", Jason. Good luck on your new job!

There's no need to convert to a number and then back to a date if the data is just being used in a WHERE clause... for example... a modification of...

What is the primary key of the table? Please include the datatype...

In terms of the original script, I unfortunately haven't noticed any significant difference worth writing home about in terms of execution time after changing it from a cursor to a...

The problem is that you never give the system time to "breath"... sure, it only takes about 3 seconds to delete 100,000 rows provided you don't have Delete Triggers on...

Adam Angelini (12/20/2007)

---

A quick follow up. I used one of the built in reports to find when this was happening. I right clicked the DB and went to reports/disk usage....