Aaron Hope

My feedback

  1. 27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron Hope supported this idea  · 
  2. 4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron Hope supported this idea  · 
  3. 6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  3 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron Hope commented  · 

    I'd love to see transparent compression of off-row data, but wouldn't a general purpose compression alg make more sense than SCSU? I just want type-safe COMPRESS/DECOMPRESS without all the repetition.

    http://unicode.org/faq/compression.html#longer-texts

  4. 2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 2

    <=-=May 21 2017 3:20AM=-=>

    The docs (at msdn: “Specify Field and Row Terminators (SQL Server)”) say, “Any printable character”. They do not say, “Any printable ascii character”, so the product is not currently meeting this important promise.

    Although it’s well and good that the product supports “String of up to 10 printable characters”, and this could be used to specify a bullet-proof terminator signature, Excel does not support importing text files with multiple sequential delimiters, so generating files with such a sequence would not support viewing/manipulating the data in Excel. In practical terms, we end up needing to use standard qualifiers, which are ugly.

    There is value to supporting non-ascii field terminators so please fulfill the promise made in the docs.

    Aaron Hope supported this idea  · 
  5. 12 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron Hope supported this idea  · 

Feedback and Knowledge Base