Lynn Pettis (3/19/2009)

---

Okay, I can use stuff((select ', ' + cola from dbo.table1 t1 for xml path ('')), 1, 2, '') but I sure can't explain the how's and why's....

Stuff gets rid of a preceding comma at the beginning of the string. That's all. Try the query without it, and you get:

The Stuff command,...

The querying against this table is heavliy balanced towards queries against single records .... however the index DMV's show the non-clustered index getting most of the seeks, when i would...

Try this, see if it'll give you what you need. Returns the number of differences between the strings. I don't have time to finalize it right now, but...

I generally use SSIS to move data around. Into and out of databases.

Perhaps you could do something with exporting data out of the system databases into Excel? Not...

Might cause issues for disk space, but it's not like it's going to wear out the databases.

You seem to be trying to select the data between // and \\. Is that correct?

If so, then try this:

declare @UserName varchar(max);

--

SET @UserName = '03/12/2009 07:48 PM ...

I just ran your code on my machine. It looped 87 times in less than 1 second, and then stopped. No infinite loop. Did I misunderstand that...

Yep. Exactly.

Derek Dongray (3/19/2009)

---

Bob Hovious (3/19/2009)

---

I will try to dig up the Documentation of the undocumented parameters and try to figure out the correct order even if it takes a life...

"While" works in SQL 2000. Used to use it all the time...

Then the SSIS package isn't set up correctly, or there's something wrong with the Excel sheet.

Don't use dynamic SQL for this kind of thing. Use a string parser to break up the list of values into a table.

That's kind of already been said here,...

It means the job is protected from alteration while it's running. Means you'll get an error message if you try to modify it "in flight".

Basically, it's meant to protect...

Then it's probably either something wrong with the Excel file, or the Jet section of the registry on the machine you're running the SSIS package on.

Try running the import on...