Home Forums SQL Server 7,2000 Strategies A Case For Concatenation (Building Delimited Strings ) In T-SQL RE: A Case For Concatenation (Building Delimited Strings ) In T-SQL

  • I'm afraid I can't, but I will listen respectfullly to anyone who can, if they'd care to report their results. However, I see that as a different issue from doing it at the database level instead of passing it to a UI.

    I can't argue with "It depends." The difference in concatenating and simple passing of the raw data is a function of the average number of rows that need to be concatenated, the average size of the data within the column being concatenated, and the combined size of the columns that would be duplicated. With only two or three average rows being concatenated, the percentage of "compression" would obviously be less. The same would hold true if the values being concatenated were longer strings.

    Please understand, I'm not arguing that concatenation should always be done at the server, I'm just saying there seem to be instances where it would be the better solution, and more instances where it really doesn't matter.

    Thanks for the feedback, G.

    __________________________________________________

    Against stupidity the gods themselves contend in vain. -- Friedrich Schiller
    Stop, children, what's that sound? Everybody look what's going down. -- Stephen Stills