Davide Mauri

My feedback

  1. 8 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Davide Mauri commented  · 

    In case of big JSON result, you can have the result split in multiple rows, as documented here:

    https://docs.microsoft.com/en-us/sql/relational-databases/json/format-query-results-as-json-with-for-json-sql-server?view=sql-server-ver15#output-of-the-for-json-clause

    BCP, at the moment, is not able to correctly deal with this but there is a workaound. If

    bcp "with json(j) as (select replicate('0', 5000) as col1 for json path) select j from json" queryout testbcpjson.txt -c -S localhost -T

    that works as it solves the split problem right on the server side

  2. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Davide Mauri commented  · 

    By default Hyperscale database will be created with a size of 40GB. 10GB will be allocated every 15 minutes or so, until 40GB are reached. This is done to provide enough Page Server to avoid any possible hot-spot and spread out I/Os.

Feedback and Knowledge Base