Hiram

My feedback

  1. 1,553 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    65 comments  ·  Networking » IPv6  ·  Flag idea as inappropriate…  ·  Admin →

    IPv6 in Azure VNET is currently previewing globally- in ALL Azure Public cloud regions.

    Announcement (Service Update): https://azure.microsoft.com/en-us/updates/public-preview-microsoft-adds-full-ipv6-support-for-azure-vnets/

    Links to Documentation & Samples
    Full documentation including sample scripts is available here: https://aka.ms/IPv6ForAzureVNETdoc

    A sample JSON template is posted in the quickstart repository: https://azure.microsoft.com/en-us/resources/templates/ipv6-in-vnet/

    Hiram commented  · 

    Would be good if NSG would display the client IP how PaaS services do on their resource firewalls. This would avoid the confusion if traffic is going over ipv4 or ipv6.

    Hiram supported this idea  · 
  2. 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 » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 30

    <=-=Jul 21 2005 2:03PM=-=>

    Greg,
    I agree that this would be valuable, but as you can probably guess it is too late in the product cycle to do this in SQL 2005. I will make sure that this gets tracked as a requirement in the next release.
    Thanks,
    - Balaji

    <=-=Jul 24 2005 3:37AM=-=>

    I’ll chime in here to make a few points.

    One idea I once saw floated was to add WITH SCHEMABINDING for stored procedures. I like to add here that this is both too harsh and too lax. Too harsh , because you may want to change tables by means of drop and recreate, and SCHEMABINDING would be a major hassle. Too lax, because it would not in itself address temp tables.

    The other important issue is that temp tables created in the procedure needs to be handled. But this should be difficult, just restore…

    Hiram commented  · 

    +1
    I agree it would be useful.
    Perhaps this is a bug for the Execute command. I ran into this on SQL Server 2017 only when a variable is assigned. You can reproduce the issue by setting the user database offline.

    use tempdb
    go
    if 1=0
    begin
    --job step here:
    declare @var as date = dateadd(day, -1, getdate())
    execute dbawork.dbo.uspTest @tbd = @var
    end
    else begin
    print '0'
    end

    Msg 946, Level 14, State 1, Line 7
    Cannot open database 'DBAWork' version 852. Upgrade the database to the latest version.

    Hiram supported this idea  · 

Feedback and Knowledge Base