AdminSQL Database feature voting forum admins (Product Owner, Microsoft Azure)

My feedback

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

    We’ll send you updates on this idea

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

    Tuukka,

    Could you please share the T-SQL Scalar UDF definition (datereturn)?

    Thanks,
    Joe

  2. 1 vote
    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

    Thanks for reporting.

    Could you please try the following and see if this resolves your issue?

    Note: for a future CU, this refresh will be automatic. Today the process is manual after inlineability has first been determined.

    After upgrading to SQL Server 2019 CU3, to re-evaluate if a UDF is eligible for inlining, refresh eligible scalar UDFs through either one of the following methods:

    1) Execute sp_refreshsqlmodule for applicable scalar UDFs
    2) Alter or recreate the existing scalar UDF with existing definition, permissions and set properties (see ALTER FUNCTION (Transact-SQL))

    The following script generates a script to refresh metadata for existing inlined scalar UDFs:
    /*
    Generates a script that can be used to refresh all active inlineable Scalar UDFs.
    Note: sp_refreshsqlmodule does not affect any permissions, extended properties,
    or SET options that are associated with the object.
    */
    SELECT 'EXECUTE sys.sp_refreshsqlmodule ''[' + OBJECT_SCHEMA_NAME(object_id) + +'].' + '[' + OBJECT_NAME(object_id)
    + ']'';' AS 'RefreshStatement'
    FROM sys.sql_modules
    WHERE is_inlineable = 1
    AND inline_type = 1;
    GO

  3. 11 votes
    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

    Azure SQL Database always takes a tail of log backup before a database is dropped. This ensures that you can restore a dropped database to the point in time when the deletion occurred, within the backup retention period configured for the database.

  4. 30 votes
    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

    Log backup size is determined by the amount of transaction log generated since the previous log backup, i.e. by the volume of writes to the database. It does not depend on the size of transaction log file in storage, so shrinking the log would have no impact on the log backup size.

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

    We’ll send you updates on this idea

    unplanned  ·  3 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hi Fabio,

    The closest floating point number to 5.175 is in fact a number that is infinitesimally less than 5.175. So the rounding is correct - even though the return value may seem unexpected vs. an exact equivalent.

    Thanks

  6. 8 votes
    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

    Thanks for the feedback Sohi.  We plan on bringing this feature to Azure SQL Database.  I'll follow up with an update on this User Voice suggestion once it is fully deployed.

  7. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Hi Martin,

    Note that in general, Halloween protection for STRING_SPLIT() is required because the input of the function can reference the same table being modified. For example, consider this query:

    INSERT INTO @T
    SELECT value
    FROM @T CROSS APPLY STRING_SPLIT(c, ';')

    However, under compatibility level 140 with query optimizer hotfixes enabled, and under compatibility level 150 with or without query optimizer hotfixes enabled, the optimizer does not add a spool if the input of STRING_SPLIT() is a string literal.

    Hope this helps,
    Dimitri

  8. 86 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  7 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Hello,

    Azure SQL Database serverless is now in preview:

    https://docs.microsoft.com/en-us/azure/sql-database/sql-database-serverless

    Feedback welcome. Thanks

  9. 1 vote
    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 →
    An error occurred while saving the comment

    Hello,

    Could you please let me know what version you were running when you saw the truncation error?

    The SPACE function will not exceed 8,000: https://docs.microsoft.com/en-us/sql/t-sql/functions/space-transact-sql?view=sql-server-2017. So SPACE(8000) = SPACE(8001) given 8001 is cut off at 8000. The hashes are the same because the output of the function is the same.

  10. 19 votes
    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

    Thank you for taking the time to provide feedback on your Azure SQL DB experience. Are you looking to track login failures exclusively for security purposes or are you also interested in receiving alerts for login failures tied to unavailability?

  11. 363 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    60 comments  ·  Virtual Machines  ·  Flag idea as inappropriate…  ·  Admin →
  12. 25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  5 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Sher,

    Thank you for taking the time to post this suggestion! This suggestion will be reviewed and discussed for a future planning cycle. If the proposed change meets the bar for approval, I'll provide an update on the status in this User Voice item.

    Best Regards,
    Joe Sack, Principal Program Manager, Microsoft

  13. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  SQL Database » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment

    Mike,

    Thanks for the additional details, I will take this feedback to the engineering team.

    Best Regards,

    Joe Sack, Principal PM, Microsoft

Feedback and Knowledge Base